Home
last modified time | relevance | path

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

/linux-6.12.1/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-6.12.1/drivers/staging/media/atomisp/include/linux/
Datomisp.h838 (V4L2_CID_PRIVATE_BASE + 0)
840 (V4L2_CID_PRIVATE_BASE + 1)
842 (V4L2_CID_PRIVATE_BASE + 2)
844 (V4L2_CID_PRIVATE_BASE + 3)
846 (V4L2_CID_PRIVATE_BASE + 4)
848 (V4L2_CID_PRIVATE_BASE + 5)
/linux-6.12.1/Documentation/userspace-api/media/v4l/
Dcontrol.rst20 controls using ``V4L2_CID_PRIVATE_BASE`` [#f1]_ and higher values. The
320 ``V4L2_CID_PRIVATE_BASE``
432 for (queryctrl.id = V4L2_CID_PRIVATE_BASE;;
509 The use of ``V4L2_CID_PRIVATE_BASE`` is problematic because different
510 drivers may use the same ``V4L2_CID_PRIVATE_BASE`` ID for different
514 ``V4L2_CID_PRIVATE_BASE`` IDs are mapped to those unique IDs by the
515 kernel. Consider these ``V4L2_CID_PRIVATE_BASE`` IDs as aliases to
518 Many applications today still use the ``V4L2_CID_PRIVATE_BASE`` IDs
521 support for ``V4L2_CID_PRIVATE_BASE`` is still around.
Dvidioc-queryctrl.rst52 ``V4L2_CID_PRIVATE_BASE`` and incrementing ``id`` until the driver
/linux-6.12.1/include/uapi/linux/
Dmatroxfb.h37 MATROXFB_CID_TESTOUT = V4L2_CID_PRIVATE_BASE,
Dvideodev2.h2022 #define V4L2_CID_PRIVATE_BASE 0x08000000 macro
/linux-6.12.1/drivers/media/v4l2-core/
Dv4l2-ctrls-api.c245 if (id >= V4L2_CID_PRIVATE_BASE) { in prepare_ext_ctrls()
1103 if (id >= V4L2_CID_PRIVATE_BASE) in v4l2_query_ext_ctrl()
Dv4l2-ctrls-core.c1602 id -= V4L2_CID_PRIVATE_BASE; in find_private_ref()
1627 if (id >= V4L2_CID_PRIVATE_BASE) in find_ref()
1883 id >= V4L2_CID_PRIVATE_BASE || in v4l2_ctrl_new()
Dv4l2-ioctl.c885 case V4L2_CID_PRIVATE_BASE: in check_ext_ctrls()
/linux-6.12.1/Documentation/userspace-api/media/
Dvideodev2.h.rst.exceptions400 replace define V4L2_CID_PRIVATE_BASE control