Searched refs:V4L2_CID_PRIVATE_BASE (Results 1 – 10 of 10) sorted by relevance
20 #define M5602_V4L2_CID_GREEN_BALANCE (V4L2_CID_PRIVATE_BASE + 0)21 #define M5602_V4L2_CID_NOISE_SUPPRESION (V4L2_CID_PRIVATE_BASE + 1)
827 (V4L2_CID_PRIVATE_BASE + 0)829 (V4L2_CID_PRIVATE_BASE + 1)831 (V4L2_CID_PRIVATE_BASE + 2)833 (V4L2_CID_PRIVATE_BASE + 3)835 (V4L2_CID_PRIVATE_BASE + 4)837 (V4L2_CID_PRIVATE_BASE + 5)
20 controls using ``V4L2_CID_PRIVATE_BASE`` [#f1]_ and higher values. The322 ``V4L2_CID_PRIVATE_BASE``434 for (queryctrl.id = V4L2_CID_PRIVATE_BASE;;511 The use of ``V4L2_CID_PRIVATE_BASE`` is problematic because different512 drivers may use the same ``V4L2_CID_PRIVATE_BASE`` ID for different516 ``V4L2_CID_PRIVATE_BASE`` IDs are mapped to those unique IDs by the517 kernel. Consider these ``V4L2_CID_PRIVATE_BASE`` IDs as aliases to520 Many applications today still use the ``V4L2_CID_PRIVATE_BASE`` IDs523 support for ``V4L2_CID_PRIVATE_BASE`` is still around.
52 ``V4L2_CID_PRIVATE_BASE`` and incrementing ``id`` until the driver
37 MATROXFB_CID_TESTOUT = V4L2_CID_PRIVATE_BASE,
2033 #define V4L2_CID_PRIVATE_BASE 0x08000000 macro
261 if (id >= V4L2_CID_PRIVATE_BASE) { in prepare_ext_ctrls()1137 if (id >= V4L2_CID_PRIVATE_BASE) in v4l2_query_ext_ctrl()
1681 id -= V4L2_CID_PRIVATE_BASE; in find_private_ref()1706 if (id >= V4L2_CID_PRIVATE_BASE) in find_ref()1974 id >= V4L2_CID_PRIVATE_BASE || in v4l2_ctrl_new()
885 case V4L2_CID_PRIVATE_BASE: in check_ext_ctrls()
403 replace define V4L2_CID_PRIVATE_BASE control