Home
last modified time | relevance | path

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

12345678910>>...81

/Linux-v5.15/Documentation/userspace-api/media/
Dvideodev2.h.rst.exceptions156 replace define V4L2_CAP_VIDEO_CAPTURE device-capabilities
157 replace define V4L2_CAP_VIDEO_CAPTURE_MPLANE device-capabilities
158 replace define V4L2_CAP_VIDEO_OUTPUT device-capabilities
159 replace define V4L2_CAP_VIDEO_OUTPUT_MPLANE device-capabilities
160 replace define V4L2_CAP_VIDEO_M2M device-capabilities
161 replace define V4L2_CAP_VIDEO_M2M_MPLANE device-capabilities
162 replace define V4L2_CAP_VIDEO_OVERLAY device-capabilities
163 replace define V4L2_CAP_VBI_CAPTURE device-capabilities
164 replace define V4L2_CAP_VBI_OUTPUT device-capabilities
165 replace define V4L2_CAP_SLICED_VBI_CAPTURE device-capabilities
[all …]
/Linux-v5.15/Documentation/userspace-api/media/v4l/
Dvidioc-querycap.rst13 VIDIOC_QUERYCAP - Query device capabilities
36 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.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
Dvidioc-create-bufs.rst103 - ``capabilities``
105 capabilities. In that case all you know is that the driver is
108 capabilities. See :ref:`here <v4l2-buf-capabilities>` for a list of the
109 capabilities.
111 If you want to just query the capabilities without making any
/Linux-v5.15/fs/ksmbd/
Dsmb2ops.c19 .capabilities = SMB2_GLOBAL_CAP_LARGE_MTU,
44 .capabilities = SMB2_GLOBAL_CAP_LARGE_MTU,
70 .capabilities = SMB2_GLOBAL_CAP_LARGE_MTU,
96 .capabilities = SMB2_GLOBAL_CAP_LARGE_MTU,
205 conn->vals->capabilities |= SMB2_GLOBAL_CAP_LEASING; in init_smb2_1_server()
223 conn->vals->capabilities |= SMB2_GLOBAL_CAP_LEASING; in init_smb3_0_server()
227 conn->vals->capabilities |= SMB2_GLOBAL_CAP_ENCRYPTION; in init_smb3_0_server()
230 conn->vals->capabilities |= SMB2_GLOBAL_CAP_MULTI_CHANNEL; in init_smb3_0_server()
248 conn->vals->capabilities |= SMB2_GLOBAL_CAP_LEASING; in init_smb3_02_server()
252 conn->vals->capabilities |= SMB2_GLOBAL_CAP_ENCRYPTION; in init_smb3_02_server()
[all …]
/Linux-v5.15/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`.
/Linux-v5.15/tools/testing/selftests/kvm/x86_64/
Dvmx_pmu_msrs_test.c50 u64 capabilities; member
69 host_cap.capabilities = kvm_get_feature_msr(MSR_IA32_PERF_CAPABILITIES); in main()
70 host_cap.capabilities &= (PMU_CAP_FW_WRITES | PMU_CAP_LBR_FMT); in main()
91 /* testcase 1, set capabilities when we have PDCM bit */ in main()
95 /* check capabilities can be retrieved with KVM_GET_MSR */ in main()
113 /* testcase 4, set capabilities when we don't have PDCM bit */ in main()
116 ret = _vcpu_set_msr(vm, 0, MSR_IA32_PERF_CAPABILITIES, host_cap.capabilities); in main()
119 /* testcase 5, set capabilities when we don't have PMU version bits */ in main()
/Linux-v5.15/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
/Linux-v5.15/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 …]
/Linux-v5.15/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
/Linux-v5.15/drivers/staging/media/sunxi/cedrus/
Dcedrus_video.c41 .capabilities = CEDRUS_CAPABILITY_MPEG2_DEC,
46 .capabilities = CEDRUS_CAPABILITY_H264_DEC,
51 .capabilities = CEDRUS_CAPABILITY_H265_DEC,
56 .capabilities = CEDRUS_CAPABILITY_VP8_DEC,
65 .capabilities = CEDRUS_CAPABILITY_UNTILED,
77 unsigned int capabilities) in cedrus_find_format() argument
86 if ((fmt->capabilities & capabilities) != fmt->capabilities || in cedrus_find_format()
181 unsigned int capabilities = dev->capabilities; in cedrus_enum_fmt() local
191 if (fmt->capabilities && (fmt->capabilities & capabilities) != in cedrus_enum_fmt()
192 fmt->capabilities) in cedrus_enum_fmt()
[all …]
/Linux-v5.15/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()
/Linux-v5.15/drivers/crypto/qat/qat_common/
Dadf_gen2_hw_data.c162 u32 capabilities = ICP_ACCEL_CAPABILITIES_CRYPTO_SYMMETRIC | in adf_gen2_get_accel_cap() local
166 /* Read accelerator capabilities mask */ in adf_gen2_get_accel_cap()
170 capabilities &= ~ICP_ACCEL_CAPABILITIES_CRYPTO_SYMMETRIC; in adf_gen2_get_accel_cap()
172 capabilities &= ~ICP_ACCEL_CAPABILITIES_CRYPTO_ASYMMETRIC; in adf_gen2_get_accel_cap()
174 capabilities &= ~ICP_ACCEL_CAPABILITIES_AUTHENTICATION; in adf_gen2_get_accel_cap()
177 capabilities &= ~ICP_ACCEL_CAPABILITIES_CRYPTO_ASYMMETRIC; in adf_gen2_get_accel_cap()
179 return capabilities; in adf_gen2_get_accel_cap()
/Linux-v5.15/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 …]
/Linux-v5.15/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
/Linux-v5.15/drivers/crypto/qat/qat_dh895xcc/
Dadf_dh895xcc_hw_data.c84 u32 capabilities; in get_accel_cap() local
87 capabilities = ICP_ACCEL_CAPABILITIES_CRYPTO_SYMMETRIC | in get_accel_cap()
91 /* Read accelerator capabilities mask */ in get_accel_cap()
95 capabilities &= ~ICP_ACCEL_CAPABILITIES_CRYPTO_SYMMETRIC; in get_accel_cap()
97 capabilities &= ~ICP_ACCEL_CAPABILITIES_CRYPTO_ASYMMETRIC; in get_accel_cap()
99 capabilities &= ~ICP_ACCEL_CAPABILITIES_AUTHENTICATION; in get_accel_cap()
101 return capabilities; in get_accel_cap()
/Linux-v5.15/drivers/staging/most/i2c/
Di2c.c36 struct most_channel_capability capabilities[NUM_CHANNELS]; member
78 if (channel_config->direction != dev->capabilities[ch_idx].direction) { in configure_channel()
301 dev->capabilities[i].data_type = MOST_CH_CONTROL; in i2c_probe()
302 dev->capabilities[i].num_buffers_packet = MAX_BUFFERS_CONTROL; in i2c_probe()
303 dev->capabilities[i].buffer_size_packet = MAX_BUF_SIZE_CONTROL; in i2c_probe()
305 dev->capabilities[CH_RX].direction = MOST_CH_RX; in i2c_probe()
306 dev->capabilities[CH_RX].name_suffix = "rx"; in i2c_probe()
307 dev->capabilities[CH_TX].direction = MOST_CH_TX; in i2c_probe()
308 dev->capabilities[CH_TX].name_suffix = "tx"; in i2c_probe()
313 dev->most_iface.channel_vector = dev->capabilities; in i2c_probe()
/Linux-v5.15/drivers/staging/greybus/
Dgb-camera.h52 * @capabilities: Retrieve camera capabilities and store them in the buffer
53 * 'buf' capabilities. The buffer maximum size is specified by
55 * capabilities size is returned from the function. If the buffer
56 * size is too small to hold the capabilities an error is
90 ssize_t (*capabilities)(void *priv, char *buf, size_t len); member
/Linux-v5.15/sound/usb/line6/
Dpodhd.c242 if (pod->line6.properties->capabilities & LINE6_CAP_CONTROL_INFO) { in podhd_disconnect()
375 if (pod->line6.properties->capabilities & LINE6_CAP_CONTROL) { in podhd_init()
393 if (pod->line6.properties->capabilities & LINE6_CAP_CONTROL_INFO) { in podhd_init()
400 if (pod->line6.properties->capabilities & LINE6_CAP_PCM) { in podhd_init()
410 if (pod->line6.properties->capabilities & LINE6_CAP_HWMON_CTL) { in podhd_init()
419 if (!(pod->line6.properties->capabilities & LINE6_CAP_CONTROL_INFO)) { in podhd_init()
452 .capabilities = LINE6_CAP_PCM
463 .capabilities = LINE6_CAP_PCM
474 .capabilities = LINE6_CAP_PCM | LINE6_CAP_CONTROL
486 .capabilities = LINE6_CAP_CONTROL | LINE6_CAP_CONTROL_INFO
[all …]
/Linux-v5.15/arch/ia64/kernel/
Derr_inject.c4 * 2.) Query error injection capabilities.
53 static u64 capabilities[NR_CPUS]; variable
103 &capabilities[cpu], in show()
110 &capabilities[cpu], in show()
120 printk(KERN_DEBUG "capabilities=%llx,\n", capabilities[cpu]); in show()
198 show(capabilities)
207 define_one_ro(capabilities);
/Linux-v5.15/arch/arm64/include/asm/
Dcpufeature.h106 * CPU capabilities:
113 * detect the capabilities correctly on the system and take appropriate
116 * This comment tries to explain how we treat the capabilities.
158 * CPUs are treated "late CPUs" for capabilities determined by the boot
161 * At the moment there are two passes of finalising the capabilities.
162 * a) Boot CPU scope capabilities - Finalised by primary boot CPU via
169 * capabilities finalised already. This happens via :
173 * As explained in (2) above, capabilities could be finalised at
175 * against the capabilities that have been finalised by the time it
224 * typical for capabilities that represent enhanced functionality.
[all …]
/Linux-v5.15/mm/
Dnommu.c753 unsigned long capabilities, rlen; in validate_mmap_request() local
786 capabilities = file->f_op->mmap_capabilities(file); in validate_mmap_request()
788 /* no explicit capabilities set, so assume some in validate_mmap_request()
793 capabilities = NOMMU_MAP_COPY; in validate_mmap_request()
797 capabilities = in validate_mmap_request()
808 /* eliminate any capabilities that we can't support on this in validate_mmap_request()
811 capabilities &= ~NOMMU_MAP_DIRECT; in validate_mmap_request()
813 capabilities &= ~NOMMU_MAP_COPY; in validate_mmap_request()
829 if (!(capabilities & NOMMU_MAP_DIRECT)) in validate_mmap_request()
833 capabilities &= ~NOMMU_MAP_COPY; in validate_mmap_request()
[all …]
/Linux-v5.15/drivers/bcma/
Ddriver_chipcommon.c30 if (cc->capabilities & BCMA_CC_CAP_PMU) in bcma_chipco_get_alp_clock()
41 if (cc->capabilities & BCMA_CC_CAP_PMU) { in bcma_core_cc_has_pmu_watchdog()
99 if (cc->capabilities & BCMA_CC_CAP_PMU) { in bcma_chipco_watchdog_ticks_per_ms()
146 switch (cc->capabilities & BCMA_CC_CAP_FLASHT) { in bcma_core_chipcommon_flash_detect()
162 if (cc->capabilities & BCMA_CC_CAP_NFLASH) { in bcma_core_chipcommon_flash_detect()
180 cc->capabilities = bcma_cc_read32(cc, BCMA_CC_CAP); in bcma_core_chipcommon_early_init()
184 if (cc->capabilities & BCMA_CC_CAP_PMU) in bcma_core_chipcommon_early_init()
215 if (cc->capabilities & BCMA_CC_CAP_PMU) in bcma_core_chipcommon_init()
217 if (cc->capabilities & BCMA_CC_CAP_PCTL) in bcma_core_chipcommon_init()
412 cc->nr_serial_ports = (cc->capabilities & BCMA_CC_CAP_NRUART); in bcma_chipco_serial_init()
/Linux-v5.15/Documentation/ia64/
Derr_inject.rst12 and query error injection capabilities. The driver code is in
15 (sysfs interface) to inject errors or query error injection capabilities.
17 The tool can be used to test Intel IPF machine MC handling capabilities.
497 int rd_capabilities(char *path, u64 *capabilities)
500 sprintf(fn, "%s/capabilities", path);
501 if (rd(fn, capabilities)<0) {
502 perror("capabilities reading error.\n");
513 unsigned long capabilities, resources;
544 sprintf(fn, "%s/capabilities", path);
545 if (rd(fn,&capabilities)<0) {
[all …]

12345678910>>...81