aboutsummaryrefslogtreecommitdiffstats
path: root/include/video
diff options
context:
space:
mode:
authorArchit Taneja <archit@ti.com>2014-05-22 17:01:57 +0530
committerTomi Valkeinen <tomi.valkeinen@ti.com>2014-11-12 13:40:01 +0200
commit387ce9f2f2bd78436538deab9ece94512e362deb (patch)
tree47518c74b682b67b3e1c98db97569ff2917d4314 /include/video
parentOMAPDSS: DPI: Store dpi_data pointer in the DT port's data (diff)
downloadlinux-dev-387ce9f2f2bd78436538deab9ece94512e362deb.tar.xz
linux-dev-387ce9f2f2bd78436538deab9ece94512e362deb.zip
OMAPDSS: DSS: init dss ports cleanly
The init/uninit port functions are used to set up the DPI and SDI outputs under the dss platform device. A 'reg' property is used to determine the port number of the output. This tells us whether the port is DPI or SDI for OMAP34xx DSS revision. For other DSS revisions, we only have DPI outputs under the dss platform device. For multiple DPI output instances(introduced in DRA7xx DSS), we will use the the port number to specify which DPI output instance is being inited. The current functions work fine if there is only one DPI output instance in DSS. For multiple DPI instances, it would get complicated to figure out whether port number was used to specify whether the output is SDI, or another DPI instance. We create a list of port types supported for each DSS rev, with the index of the port in the list specifying the port number of the output for that DSS revision. This allows us to have a more generic way to init/uninit ports within DSS, and also support multiple DPI ports. We make the uninit_port functions iterative since we will have multiple DPI ports to uninit in the future. Signed-off-by: Archit Taneja <archit@ti.com> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Diffstat (limited to 'include/video')
0 files changed, 0 insertions, 0 deletions