summaryrefslogtreecommitdiffstats
path: root/MAINTAINERS
diff options
context:
space:
mode:
authorKevin Hilman <khilman@baylibre.com>2017-06-09 13:10:26 -0300
committerMauro Carvalho Chehab <mchehab@s-opensource.com>2017-06-20 09:05:37 -0300
commit479f7a1181058689435baddc16a6a42e1a8ff0e8 (patch)
tree1ba82ac7712bb71ab4b11f25cd43d4227937e849 /MAINTAINERS
parent72b7876c2e3b6087c72ce030d8145ec4a7328121 (diff)
downloadop-kernel-dev-479f7a1181058689435baddc16a6a42e1a8ff0e8.zip
op-kernel-dev-479f7a1181058689435baddc16a6a42e1a8ff0e8.tar.gz
[media] davinci: vpif: adaptions for DT support
The davinci VPIF is a single hardware block, but the existing driver is broken up into a common library (vpif.c), output (vpif_display.c) and intput (vpif_capture.c). When migrating to DT, to better model the hardware, and because registers, interrupts, etc. are all common,it was decided to have a single VPIF hardware node[1]. Because davinci uses legacy, non-DT boot on several SoCs still, the platform_drivers need to remain. But they are also needed in DT boot. Since there are no DT nodes for the display/capture parts in DT boot (there is a single node for the parent/common device) we need to create platform_devices somewhere to instantiate the platform_drivers. When VPIF display/capture are needed for a DT boot, the VPIF node will have endpoints defined for its subdevs. Therefore, vpif_probe() checks for the presence of endpoints, and if detected manually creates the platform_devices for the display and capture platform_drivers. [1] Documentation/devicetree/bindings/media/ti,da850-vpif.txt Signed-off-by: Kevin Hilman <khilman@baylibre.com> Signed-off-by: Hans Verkuil <hansverk@cisco.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud