Searched full:capability (Results 1 – 25 of 242) sorted by relevance
12345678910
| /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/block/ |
| D | capability.rst | 2 Generic Block Device Capability
5 This file documents the sysfs file ``block/<disk>/capability``.
7 ``capability`` is a bitfield, printed in hexadecimal, indicating which
|
| /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/ABI/testing/ |
| D | sysfs-bus-umc | 19 The ID of this capability, with 0 being the radio
20 controller capability.
27 The specification version this capability's hardware
|
| 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
|
| D | sysfs-class-iommu-intel-iommu | 15 The cached hardware capability register value
23 The cached hardware extended capability register
|
| D | sysfs-class-mtd | 134 In the case of devices lacking any ECC capability, it is 0.
173 capability. It is ignored on devices lacking ECC capability;
186 devices lacking any ECC capability, it is 0.
197 devices lacking any ECC capability, it is 0.
208 devices lacking any ECC capability, it is 0.
|
| /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
181 is dependent on the CPU capability and the kernel configuration. The limit can
188 Please note that configuring the IPA size does not affect the capability
197 :Capability: basic, KVM_CAP_GET_MSR_FEATURES for KVM_GET_MSR_FEATURE_INDEX_LIST
239 :Capability: basic, KVM_CAP_CHECK_EXTENSION_VM for vm ioctl
258 :Capability: basic
272 :Capability: basic
[all …]
|
| /Documentation/userspace-api/media/ |
| D | videodev2.h.rst.exceptions | 151 # V4L2 capability defines
381 replace define V4L2_TUNER_CAP_LOW tuner-capability
382 replace define V4L2_TUNER_CAP_NORM tuner-capability
383 replace define V4L2_TUNER_CAP_HWSEEK_BOUNDED tuner-capability
384 replace define V4L2_TUNER_CAP_HWSEEK_WRAP tuner-capability
385 replace define V4L2_TUNER_CAP_STEREO tuner-capability
386 replace define V4L2_TUNER_CAP_LANG2 tuner-capability
387 replace define V4L2_TUNER_CAP_SAP tuner-capability
388 replace define V4L2_TUNER_CAP_LANG1 tuner-capability
389 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 PCI Express advanced error reporting
35 extended capability structure providing more robust error reporting.
38 Express Advanced Error Reporting capability. The PCI Express AER
46 capability.
57 has to be compiled. Option CONFIG_PCIEAER supports this capability. It
100 the AER capability structure within its device and to provide callbacks.
126 capability structure. Error information being logged includes storing
138 Configure the AER capability structure
|
| /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/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 processes provided with CAP_SYS_PTRACE capability are effectively
96 CAP_SYSLOG capability permits reading kernel space memory addresses from
102 Mechanisms of capabilities, privileged capability-dumb files [6]_ and
187 [6]_ capability.
195 unprivileged processes with CAP_IPC_LOCK capability.
202 unprivileged processes with CAP_IPC_LOCK capability.
245 for processes with the CAP_IPC_LOCK capability. Thus, perf_events/Perf
[all …]
|
| /Documentation/userspace-api/media/cec/ |
| 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
|
| 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
|
| /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
|
| /Documentation/networking/devlink/ |
| D | devlink-params.rst | 7 ``devlink`` provides capability for a driver to expose device parameters for low
63 - Ignore Alternative Routing-ID Interpretation (ARI) capability. If
64 enabled, the adapter will ignore ARI capability even when the
|
| /Documentation/devicetree/bindings/usb/ |
| D | usb.yaml | 41 default to HW capability.
49 capability.
|
| /Documentation/devicetree/bindings/media/i2c/ |
| D | dongwoon,dw9807-vcm.txt | 3 DW9807 is a 10-bit DAC with current sink capability. It is intended for
|
| D | dongwoon,dw9714.txt | 3 DW9174 is a 10-bit DAC with current sink capability. It is intended
|
12345678910