tree d8ece0b76b86b47973921d33f5971d3a5be5d79a
parent 09a8c45cbb872f5e861c4385d6967d0aa7f637f1
author Tomi Valkeinen <tomi.valkeinen@ti.com> 1354877408 +0200
committer Tomi Valkeinen <tomi.valkeinen@ti.com> 1354892104 +0200

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>