• Tomi Valkeinen's avatar
    OMAPDSS: interface drivers register their panel devices · 35deca3d
    Tomi Valkeinen authored
    Currently the higher level omapdss platform driver gets the list of
    displays in its platform data, and uses that list to create the
    omap_dss_device for each display.
    
    With DT, the logical way to do the above is to list the displays under
    each individual output, i.e. we'd have "dpi" node, under which we would
    have the display that uses DPI. In other words, each output driver
    handles the displays that use that particular output.
    
    To make the current code ready for DT, this patch modifies the output
    drivers so that each of them creates the display devices which use that
    output. However, instead of changing the platform data to suit this
    method, each output driver is passed the full list of displays, and the
    drivers pick the displays that are meant for them. This allows us to
    keep the old platform data, and thus we avoid the need to change the
    board files.
    Signed-off-by: default avatarTomi Valkeinen <tomi.valkeinen@ti.com>
    35deca3d
rfbi.c 22.7 KB