summaryrefslogtreecommitdiffstats
path: root/drivers/staging
diff options
context:
space:
mode:
authorHans Verkuil <hans.verkuil@cisco.com>2016-03-22 07:30:29 -0300
committerMauro Carvalho Chehab <mchehab@osg.samsung.com>2016-04-20 16:05:11 -0300
commitc5c631416789004e7205a56ab1aaab2b3a011b1b (patch)
treed1fa98f2a64144942a988b7d875d2c26e02a1568 /drivers/staging
parent0c53fee973a9adfa4ad21433d397adae12b2120b (diff)
downloadtalos-op-linux-c5c631416789004e7205a56ab1aaab2b3a011b1b.tar.gz
talos-op-linux-c5c631416789004e7205a56ab1aaab2b3a011b1b.zip
[media] vidioc-dv-timings-cap.xml: explicitly state that pad and reserved should be zeroed
The DV_TIMINGS_CAP documentation didn't state clearly that the pad and reserved fields should be zeroed by the application. For subdev pad can be other values as well. It also mistakenly said that only drivers would have to zero the reserved field, that's not correct. Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Diffstat (limited to 'drivers/staging')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud