Searched refs:V4L2_CID_PRIVATE_BASE (Results 1 – 14 of 14) 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)
20 controls using ``V4L2_CID_PRIVATE_BASE`` [#f1]_ and higher values. The304 ``V4L2_CID_PRIVATE_BASE``416 for (queryctrl.id = V4L2_CID_PRIVATE_BASE;;493 The use of ``V4L2_CID_PRIVATE_BASE`` is problematic because different494 drivers may use the same ``V4L2_CID_PRIVATE_BASE`` ID for different498 ``V4L2_CID_PRIVATE_BASE`` IDs are mapped to those unique IDs by the499 kernel. Consider these ``V4L2_CID_PRIVATE_BASE`` IDs as aliases to502 Many applications today still use the ``V4L2_CID_PRIVATE_BASE`` IDs505 support for ``V4L2_CID_PRIVATE_BASE`` is still around.
52 ``V4L2_CID_PRIVATE_BASE`` and incrementing ``id`` until the driver
1240 (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)
37 MATROXFB_CID_TESTOUT = V4L2_CID_PRIVATE_BASE,
1723 #define V4L2_CID_PRIVATE_BASE 0x08000000 macro
1858 #define V4L2_CID_PRIVATE_BASE 0x08000000 macro
2528 id -= V4L2_CID_PRIVATE_BASE; in find_private_ref()2553 if (id >= V4L2_CID_PRIVATE_BASE) in find_ref()2785 id >= V4L2_CID_PRIVATE_BASE || in v4l2_ctrl_new()3385 if (id >= V4L2_CID_PRIVATE_BASE) in v4l2_query_ext_ctrl()3679 if (id >= V4L2_CID_PRIVATE_BASE) { in prepare_ext_ctrls()
931 case V4L2_CID_PRIVATE_BASE: in check_ext_ctrls()
377 replace define V4L2_CID_PRIVATE_BASE control
1840 #define V4L2_CID_PRIVATE_BASE 0x08000000 macro