Searched full:capabilities (Results 1 – 25 of 352) sorted by relevance
12345678910>>...15
| /Documentation/userspace-api/media/v4l/ |
| 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 …]
|
| 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 …]
|
| 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 …]
|
| 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
|
| 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
|
| 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
|
| D | querycap.rst | 6 Querying Capabilities
11 the same type have different capabilities and this specification permits
|
| D | vidioc-query-dv-timings.rst | 62 capabilities), then the driver fills in whatever timings it could find
65 found timings with the hardware's capabilities in order to give more
86 capabilities.
|
| D | vidioc-reqbufs.rst | 97 - ``capabilities``
99 capabilities. In that case all you know is that the driver is
102 capabilities.
104 If you want to query the capabilities with a minimum of side-effects,
117 .. _v4l2-buf-capabilities:
128 .. flat-table:: V4L2 Buffer Capabilities Flags
|
| /Documentation/userspace-api/media/ |
| D | videodev2.h.rst.exceptions | 171 replace define V4L2_CAP_VIDEO_CAPTURE device-capabilities
172 replace define V4L2_CAP_VIDEO_CAPTURE_MPLANE device-capabilities
173 replace define V4L2_CAP_VIDEO_OUTPUT device-capabilities
174 replace define V4L2_CAP_VIDEO_OUTPUT_MPLANE device-capabilities
175 replace define V4L2_CAP_VIDEO_M2M device-capabilities
176 replace define V4L2_CAP_VIDEO_M2M_MPLANE device-capabilities
177 replace define V4L2_CAP_VIDEO_OVERLAY device-capabilities
178 replace define V4L2_CAP_VBI_CAPTURE device-capabilities
179 replace define V4L2_CAP_VBI_OUTPUT device-capabilities
180 replace define V4L2_CAP_SLICED_VBI_CAPTURE device-capabilities
[all …]
|
| /Documentation/userspace-api/media/dvb/ |
| 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`.
|
| /Documentation/ABI/testing/ |
| 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 …]
|
| D | sysfs-bus-i3c | 51 device capabilities in term of speed, maximum read/write
61 device capabilities in term of exposed features. See the I3C
82 Expose the HDR (High Data Rate) capabilities of a device.
126 device capabilities in term of speed, maximum read/write
134 device capabilities in term of exposed features. See the I3C
151 Expose the HDR (High Data Rate) capabilities of a device.
|
| /Documentation/arch/x86/ |
| 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
|
| /Documentation/admin-guide/LSM/ |
| D | SafeSetID.rst | 13 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
|
| D | index.rst | 20 The Linux capabilities modules will always be included. This may be
22 For more details on capabilities, see ``capabilities(7)`` in the Linux
|
| /Documentation/security/ |
| 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
|
| /Documentation/ABI/removed/ |
| D | sysfs-bus-nfit | 11 involves determining the ARS capabilities of a given address
12 range. One of the capabilities that is reported is the 'Clear
14 section 9.20.7.4 Function Index 1 - Query ARS Capabilities).
|
| /Documentation/userspace-api/media/cec/ |
| 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
|
| /Documentation/devicetree/bindings/mmc/ |
| D | sdhci.txt | 7 - sdhci-caps-mask: The sdhci capabilities register is incorrect. This 64bit
11 - sdhci-caps: The sdhci capabilities register is incorrect. This 64bit
|
| D | sdhci-common.yaml | 20 Additionally present SDHCI capabilities - values for SDHCI_CAPABILITIES
26 Masked SDHCI capabilities to remove from SDHCI_CAPABILITIES and
|
| /Documentation/ABI/stable/ |
| D | sysfs-driver-usb-usbtmc | 6 These files show the various USB TMC capabilities as described
20 These files show the various USB TMC capabilities as described
|
| /Documentation/admin-guide/ |
| 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 …]
|
| /Documentation/arch/powerpc/ |
| D | elfnote.rst | 6 capabilities and information which can be used by a bootloader or userland.
15 Define the capabilities supported/required by the kernel. This type uses a
|
| /Documentation/driver-api/soundwire/ |
| D | summary.rst | 93 provides capabilities information. DT support is not implemented at this
94 time but should be trivial to add since capabilities are enabled with the
97 The Master interface along with the Master interface capabilities are
181 For capabilities, Bus implements API to read standard Slave MIPI properties
183 function that provides capabilities information. Bus needs to know a set of
184 Slave capabilities to program Slave registers and to control the Bus
|
12345678910>>...15