| commit | 3e22b355343d808bb09cc47b5ecb261af3b5753b | |
| author | Tomi Valkeinen <tomi.valkeinen@ti.com> | |
| Tue, 6 Aug 2013 06:50:22 +0000 (6 09:50 +0300) | ||
| committer | Tomi Valkeinen <tomi.valkeinen@ti.com> | |
| Wed, 19 Mar 2014 09:03:05 +0000 (19 11:03 +0200) | ||
| tree | 12bf66dfe5a5c33ae5c0fc40b676c83fa20fa325 | treesnapshot (tar.gz zip) |
| parent | 7f2bcd06558a40deecd4a294acbd0b3f659be911 | commitdiff |
OMAPDSS: get dssdev->alias from DT alias
We currently create a "displayX" style alias name for all displays,
using a number that is incremented for each registered display. With the
new DSS device model there is no clear order in which the displays are
registered, and thus the numbering is somewhat random.
This patch improves the behavior for DT case so that if the displays
have been assigned DT aliases, those aliases will be used as DSS
aliases.
This means that "display0" is always the one specified in the DT alias,
and thus display0 can be used as default display in case the user didn't
specify a default display.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Reviewed-by: Archit Taneja <archit@ti.com>
We currently create a "displayX" style alias name for all displays,
using a number that is incremented for each registered display. With the
new DSS device model there is no clear order in which the displays are
registered, and thus the numbering is somewhat random.
This patch improves the behavior for DT case so that if the displays
have been assigned DT aliases, those aliases will be used as DSS
aliases.
This means that "display0" is always the one specified in the DT alias,
and thus display0 can be used as default display in case the user didn't
specify a default display.
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Reviewed-by: Archit Taneja <archit@ti.com>
| drivers/video/omap2/dss/display.c | diffblobblamehistory |