mirror of https://gitee.com/openkylin/linux.git
09e5bb6d5b
When an omap_dss_device operation can be implemented in multiple places in a chain of devices, it is important to find out which device to address to perfom the operation. This is currently done by calling the operation on the display device at the end of the chain, and recursively delagating the operation to the previous device if it can't be performed locally. The drawback of this approach is an increased complexity in omap_dss_device drivers. In order to simplify the drivers, we will switch from a recursive model to an interative model, centralizing the complexity in a single location. This requires knowing which operations an omap_dss_device supports at runtime. We can already test which operations are implemented by checking the operation pointer, but implemented operations can require resources whose availability varies between systems. For instance a hot-plug signal from a connector can be wired to a GPIO or to a bridge chip. Add operation flags that can be set in the omap_dss_device structure by drivers to signal support for operations. Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Reviewed-by: Sebastian Reichel <sebastian.reichel@collabora.co.uk> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com> |
||
|---|---|---|
| .. | ||
| displays | ||
| dss | ||
| Kconfig | ||
| Makefile | ||
| TODO | ||
| omap_connector.c | ||
| omap_connector.h | ||
| omap_crtc.c | ||
| omap_crtc.h | ||
| omap_debugfs.c | ||
| omap_dmm_priv.h | ||
| omap_dmm_tiler.c | ||
| omap_dmm_tiler.h | ||
| omap_drv.c | ||
| omap_drv.h | ||
| omap_encoder.c | ||
| omap_encoder.h | ||
| omap_fb.c | ||
| omap_fb.h | ||
| omap_fbdev.c | ||
| omap_fbdev.h | ||
| omap_gem.c | ||
| omap_gem.h | ||
| omap_gem_dmabuf.c | ||
| omap_irq.c | ||
| omap_irq.h | ||
| omap_plane.c | ||
| omap_plane.h | ||
| tcm-sita.c | ||
| tcm-sita.h | ||
| tcm.h | ||