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/dss/dss.h | |
| parent | 09a8c45cbb872f5e861c4385d6967d0aa7f637f1 (diff) | |
| download | op-kernel-dev-486c0e17b7d1a4f8f057a97f2e48f715208f950d.zip op-kernel-dev-486c0e17b7d1a4f8f057a97f2e48f715208f950d.tar.gz | |
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/dss/dss.h')
| -rw-r--r-- | drivers/video/omap2/dss/dss.h | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/video/omap2/dss/dss.h b/drivers/video/omap2/dss/dss.h index 4d6f325..bdf8431 100644 --- a/drivers/video/omap2/dss/dss.h +++ b/drivers/video/omap2/dss/dss.h @@ -212,7 +212,6 @@ int dss_ovl_unset_manager(struct omap_overlay *ovl); /* output */ void dss_register_output(struct omap_dss_output *out); void dss_unregister_output(struct omap_dss_output *out); -struct omap_dss_output *omapdss_get_output_from_dssdev(struct omap_dss_device *dssdev); /* display */ int dss_suspend_all_devices(void); |
