summaryrefslogtreecommitdiffstats
path: root/include/drm/drm_crtc.h
diff options
context:
space:
mode:
authorThierry Reding <treding@nvidia.com>2014-01-09 17:08:36 +0100
committerThierry Reding <treding@nvidia.com>2014-01-23 15:51:32 +0100
commit13411ddd319057ae334a4084ebcf2c741b317f34 (patch)
tree9915698fb7fe169acd53b9b7f75347524ed04a98 /include/drm/drm_crtc.h
parent70bf6878a874523e4b62992d07b5739298f8c1eb (diff)
downloadlinux-stable-13411ddd319057ae334a4084ebcf2c741b317f34.tar.gz
linux-stable-13411ddd319057ae334a4084ebcf2c741b317f34.tar.bz2
linux-stable-13411ddd319057ae334a4084ebcf2c741b317f34.zip
drm/tegra: Obtain head number from DT
The head number of a given display controller is fixed in hardware and required to program outputs appropriately. Relying on the driver probe order to determine this number will not work, since that could yield a situation where the second head was probed first and would be assigned head number 0 instead of 1. By explicitly specifying the head number in the device tree, it is no longer necessary to rely on these assumptions. As a fallback, if the property isn't available, derive the head number from the display controller node's position in the device tree. That's somewhat more reliable than the previous default but not a proper solution. Tested-by: Stephen Warren <swarren@nvidia.com> Signed-off-by: Thierry Reding <treding@nvidia.com>
Diffstat (limited to 'include/drm/drm_crtc.h')
0 files changed, 0 insertions, 0 deletions