diff options
| author | Tomi Valkeinen <tomi.valkeinen@ti.com> | 2012-12-07 12:50:08 +0200 |
|---|---|---|
| committer | Tomi Valkeinen <tomi.valkeinen@ti.com> | 2012-12-07 16:55:04 +0200 |
| commit | 486c0e17b7d1a4f8f057a97f2e48f715208f950d (patch) | |
| tree | d8ece0b76b86b47973921d33f5971d3a5be5d79a /drivers/video/omap2/omapfb | |
| parent | 09a8c45cbb872f5e861c4385d6967d0aa7f637f1 (diff) | |
| download | talos-op-linux-486c0e17b7d1a4f8f057a97f2e48f715208f950d.tar.gz talos-op-linux-486c0e17b7d1a4f8f057a97f2e48f715208f950d.zip | |
OMAPDSS: manage output-dssdev connection in output drivers
We currently attach an output to a dssdev in the initialization code for
dssdevices in display.c. This works, but doesn't quite make sense: an
output entity represents (surprisingly) an output of DSS, which is
managed by an output driver. The output driver also handles adding new
dssdev's for that particular output.
It makes more sense to make the output-dssdev connection in the output
driver. This is also in line with common display framework.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Diffstat (limited to 'drivers/video/omap2/omapfb')
0 files changed, 0 insertions, 0 deletions
