• Tomi Valkeinen's avatar
    OMAPDSS: alloc dssdevs dynamically · 5274484b
    Tomi Valkeinen authored
    We currently create omap_dss_devices statically in board files, and use
    those devices directly in the omapdss driver. This model prevents us
    from having the platform data (which the dssdevs in board files
    practically are) as read-only, and it's also different than what we will
    use with device tree.
    This patch changes the model to be in line with DT model: we allocate
    the dssdevs dynamically, and initialize them according to the data in
    the board file's dssdev (basically we memcopy the dssdev fields).
    The allocation and registration is done in the following steps in the
    output drivers:
    - Use dss_alloc_and_init_device to allocate and initialize the device.
      The function uses kalloc and device_initialize to accomplish this.
    - Call dss_copy_device_pdata to copy the data from the board file's
    - Use dss_add_device to register the device.
    Signed-off-by: default avatarTomi Valkeinen <tomi.valkeinen@ti.com>