Home
last modified time | relevance | path

Searched refs:V4L2_CID_PRIVATE_BASE (Results 1 – 10 of 10) sorted by relevance

/linux/drivers/media/usb/gspca/m5602/
A Dm5602_sensor.h20 #define M5602_V4L2_CID_GREEN_BALANCE (V4L2_CID_PRIVATE_BASE + 0)
21 #define M5602_V4L2_CID_NOISE_SUPPRESION (V4L2_CID_PRIVATE_BASE + 1)
/linux/Documentation/userspace-api/media/v4l/
A Dcontrol.rst20 controls using ``V4L2_CID_PRIVATE_BASE`` [#f1]_ and higher values. The
307 ``V4L2_CID_PRIVATE_BASE``
419 for (queryctrl.id = V4L2_CID_PRIVATE_BASE;;
496 The use of ``V4L2_CID_PRIVATE_BASE`` is problematic because different
497 drivers may use the same ``V4L2_CID_PRIVATE_BASE`` ID for different
501 ``V4L2_CID_PRIVATE_BASE`` IDs are mapped to those unique IDs by the
502 kernel. Consider these ``V4L2_CID_PRIVATE_BASE`` IDs as aliases to
505 Many applications today still use the ``V4L2_CID_PRIVATE_BASE`` IDs
508 support for ``V4L2_CID_PRIVATE_BASE`` is still around.
A Dvidioc-queryctrl.rst52 ``V4L2_CID_PRIVATE_BASE`` and incrementing ``id`` until the driver
/linux/drivers/staging/media/atomisp/include/linux/
A Datomisp.h1240 (V4L2_CID_PRIVATE_BASE + 0)
1242 (V4L2_CID_PRIVATE_BASE + 1)
1244 (V4L2_CID_PRIVATE_BASE + 2)
1246 (V4L2_CID_PRIVATE_BASE + 3)
1248 (V4L2_CID_PRIVATE_BASE + 4)
1250 (V4L2_CID_PRIVATE_BASE + 5)
/linux/include/uapi/linux/
A Dmatroxfb.h37 MATROXFB_CID_TESTOUT = V4L2_CID_PRIVATE_BASE,
A Dvideodev2.h1889 #define V4L2_CID_PRIVATE_BASE 0x08000000 macro
/linux/drivers/media/v4l2-core/
A Dv4l2-ctrls-api.c236 if (id >= V4L2_CID_PRIVATE_BASE) { in prepare_ext_ctrls()
1013 if (id >= V4L2_CID_PRIVATE_BASE) in v4l2_query_ext_ctrl()
A Dv4l2-ctrls-core.c1005 id -= V4L2_CID_PRIVATE_BASE; in find_private_ref()
1030 if (id >= V4L2_CID_PRIVATE_BASE) in find_ref()
1270 id >= V4L2_CID_PRIVATE_BASE || in v4l2_ctrl_new()
A Dv4l2-ioctl.c882 case V4L2_CID_PRIVATE_BASE: in check_ext_ctrls()
/linux/Documentation/userspace-api/media/
A Dvideodev2.h.rst.exceptions383 replace define V4L2_CID_PRIVATE_BASE control

Completed in 36 milliseconds