diff options
author | Hans Verkuil <hans.verkuil@cisco.com> | 2012-05-10 08:36:00 (GMT) |
---|---|---|
committer | Mauro Carvalho Chehab <mchehab@redhat.com> | 2012-05-14 12:17:28 (GMT) |
commit | 48ea0be06028d97b57602372f032afbec02e7e97 (patch) | |
tree | e4d089a40163ba3491b0d5989048cec29ccbba17 /drivers/rapidio | |
parent | 8ab75e3ecd8f232d9564510f0c601a6aa7a149ea (diff) | |
download | linux-fsl-qoriq-48ea0be06028d97b57602372f032afbec02e7e97.tar.xz |
[media] v4l2-dev/ioctl: determine the valid ioctls upfront
Rather than testing whether an ioctl is implemented in the driver or not
every time the ioctl is called, do it upfront when the device is registered.
This also allows a driver to disable certain ioctls based on the capabilities
of the detected board, something you can't do today without creating separate
v4l2_ioctl_ops structs for each new variation.
For the most part it is pretty straightforward, but for control ioctls a flag
is needed since it is possible that you have per-filehandle controls, and that
can't be determined upfront of course.
Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
Acked-by: Hans de Goede <hdegoede@redhat.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'drivers/rapidio')
0 files changed, 0 insertions, 0 deletions