Searched full:capability (Results 1 – 25 of 300) sorted by relevance
12345678910>>...12
| /Documentation/devicetree/bindings/firmware/ |
| D | gunyah-hypervisor.yaml | 14 Gunyah virtual machines use this information to determine the capability IDs
23 description: Number of cells needed to represent 64-bit capability IDs.
27 description: must be 0, because capability IDs are not memory address
44 - description: Gunyah capability ID of the TX message queue
45 - description: Gunyah capability ID of the RX message queue
79 reg = <0x00000000 0x00000000>, /* TX capability ID */
80 <0x00000000 0x00000001>; /* RX capability ID */
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-usb_power_delivery | 41 The sink capability message "Sink_Capabilities" contains a set
46 The order of the objects in the sink capability message is the
51 What: /sys/class/usb_power_delivery/.../<capability>/<position>:fixed_supply
65 What: /sys/class/usb_power_delivery/.../<capability>/1:fixed_supply/dual_role_power
85 This file shows the value of the Higher capability bit in
90 What: /sys/class/usb_power_delivery/.../<capability>/1:fixed_supply/unconstrained_power
99 What: /sys/class/usb_power_delivery/.../<capability>/1:fixed_supply/usb_communication_capable
106 What: /sys/class/usb_power_delivery/.../<capability>/1:fixed_supply/dual_role_data
114 What: /sys/class/usb_power_delivery/.../<capability>/1:fixed_supply/unchunked_extended_messages_su…
121 What: /sys/class/usb_power_delivery/.../<capability>/<position>:fixed_supply/voltage
[all …]
|
| D | sysfs-bus-pci-drivers-xhci_hcd | 7 Capability (DbC). It can present a debug device which
14 to the Debug Capability. Otherwise, it will be assigned
34 Value can only be changed while debug capability (DbC) is in
47 Value can only be changed while debug capability (DbC) is in
59 Value can only be changed while debug capability (DbC) is in
72 Value can only be changed while debug capability (DbC) is in
|
| D | sysfs-bus-pci-devices-pvpanic | 1 What: /sys/devices/pci0000:00/*/QEMU0001:00/capability for MMIO
2 /sys/bus/pci/drivers/pvpanic-pci/0000:00:0*.0/capability for PCI
22 Notice that this value should be a subset of capability.
|
| D | sysfs-class-iommu-intel-iommu | 15 The cached hardware capability register value
23 The cached hardware extended capability register
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-enum-freq-bands.rst | 40 This ioctl is supported if the ``V4L2_TUNER_CAP_FREQ_BANDS`` capability
72 - ``capability``
73 - :cspan:`2` The tuner/modulator capability flags for this
74 frequency band, see :ref:`tuner-capability`. The
75 ``V4L2_TUNER_CAP_LOW`` or ``V4L2_TUNER_CAP_1HZ`` capability must
77 tuner/modulator. So either all bands have that capability set, or
78 none of them have that capability.
82 if the ``capability`` flag ``V4L2_TUNER_CAP_LOW`` is set, in units
84 ``capability`` flag ``V4L2_TUNER_CAP_1HZ`` is set.
88 or if the ``capability`` flag ``V4L2_TUNER_CAP_LOW`` is set, in
[all …]
|
| D | vidioc-s-hw-freq-seek.rst | 43 :c:type:`v4l2_tuner` ``capability`` field has the
55 This ioctl is supported if the ``V4L2_CAP_HW_FREQ_SEEK`` capability is
88 ``capability`` field will tell you what the hardware supports.
98 :c:type:`v4l2_tuner` ``capability`` field has the
100 struct :c:type:`v4l2_tuner` ``capability`` field has
107 :c:type:`v4l2_tuner` ``capability`` field has the
109 struct :c:type:`v4l2_tuner` ``capability`` field has
|
| D | vidioc-g-tuner.rst | 86 - ``capability``
89 Tuner capability flags, see :ref:`tuner-capability`. Audio flags
97 If multiple frequency bands are supported, then ``capability`` is
98 the union of all ``capability`` fields of each struct
103 if the ``capability`` flag ``V4L2_TUNER_CAP_LOW`` is set, in units
104 of 62.5 Hz, or if the ``capability`` flag ``V4L2_TUNER_CAP_1HZ``
111 or if the ``capability`` flag ``V4L2_TUNER_CAP_LOW`` is set, in
112 units of 62.5 Hz, or if the ``capability`` flag
149 ``_SAP`` flag is cleared in the ``capability`` field, the
210 .. _tuner-capability:
[all …]
|
| D | vidioc-g-audio.rst | 70 - ``capability``
71 - Audio capability flags, see :ref:`audio-capability`.
84 .. _audio-capability:
86 .. flat-table:: Audio Capability Flags
|
| D | vidioc-g-modulator.rst | 81 - ``capability``
82 - Modulator capability flags. No flags are defined for this field,
90 ``capability`` flag ``V4L2_TUNER_CAP_LOW`` is set, in units of
91 62.5 Hz, or if the ``capability`` flag ``V4L2_TUNER_CAP_1HZ`` is
96 ``capability`` flag ``V4L2_TUNER_CAP_LOW`` is set, in units of
97 62.5 Hz, or if the ``capability`` flag ``V4L2_TUNER_CAP_1HZ`` is
|
| /Documentation/networking/device_drivers/ethernet/mellanox/mlx5/ |
| D | switchdev.rst | 175 RoCE capability setup
177 Not all mlx5 PCI devices/SFs require RoCE capability.
179 When RoCE capability is disabled, it saves 1 Mbytes worth of system memory per
183 capability. (refer to Documentation/networking/devlink/devlink-port.rst)
185 migratable capability setup
188 explicitly enable the VF migratable capability.
191 capability. (refer to Documentation/networking/devlink/devlink-port.rst)
193 IPsec crypto capability setup
196 to explicitly enable the VF ipsec_crypto capability. Enabling IPsec capability
198 IPsec capability enabled, any IPsec offloading is blocked on the PF.
[all …]
|
| /Documentation/driver-api/nvdimm/ |
| D | firmware-activate.rst | 18 capability.
47 firmware activation capability is detected.
49 Another property 'ndbusX/firmware/capability' indicates a value of
52 firmware. A capability value of 'quiesce' indicates that firmware does
56 application activity. The 'ndbusX/firmware/capability' property will be
57 elided completely if no firmware activation capability is detected.
|
| /Documentation/networking/devlink/ |
| D | devlink-port.rst | 125 Users may also set the RoCE capability of the function using
131 Users may also set the IPsec crypto capability of the function using
134 Users may also set the IPsec packet capability of the function using
180 RoCE capability setup
182 Not all PCI VFs/SFs require RoCE capability.
184 When RoCE capability is disabled, it saves system memory per PCI VF/SF.
186 When user disables RoCE capability for a VF/SF, user application cannot send or
190 When RoCE capability is disabled in the device using port function attribute,
193 - Get RoCE capability of the VF device::
200 - Set RoCE capability of the VF device::
[all …]
|
| /Documentation/virt/kvm/ |
| D | api.rst | 96 Capability:
102 support this ioctl, there's no capability bit to check its
124 :Capability: basic
141 :Capability: basic
194 is dependent on the CPU capability and the kernel configuration. The limit can
201 Please note that configuring the IPA size does not affect the capability
210 :Capability: basic, KVM_CAP_GET_MSR_FEATURES for KVM_GET_MSR_FEATURE_INDEX_LIST
252 :Capability: basic, KVM_CAP_CHECK_EXTENSION_VM for vm ioctl
271 :Capability: basic
297 :Capability: basic
[all …]
|
| /Documentation/userspace-api/media/ |
| D | videodev2.h.rst.exceptions | 170 # V4L2 capability defines
406 replace define V4L2_TUNER_CAP_LOW tuner-capability
407 replace define V4L2_TUNER_CAP_NORM tuner-capability
408 replace define V4L2_TUNER_CAP_HWSEEK_BOUNDED tuner-capability
409 replace define V4L2_TUNER_CAP_HWSEEK_WRAP tuner-capability
410 replace define V4L2_TUNER_CAP_STEREO tuner-capability
411 replace define V4L2_TUNER_CAP_LANG2 tuner-capability
412 replace define V4L2_TUNER_CAP_SAP tuner-capability
413 replace define V4L2_TUNER_CAP_LANG1 tuner-capability
414 replace define V4L2_TUNER_CAP_RDS tuner-capability
[all …]
|
| /Documentation/PCI/ |
| D | pci-iov-howto.rst | 19 capability which makes one physical device appear as multiple virtual
23 registers encapsulated in the capability. By default, this feature is
34 How can I enable SR-IOV capability
39 enabling and disabling of the capability via API provided by SR-IOV core.
40 If the hardware has SR-IOV capability, loading its PF driver would
66 To enable SR-IOV capability:
79 To disable SR-IOV capability:
|
| D | pcieaer-howto.rst | 30 defines two error reporting paradigms: the baseline capability and
31 the Advanced Error Reporting capability. The baseline capability is
34 capability is implemented with a PCIe Advanced Error Reporting
35 extended capability structure providing more robust error reporting.
38 Error Reporting capability. The PCIe AER driver provides three basic
46 AER capability.
125 Capability structure. Error information being logged includes storing
|
| /Documentation/virt/gunyah/ |
| D | index.rst | 76 virtual machine through capabilities. A capability is an access control
80 is performed using hypercalls taking Capability ID arguments for the required
84 an object to create a new Capability, meaning simpler security analysis.
85 Creation of a new Capability requires the holding of a set of privileged
88 Gunyah itself provides no APIs for Capability ID discovery. Enumeration of
89 Capability IDs is provided by RM as a higher level service to VMs.
127 - Resource (capability) discovery
|
| /Documentation/admin-guide/ |
| D | perf-security.rst | 69 Unprivileged processes with enabled CAP_PERFMON capability are treated
80 use cases is discouraged with respect to the CAP_PERFMON capability.
83 capabilities then providing the process with CAP_PERFMON capability singly
90 So unprivileged processes provided with CAP_SYS_PTRACE capability are
92 CAP_SYS_PTRACE capability is not required and CAP_PERFMON is enough to
99 CAP_SYSLOG capability permits reading kernel space memory addresses from
105 Mechanisms of capabilities, privileged capability-dumb files [6]_,
176 and other required capabilities into ambient capability set of the shell
198 in permitted, effective and ambient capability sets of an inherent process:
217 governed by CAP_PERFMON Linux capability.
[all …]
|
| /Documentation/driver-api/media/drivers/ccs/ |
| D | ccs-regs.asc | 535 # data pedestal capability registers
538 # adc capability registers
561 # video timing set-up capability registers
598 # output clock set-up capability registers
712 # usl capability register
735 # image compression capability registers
739 # test mode capability registers
757 # fifo capability registers
763 # csi-2 capability registers
928 # binning capability registers
[all …]
|
| /Documentation/devicetree/bindings/power/ |
| D | power-controller.txt | 1 * Generic system power control capability
5 components might need to define this capability, which tells the kernel that
|
| /Documentation/devicetree/bindings/mmc/ |
| D | sdhci.txt | 8 property corresponds to the bits in the sdhci capability register. If the bit
12 property corresponds to the bits in the sdhci capability register. If the
|
| /Documentation/userspace-api/media/cec/ |
| D | cec-ioc-adap-g-caps.rst | 81 this capability isn't set, then setting the physical address is
90 this capability isn't set, then the kernel will have configured
100 capability isn't set, then the kernel will handle all CEC
138 - If this capability is set, then :ref:`CEC_ADAP_G_CONNECTOR_INFO` can
144 - If this capability is set, then
|
| D | cec-ioc-dqevent.rst | 70 capability is set and ``have_conn_info`` is zero, then that indicates
159 capability set.
166 capability set.
173 capability set. When open() is called, the HPD pin can be read and
182 capability set. When open() is called, the HPD pin can be read and
191 capability set. When open() is called, the 5V pin can be read and
200 capability set. When open() is called, the 5V pin can be read and
|
| /Documentation/admin-guide/LSM/ |
| D | SafeSetID.rst | 16 user that have been explicitly given the CAP_SETUID runtime capability. It is
26 user, it is an overpowered capability for what is needed in this scenario,
78 capability checks for access to a given network namespace are done by checking
79 whether a task has the given capability in the context of the user namespace
84 retain the CAP_NET_ADMIN capability for the purpose of adjusting network
90 None of the other in-tree LSMs have the capability to gate setid transitions, or
|
12345678910>>...12