| /linux/tools/testing/selftests/kvm/x86/ |
| H A D | vmx_pmu_caps_test.c | 34 u64 capabilities; member
89 vcpu_set_msr(vcpu, MSR_IA32_PERF_CAPABILITIES, host_cap.capabilities); in KVM_ONE_VCPU_TEST()
91 vcpu_args_set(vcpu, 1, host_cap.capabilities); in KVM_ONE_VCPU_TEST()
105 host_cap.capabilities); in KVM_ONE_VCPU_TEST()
107 vcpu_set_msr(vcpu, MSR_IA32_PERF_CAPABILITIES, host_cap.capabilities); in KVM_ONE_VCPU_TEST()
114 host_cap.capabilities ^ BIT_ULL(i)); in KVM_ONE_VCPU_TEST()
116 host_cap.capabilities ^ BIT_ULL(i)); in KVM_ONE_VCPU_TEST()
127 vcpu_set_msr(vcpu, MSR_IA32_PERF_CAPABILITIES, host_cap.capabilities); in KVM_ONE_VCPU_TEST()
132 const uint64_t fungible_caps = host_cap.capabilities & ~immutable_caps.capabilities; in KVM_ONE_VCPU_TEST()
138 host_cap.capabilities & ~BIT_ULL(bit)); in KVM_ONE_VCPU_TEST()
[all …]
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | vidioc-subdev-g-client-cap.rst | 14 capabilities.
40 subdevice ioctls) capabilities. The client capabilities are stored in the file
42 capabilities for each opened subdev separately.
44 By default no client capabilities are set when a subdev device node is opened.
46 The purpose of the client capabilities are to inform the kernel of the behavior
50 The ``VIDIOC_SUBDEV_G_CLIENT_CAP`` ioctl returns the current client capabilities
53 The ``VIDIOC_SUBDEV_S_CLIENT_CAP`` ioctl sets client capabilities for the file
54 handle ``fd``. The new capabilities fully replace the current capabilities, the
55 ioctl can therefore also be used to remove capabilities that have previously
59 :c:type:`v4l2_subdev_client_capability` to reflect the capabilities that have
[all …]
|
| H A D | vidioc-querycap.rst | 13 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 …]
|
| H A D | vidioc-dv-timings-cap.rst | 13 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 …]
|
| H A D | vidioc-subdev-querycap.rst | 13 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
|
| H A D | vidioc-create-bufs.rst | 103 - ``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
|
| H A D | vidioc-enumoutput.rst | 90 - ``capabilities``
91 - This field provides capabilities for the output. See
92 :ref:`output-capabilities` for flags.
123 .. _output-capabilities:
125 .. flat-table:: Output capabilities
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-usb_power_delivery | 23 What: /sys/class/usb_power_delivery/.../source-capabilities
27 The source capabilities message "Source_Capabilities" contains a
37 What: /sys/class/usb_power_delivery/.../sink-capabilities
42 of Power Data Objects (PDO) just like with source capabilities,
43 but instead of describing the power capabilities, these objects
47 same as with the source capabilities message.
63 related to the USB capabilities rather than power capabilities.
72 What: /sys/class/usb_power_delivery/.../source-capabilities/1:fixed_supply/usb_suspend_supported
81 What: /sys/class/usb_power_delivery/.../sink-capabilities/1:fixed_supply/higher_capability
127 What: /sys/class/usb_power_delivery/.../source-capabilities/<position>:fixed_supply/peak_current
[all …]
|
| /linux/fs/smb/server/ |
| H A D | smb2ops.c | 18 .capabilities = SMB2_GLOBAL_CAP_LARGE_MTU,
44 .capabilities = SMB2_GLOBAL_CAP_LARGE_MTU,
71 .capabilities = SMB2_GLOBAL_CAP_LARGE_MTU,
98 .capabilities = SMB2_GLOBAL_CAP_LARGE_MTU,
207 conn->vals->capabilities |= SMB2_GLOBAL_CAP_LEASING; in init_smb2_1_server()
224 conn->vals->capabilities |= SMB2_GLOBAL_CAP_LEASING | in init_smb3_0_server()
229 conn->vals->capabilities |= SMB2_GLOBAL_CAP_ENCRYPTION; in init_smb3_0_server()
234 conn->vals->capabilities |= SMB2_GLOBAL_CAP_ENCRYPTION; in init_smb3_0_server()
237 conn->vals->capabilities |= SMB2_GLOBAL_CAP_MULTI_CHANNEL; in init_smb3_0_server()
254 conn->vals->capabilities |= SMB2_GLOBAL_CAP_LEASING | in init_smb3_02_server()
[all …]
|
| /linux/Documentation/arch/x86/ |
| H A D | intel-hfi.rst | 25 separate capabilities. Even though on some systems these two metrics may be
26 related, they are specified as independent capabilities in the Intel SDM.
28 These capabilities may change at runtime as a result of changes in the
30 at which these capabilities are updated is specific to each processor model. On
31 some models, capabilities are set at boot time and never change. On others,
32 capabilities may change every tens of milliseconds. For instance, a remote
37 The kernel or a userspace policy daemon can use these capabilities to modify
39 capabilities of a given logical processor becomes zero, it is an indication that
|
| /linux/Documentation/userspace-api/media/dvb/ |
| H A D | fe-get-info.rst | 13 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/Documentation/security/ |
| H A D | lsm.rst | 35 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/drivers/net/ethernet/mellanox/mlx5/core/lib/ |
| H A D | hv_vhca.c | 133 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/security/ |
| H A D | commoncap.c | 2 /* Common capabilities, needed by capability.o.
35 * !secure(SECURE_NOROOT) mode, then we raise capabilities.
37 * the file capabilities to be applied, and the setuid-root
39 * to get full privilege on a kernel without file capabilities
40 * support. So in that case we do not raise capabilities.
49 " effective capabilities. Therefore not raising all" in warn_setuid_and_fcaps_mixed()
50 " capabilities.\n", fname); in warn_setuid_and_fcaps_mixed()
80 /* Do we have the necessary capabilities? */ in cap_capable_helper()
156 * task's capabilities, then ptrace access is allowed.
193 * capabilities, the
[all...] |
| /linux/drivers/platform/x86/ |
| H A D | dasharo-acpi.c | 70 struct dasharo_capability capabilities[DASHARO_FEATURE_MAX][MAX_CAPS_PER_FEAT]; member
104 if (feat >= ARRAY_SIZE(data->capabilities)) in dasharo_read_channel()
111 obj[0].integer.value = data->capabilities[feat][channel].group; in dasharo_read_channel()
113 obj[1].integer.value = data->capabilities[feat][channel].index; in dasharo_read_channel()
167 *str = data->capabilities[DASHARO_FEATURE_TEMPERATURE][channel].name; in dasharo_hwmon_read_string()
173 *str = data->capabilities[DASHARO_FEATURE_FAN_TACH][channel].name; in dasharo_hwmon_read_string()
213 // Max 24 capabilities per feature
310 if (cap_count >= ARRAY_SIZE(data->capabilities[feat])) in dasharo_fill_feature_caps()
313 cap = &data->capabilities[feat][cap_count]; in dasharo_fill_feature_caps()
|
| /linux/mm/ |
| H A D | nommu.c | 698 unsigned long capabilities, rlen; in validate_mmap_request() local
731 capabilities = file->f_op->mmap_capabilities(file); in validate_mmap_request()
733 /* no explicit capabilities set, so assume some in validate_mmap_request()
738 capabilities = NOMMU_MAP_COPY; in validate_mmap_request()
742 capabilities = in validate_mmap_request()
753 /* eliminate any capabilities that we can't support on this in validate_mmap_request()
756 capabilities &= ~NOMMU_MAP_DIRECT; in validate_mmap_request()
758 capabilities &= ~NOMMU_MAP_COPY; in validate_mmap_request()
774 if (!(capabilities & NOMMU_MAP_DIRECT)) in validate_mmap_request()
778 capabilities &= ~NOMMU_MAP_COPY; in validate_mmap_request()
[all …]
|
| /linux/Documentation/userspace-api/media/cec/ |
| H A D | cec-ioc-adap-g-caps.rst | 13 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/drivers/staging/greybus/ |
| H A D | gb-camera.h | 52 * @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/drivers/bcma/ |
| H A D | driver_chipcommon.c | 30 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/drivers/usb/typec/ |
| H A D | pd.c | 454 [TYPEC_SINK] = "sink-capabilities",
455 [TYPEC_SOURCE] = "source-capabilities",
464 .name = "capabilities",
469 * usb_power_delivery_register_capabilities - Register a set of capabilities.
470 * @pd: The USB PD instance that the capabilities belong to.
471 * @desc: Description of the Capabilities Message.
473 * This function registers a Capabilities Message described in @desc. The
474 * capabilities will have their own sub-directory under @pd in sysfs.
517 * usb_power_delivery_unregister_capabilities - Unregister a set of capabilities
518 * @cap: The capabilities
[all …]
|
| /linux/Documentation/admin-guide/ |
| H A D | perf-security.rst | 65 into distinct units, known as capabilities [6]_ , which can be
83 capabilities then providing the process with CAP_PERFMON capability singly
96 Other capabilities being granted to unprivileged processes can
105 Mechanisms of capabilities, privileged capability-dumb files [6]_,
127 2. Assign the required capabilities to the Perf tool executable file and
165 In case Perf tool executable can't be assigned required capabilities (e.g.
167 not supported by the file system) then creation of the capabilities
169 inherent processes with CAP_PERFMON and other required capabilities so that
176 and other required capabilities into ambient capability set of the shell
197 shell and have CAP_PERFMON and other required capabilities enabled
[all …]
|
| /linux/drivers/ssb/ |
| H A D | driver_chipcommon.c | 57 if (cc->capabilities & SSB_CHIPCO_CAP_PMU) in ssb_chipco_set_clockmode()
69 if (!(cc->capabilities & SSB_CHIPCO_CAP_PCTL)) in ssb_chipco_set_clockmode()
222 if (!(cc->capabilities & SSB_CHIPCO_CAP_PCTL)) in chipco_powercontrol_init()
269 if (cc->capabilities & SSB_CHIPCO_CAP_PMU) { in calc_fast_powerup_delay()
274 if (!(cc->capabilities & SSB_CHIPCO_CAP_PCTL)) in calc_fast_powerup_delay()
287 if (cc->capabilities & SSB_CHIPCO_CAP_PMU) in ssb_chipco_alp_clock()
297 if (cc->capabilities & SSB_CHIPCO_CAP_PMU) { in ssb_chipco_watchdog_get_max_timer()
337 if (cc->capabilities & SSB_CHIPCO_CAP_PMU) { in ssb_chipco_watchdog_ticks_per_ms()
395 *plltype = (cc->capabilities & SSB_CHIPCO_CAP_PLLT); in ssb_chipco_get_clockcpu()
418 *plltype = (cc->capabilities & SSB_CHIPCO_CAP_PLLT); in ssb_chipco_get_clockcontrol()
[all …]
|
| /linux/block/ |
| H A D | blk-crypto-profile.c | 12 * capabilities and certain functions (e.g., functions to program and evict
565 * blk_crypto_intersect_capabilities() - restrict supported crypto capabilities
570 * This clears all crypto capabilities in @parent that aren't set in @child. If
571 * @child is NULL, then this clears all parent capabilities.
599 * the crypto capabilities that @reference does.
603 * Return: %true if @target supports all the crypto capabilities of @reference.
633 * blk_crypto_update_capabilities() - Update the capabilities of a crypto
636 * @dst: The crypto profile whose capabilities to update.
637 * @src: The crypto profile whose capabilities this function will update @dst's
638 * capabilities to.
[all …]
|
| /linux/drivers/net/ethernet/chelsio/cxgb4vf/ |
| H A D | t4vf_common.h | 107 typedef u16 fw_port_cap16_t; /* 16-bit Port Capabilities integral value */
108 typedef u32 fw_port_cap32_t; /* 32-bit Port Capabilities integral value */
112 FW_CAPS16 = 1, /* old Firmware: 16-bit Port Capabilities */
113 FW_CAPS32 = 2, /* new Firmware: 32-bit Port Capabilities */
129 fw_port_cap32_t pcaps; /* link capabilities */
130 fw_port_cap32_t acaps; /* advertised capabilities */
131 fw_port_cap32_t lpacaps; /* peer advertised capabilities */
253 unsigned int r_caps; /* read capabilities */
254 unsigned int wx_caps; /* write/execute capabilities */
269 u8 fw_caps_support; /* 32-bit Port Capabilities */
|
| /linux/drivers/net/wireless/ath/ath5k/ |
| H A D | caps.c | 21 * Capabilities *
30 * Fill the capabilities struct
38 /* Capabilities stored in the EEPROM */ in ath5k_hw_set_capabilities()
43 * Set radio capabilities in ath5k_hw_set_capabilities()
65 * Set radio capabilities in ath5k_hw_set_capabilities()
|