Home
last modified time | relevance | path

Searched full:capabilities (Results 1 – 25 of 3281) sorted by relevance

12345678910>>...132

/kernel/linux/linux-5.10/Documentation/userspace-api/media/
Dvideodev2.h.rst.exceptions150 replace define V4L2_CAP_VIDEO_CAPTURE device-capabilities
151 replace define V4L2_CAP_VIDEO_CAPTURE_MPLANE device-capabilities
152 replace define V4L2_CAP_VIDEO_OUTPUT device-capabilities
153 replace define V4L2_CAP_VIDEO_OUTPUT_MPLANE device-capabilities
154 replace define V4L2_CAP_VIDEO_M2M device-capabilities
155 replace define V4L2_CAP_VIDEO_M2M_MPLANE device-capabilities
156 replace define V4L2_CAP_VIDEO_OVERLAY device-capabilities
157 replace define V4L2_CAP_VBI_CAPTURE device-capabilities
158 replace define V4L2_CAP_VBI_OUTPUT device-capabilities
159 replace define V4L2_CAP_SLICED_VBI_CAPTURE device-capabilities
[all …]
/kernel/linux/linux-4.19/Documentation/media/
Dvideodev2.h.rst.exceptions136 replace define V4L2_CAP_VIDEO_CAPTURE device-capabilities
137 replace define V4L2_CAP_VIDEO_CAPTURE_MPLANE device-capabilities
138 replace define V4L2_CAP_VIDEO_OUTPUT device-capabilities
139 replace define V4L2_CAP_VIDEO_OUTPUT_MPLANE device-capabilities
140 replace define V4L2_CAP_VIDEO_M2M device-capabilities
141 replace define V4L2_CAP_VIDEO_M2M_MPLANE device-capabilities
142 replace define V4L2_CAP_VIDEO_OVERLAY device-capabilities
143 replace define V4L2_CAP_VBI_CAPTURE device-capabilities
144 replace define V4L2_CAP_VBI_OUTPUT device-capabilities
145 replace define V4L2_CAP_SLICED_VBI_CAPTURE device-capabilities
[all …]
/kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/
Dvidioc-querycap.rst13 VIDIOC_QUERYCAP - Query device capabilities
36 information about driver and hardware capabilities. The ioctl takes a
105 - ``capabilities``
106 - Available capabilities of the physical device as a whole, see
107 :ref:`device-capabilities`. The same physical device can export
109 /dev/radioZ). The ``capabilities`` field should contain a union of
110 all capabilities available around the several V4L2 devices
111 exported to userspace. For all those devices the ``capabilities``
112 field returns the same set of capabilities. This allows
118 - Device capabilities of the opened device, see
[all …]
Dvidioc-dv-timings-cap.rst13 VIDIOC_DV_TIMINGS_CAP - VIDIOC_SUBDEV_DV_TIMINGS_CAP - The capabilities of the Digital Video receiv…
38 To query the capabilities of the DV receiver/transmitter applications
49 When implemented by the driver DV capabilities of subdevices can be
51 on a subdevice node. The capabilities are specific to inputs (for DV
55 zero the ``reserved`` array. Attempts to query capabilities on a pad
90 - ``capabilities``
91 - Several flags giving more information about the capabilities. See
92 :ref:`dv-bt-cap-capabilities` for a description of the flags.
125 - BT.656/1120 timings capabilities of the hardware.
133 .. _dv-bt-cap-capabilities:
[all …]
Dvidioc-subdev-querycap.rst13 VIDIOC_SUBDEV_QUERYCAP - Query sub-device capabilities
36 information about driver and hardware capabilities. The ioctl takes a pointer to
71 - ``capabilities``
72 - Sub-device capabilities of the opened device, see
73 :ref:`subdevice-capabilities`.
80 .. _subdevice-capabilities:
84 .. flat-table:: Sub-Device Capabilities Flags
/kernel/linux/linux-4.19/Documentation/media/uapi/v4l/
Dvidioc-querycap.rst12 VIDIOC_QUERYCAP - Query device capabilities
37 information about driver and hardware capabilities. The ioctl takes a
107 - ``capabilities``
108 - Available capabilities of the physical device as a whole, see
109 :ref:`device-capabilities`. The same physical device can export
111 /dev/radioZ). The ``capabilities`` field should contain a union of
112 all capabilities available around the several V4L2 devices
113 exported to userspace. For all those devices the ``capabilities``
114 field returns the same set of capabilities. This allows
120 - Device capabilities of the opened device, see
[all …]
Dvidioc-dv-timings-cap.rst12 VIDIOC_DV_TIMINGS_CAP - VIDIOC_SUBDEV_DV_TIMINGS_CAP - The capabilities of the Digital Video receiv…
38 To query the capabilities of the DV receiver/transmitter applications
49 When implemented by the driver DV capabilities of subdevices can be
51 on a subdevice node. The capabilities are specific to inputs (for DV
55 zero the ``reserved`` array. Attempts to query capabilities on a pad
91 - ``capabilities``
92 - Several flags giving more information about the capabilities. See
93 :ref:`dv-bt-cap-capabilities` for a description of the flags.
129 - BT.656/1120 timings capabilities of the hardware.
137 .. _dv-bt-cap-capabilities:
[all …]
/kernel/linux/linux-4.19/Documentation/
Dlsm.txt35 migrating the Linux capabilities code into such a module.
44 of the framework and the example capabilities security module provided
56 also moves most of the capabilities logic into an optional security
58 This capabilities module is discussed further in
59 `LSM Capabilities Module <#cap>`__.
157 LSM Capabilities Module
160 The LSM kernel patch moves most of the existing POSIX.1e capabilities
163 use capabilities to omit this code entirely from their kernel, instead
166 capabilities logic to maintain and enhance their code more freely,
169 In addition to moving the capabilities logic, the LSM kernel patch could
[all …]
/kernel/linux/linux-5.10/Documentation/userspace-api/media/dvb/
Dfe-get-info.rst13 FE_GET_INFO - Query Digital TV frontend capabilities and returns information
37 obtain information about driver and hardware capabilities. The ioctl
42 frontend capabilities
45 Capabilities describe what a frontend can do. Some capabilities are
48 The frontend capabilities are described at :c:type:`fe_caps`.
/kernel/linux/linux-4.19/Documentation/media/uapi/dvb/
Dfe-get-info.rst12 FE_GET_INFO - Query Digital TV frontend capabilities and returns information
39 obtain information about driver and hardware capabilities. The ioctl
45 frontend capabilities
48 Capabilities describe what a frontend can do. Some capabilities are
51 The frontend capabilities are described at :c:type:`fe_caps`.
/kernel/linux/linux-5.10/Documentation/admin-guide/LSM/
DSafeSetID.rst13 In absence of file capabilities, processes spawned on a Linux system that need
17 often preferable to use Linux runtime capabilities rather than file
18 capabilities, since using file capabilities to run a program with elevated
23 CAP_SET{U/G}ID capabilities, this is often at odds with the goals of running a
32 capabilities in such a way.
35 other untrusted uids without full blown CAP_SETUID capabilities. The non-root
53 For candidate applications that would like to have restricted setid capabilities
55 setid capabilities from the application completely and refactor the process
69 namespace and give programs in the tree setid capabilities. In this way,
75 Linux checks for capabilities based off of the user namespace that "owns" some
/kernel/linux/linux-5.10/drivers/gpu/drm/vmwgfx/
Dvmwgfx_drv.c297 static void vmw_print_capabilities(uint32_t capabilities) in vmw_print_capabilities() argument
299 DRM_INFO("Capabilities:\n"); in vmw_print_capabilities()
300 if (capabilities & SVGA_CAP_RECT_COPY) in vmw_print_capabilities()
302 if (capabilities & SVGA_CAP_CURSOR) in vmw_print_capabilities()
304 if (capabilities & SVGA_CAP_CURSOR_BYPASS) in vmw_print_capabilities()
306 if (capabilities & SVGA_CAP_CURSOR_BYPASS_2) in vmw_print_capabilities()
308 if (capabilities & SVGA_CAP_8BIT_EMULATION) in vmw_print_capabilities()
310 if (capabilities & SVGA_CAP_ALPHA_CURSOR) in vmw_print_capabilities()
312 if (capabilities & SVGA_CAP_3D) in vmw_print_capabilities()
314 if (capabilities & SVGA_CAP_EXTENDED_FIFO) in vmw_print_capabilities()
[all …]
/kernel/liteos_a/security/cap/
Dcapability_type.h35 // posix capabilities
45 // socket capabilities
51 // fs capabilities
55 // process capabilities
58 // time capabilities
62 // process capabilities
/kernel/linux/linux-4.19/kernel/
Dcapability.c24 * Leveraged for setting/resetting capabilities
50 pr_info_once("warning: `%s' uses 32-bit capabilities (legacy support in use)\n", in warn_legacy_capability_use()
55 * Version 2 capabilities worked fine, but the linux/capability.h file
62 * capabilities and may be doing so insecurely.
74 pr_info_once("warning: `%s' uses deprecated v2 capabilities in a way that may be insecure\n", in warn_deprecated_v2()
112 * The only thing that can change the capabilities of the current
114 * at the same time as we are in the process of setting capabilities
142 * sys_capget - get the capabilities of a given process.
146 * and inheritable capabilities that are returned
180 * we silently drop the upper capabilities here. This in SYSCALL_DEFINE2()
[all …]
/kernel/linux/linux-5.10/kernel/
Dcapability.c24 * Leveraged for setting/resetting capabilities
50 pr_info_once("warning: `%s' uses 32-bit capabilities (legacy support in use)\n", in warn_legacy_capability_use()
55 * Version 2 capabilities worked fine, but the linux/capability.h file
62 * capabilities and may be doing so insecurely.
74 pr_info_once("warning: `%s' uses deprecated v2 capabilities in a way that may be insecure\n", in warn_deprecated_v2()
110 * The only thing that can change the capabilities of the current
112 * at the same time as we are in the process of setting capabilities
140 * sys_capget - get the capabilities of a given process.
144 * and inheritable capabilities that are returned
178 * we silently drop the upper capabilities here. This in SYSCALL_DEFINE2()
[all …]
/kernel/linux/linux-5.10/Documentation/security/
Dlsm.rst35 migrating the Linux capabilities code into such a module.
43 report provides an overview of the framework and the capabilities
55 optional, requiring `CONFIG_SECURITY` to be enabled. The capabilities
57 This capabilities module is discussed further in
58 `LSM Capabilities Module`_.
122 LSM Capabilities Module
125 The POSIX.1e capabilities logic is maintained as a security module
126 stored in the file ``security/commoncap.c``. The capabilities
129 The capabilities security module does not use the general security
/kernel/linux/linux-5.10/drivers/net/ethernet/mellanox/mlx5/core/lib/
Dhv_vhca.c133 u32 *capabilities) in mlx5_hv_vhca_capabilities() argument
141 *capabilities |= AGENT_MASK(agent->type); in mlx5_hv_vhca_capabilities()
152 u32 capabilities = 0; in mlx5_hv_vhca_control_agent_invalidate() local
163 mlx5_hv_vhca_capabilities(hv_vhca, &capabilities); in mlx5_hv_vhca_control_agent_invalidate()
165 /* In case no capabilities, send empty block in return */ in mlx5_hv_vhca_control_agent_invalidate()
166 if (!capabilities) { in mlx5_hv_vhca_control_agent_invalidate()
171 if (block->capabilities != capabilities) in mlx5_hv_vhca_control_agent_invalidate()
172 block->capabilities = capabilities; in mlx5_hv_vhca_control_agent_invalidate()
174 if (block->control & ~capabilities) in mlx5_hv_vhca_control_agent_invalidate()
/kernel/linux/linux-4.19/drivers/gpu/drm/vmwgfx/
Dvmwgfx_drv.c282 static void vmw_print_capabilities(uint32_t capabilities) in vmw_print_capabilities() argument
284 DRM_INFO("Capabilities:\n"); in vmw_print_capabilities()
285 if (capabilities & SVGA_CAP_RECT_COPY) in vmw_print_capabilities()
287 if (capabilities & SVGA_CAP_CURSOR) in vmw_print_capabilities()
289 if (capabilities & SVGA_CAP_CURSOR_BYPASS) in vmw_print_capabilities()
291 if (capabilities & SVGA_CAP_CURSOR_BYPASS_2) in vmw_print_capabilities()
293 if (capabilities & SVGA_CAP_8BIT_EMULATION) in vmw_print_capabilities()
295 if (capabilities & SVGA_CAP_ALPHA_CURSOR) in vmw_print_capabilities()
297 if (capabilities & SVGA_CAP_3D) in vmw_print_capabilities()
299 if (capabilities & SVGA_CAP_EXTENDED_FIFO) in vmw_print_capabilities()
[all …]
/kernel/linux/linux-5.10/security/
Dcommoncap.c2 /* Common capabilities, needed by capability.o.
30 * !secure(SECURE_NOROOT) mode, then we raise capabilities.
32 * the file capabilities to be applied, and the setuid-root
34 * to get full privilege on a kernel without file capabilities
35 * support. So in that case we do not raise capabilities.
44 " effective capabilities. Therefore not raising all" in warn_setuid_and_fcaps_mixed()
45 " capabilities.\n", fname); in warn_setuid_and_fcaps_mixed()
75 /* Do we have the necessary capabilities? */ in cap_capable()
125 * task's capabilities, then ptrace access is allowed.
162 * capabilities, then ptrace access is allowed.
[all …]
/kernel/linux/linux-4.19/sound/usb/line6/
Dpodhd.c300 if (pod->line6.properties->capabilities & LINE6_CAP_CONTROL_INFO) { in podhd_disconnect()
328 if (pod->line6.properties->capabilities & LINE6_CAP_CONTROL) { in podhd_init()
346 if (pod->line6.properties->capabilities & LINE6_CAP_CONTROL_INFO) { in podhd_init()
353 if (pod->line6.properties->capabilities & LINE6_CAP_PCM) { in podhd_init()
363 if (!(pod->line6.properties->capabilities & LINE6_CAP_CONTROL_INFO)) { in podhd_init()
396 .capabilities = LINE6_CAP_PCM
407 .capabilities = LINE6_CAP_PCM
418 .capabilities = LINE6_CAP_PCM
429 .capabilities = LINE6_CAP_PCM
440 .capabilities = LINE6_CAP_CONTROL | LINE6_CAP_CONTROL_INFO
[all …]
/kernel/linux/linux-4.19/security/
Dcommoncap.c1 /* Common capabilities, needed by capability.o.
36 * !secure(SECURE_NOROOT) mode, then we raise capabilities.
38 * the file capabilities to be applied, and the setuid-root
40 * to get full privilege on a kernel without file capabilities
41 * support. So in that case we do not raise capabilities.
50 " effective capabilities. Therefore not raising all" in warn_setuid_and_fcaps_mixed()
51 " capabilities.\n", fname); in warn_setuid_and_fcaps_mixed()
81 /* Do we have the necessary capabilities? */ in cap_capable()
131 * task's capabilities, then ptrace access is allowed.
168 * capabilities, then ptrace access is allowed.
[all …]
/kernel/linux/linux-5.10/drivers/staging/media/sunxi/cedrus/
Dcedrus_video.c49 .capabilities = CEDRUS_CAPABILITY_H265_DEC,
58 .capabilities = CEDRUS_CAPABILITY_UNTILED,
70 unsigned int capabilities) in cedrus_find_format() argument
79 if ((fmt->capabilities & capabilities) != fmt->capabilities || in cedrus_find_format()
173 unsigned int capabilities = dev->capabilities; in cedrus_enum_fmt() local
183 if (fmt->capabilities && (fmt->capabilities & capabilities) != in cedrus_enum_fmt()
184 fmt->capabilities) in cedrus_enum_fmt()
244 dev->capabilities); in cedrus_try_fmt_vid_cap()
265 dev->capabilities); in cedrus_try_fmt_vid_out()
/kernel/linux/linux-4.19/Documentation/media/uapi/cec/
Dcec-ioc-adap-g-caps.rst12 CEC_ADAP_G_CAPS - Query device capabilities
54 - ``capabilities``
55 - The capabilities of the CEC adapter, see
56 :ref:`cec-capabilities`.
65 .. _cec-capabilities:
67 .. flat-table:: CEC Capabilities Flags
/kernel/linux/linux-5.10/Documentation/userspace-api/media/cec/
Dcec-ioc-adap-g-caps.rst13 CEC_ADAP_G_CAPS - Query device capabilities
58 - ``capabilities``
59 - The capabilities of the CEC adapter, see
60 :ref:`cec-capabilities`.
68 .. _cec-capabilities:
70 .. flat-table:: CEC Capabilities Flags
/kernel/linux/linux-4.19/fs/cifs/
Dsess.c37 __u32 capabilities = 0; in cifs_ssetup_hdr() local
56 capabilities = CAP_LARGE_FILES | CAP_NT_SMBS | CAP_LEVEL_II_OPLOCKS | in cifs_ssetup_hdr()
62 if (ses->capabilities & CAP_UNICODE) { in cifs_ssetup_hdr()
64 capabilities |= CAP_UNICODE; in cifs_ssetup_hdr()
66 if (ses->capabilities & CAP_STATUS32) { in cifs_ssetup_hdr()
68 capabilities |= CAP_STATUS32; in cifs_ssetup_hdr()
70 if (ses->capabilities & CAP_DFS) { in cifs_ssetup_hdr()
72 capabilities |= CAP_DFS; in cifs_ssetup_hdr()
74 if (ses->capabilities & CAP_UNIX) in cifs_ssetup_hdr()
75 capabilities |= CAP_UNIX; in cifs_ssetup_hdr()
[all …]

12345678910>>...132