Home
last modified time | relevance | path

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

/Linux-v5.4/drivers/media/usb/gspca/m5602/
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-v5.4/Documentation/media/uapi/v4l/
Dcontrol.rst27 controls using ``V4L2_CID_PRIVATE_BASE`` [#f1]_ and higher values. The
311 ``V4L2_CID_PRIVATE_BASE``
423 for (queryctrl.id = V4L2_CID_PRIVATE_BASE;;
500 The use of ``V4L2_CID_PRIVATE_BASE`` is problematic because different
501 drivers may use the same ``V4L2_CID_PRIVATE_BASE`` ID for different
505 ``V4L2_CID_PRIVATE_BASE`` IDs are mapped to those unique IDs by the
506 kernel. Consider these ``V4L2_CID_PRIVATE_BASE`` IDs as aliases to
509 Many applications today still use the ``V4L2_CID_PRIVATE_BASE`` IDs
512 support for ``V4L2_CID_PRIVATE_BASE`` is still around.
Dvidioc-queryctrl.rst60 ``V4L2_CID_PRIVATE_BASE`` and incrementing ``id`` until the driver
/Linux-v5.4/include/uapi/linux/
Dmatroxfb.h37 MATROXFB_CID_TESTOUT = V4L2_CID_PRIVATE_BASE,
Dvideodev2.h1786 #define V4L2_CID_PRIVATE_BASE 0x08000000 macro
/Linux-v5.4/drivers/media/v4l2-core/
Dv4l2-ctrls.c2198 id -= V4L2_CID_PRIVATE_BASE; in find_private_ref()
2223 if (id >= V4L2_CID_PRIVATE_BASE) in find_ref()
2433 id >= V4L2_CID_PRIVATE_BASE || in v4l2_ctrl_new()
3003 if (id >= V4L2_CID_PRIVATE_BASE) in v4l2_query_ext_ctrl()
3320 if (id >= V4L2_CID_PRIVATE_BASE) { in prepare_ext_ctrls()
Dv4l2-ioctl.c919 if (!allow_priv && c->which == V4L2_CID_PRIVATE_BASE) in check_ext_ctrls()
/Linux-v5.4/Documentation/media/
Dvideodev2.h.rst.exceptions364 replace define V4L2_CID_PRIVATE_BASE control