summaryrefslogtreecommitdiff
path: root/drivers/video/fbdev/sticore.h
diff options
context:
space:
mode:
authorTomi Valkeinen <tomi.valkeinen@ti.com>2015-06-04 15:22:23 +0300
committerTomi Valkeinen <tomi.valkeinen@ti.com>2015-06-17 13:44:53 +0300
commit736e60ddc215b85e73bbf7da26e1cde84cc9500f (patch)
tree82a8c0f7b9022cac659e6491da70ef7cd41b5fa4 /drivers/video/fbdev/sticore.h
parent606ae4865a1947c04d52b97b5109cda90aebe892 (diff)
OMAPDSS: componentize omapdss
omapdss kernel module contains drivers for multiple devices, one for each DSS submodule. The probing we have at the moment is a mess, and doesn't give us proper deferred probing nor ensure that all the devices are probed before omapfb/omapdrm start using omapdss. This patch solves the mess by using the component system for DSS submodules. The changes to all DSS submodules (dispc, dpi, dsi, hdmi4/5, rfbi, sdi, venc) are the same: probe & remove functions are changed to bind & unbind, and new probe & remove functions are added which call component_add/del. The dss_core driver (dss.c) acts as a component master. Adding and matching the components is simple: all dss device's child devices are added as components. However, we do have some dependencies between the drivers. The order in which they should be probed is reflected by the list in core.c (dss_output_drv_reg_funcs). The drivers are registered in that order, which causes the components to be added in that order, which makes the components to be bound in that order. This feels a bit fragile, and we probably should improve the code to manage binds in random order. However, for now, this works fine. Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com> Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Diffstat (limited to 'drivers/video/fbdev/sticore.h')
0 files changed, 0 insertions, 0 deletions