Searched full:capabilities (Results 1 – 25 of 265) sorted by relevance
1234567891011
| /Documentation/media/ |
| D | videodev2.h.rst.exceptions | 146 replace define V4L2_CAP_VIDEO_CAPTURE device-capabilities
147 replace define V4L2_CAP_VIDEO_CAPTURE_MPLANE device-capabilities
148 replace define V4L2_CAP_VIDEO_OUTPUT device-capabilities
149 replace define V4L2_CAP_VIDEO_OUTPUT_MPLANE device-capabilities
150 replace define V4L2_CAP_VIDEO_M2M device-capabilities
151 replace define V4L2_CAP_VIDEO_M2M_MPLANE device-capabilities
152 replace define V4L2_CAP_VIDEO_OVERLAY device-capabilities
153 replace define V4L2_CAP_VBI_CAPTURE device-capabilities
154 replace define V4L2_CAP_VBI_OUTPUT device-capabilities
155 replace define V4L2_CAP_SLICED_VBI_CAPTURE device-capabilities
[all …]
|
| /Documentation/media/uapi/v4l/ |
| D | vidioc-querycap.rst | 19 VIDIOC_QUERYCAP - Query device capabilities
44 information about driver and hardware capabilities. The ioctl takes a
114 - ``capabilities``
115 - Available capabilities of the physical device as a whole, see
116 :ref:`device-capabilities`. The same physical device can export
118 /dev/radioZ). The ``capabilities`` field should contain a union of
119 all capabilities available around the several V4L2 devices
120 exported to userspace. For all those devices the ``capabilities``
121 field returns the same set of capabilities. This allows
127 - Device capabilities of the opened device, see
[all …]
|
| D | vidioc-dv-timings-cap.rst | 19 VIDIOC_DV_TIMINGS_CAP - VIDIOC_SUBDEV_DV_TIMINGS_CAP - The capabilities of the Digital Video receiv…
45 To query the capabilities of the DV receiver/transmitter applications
56 When implemented by the driver DV capabilities of subdevices can be
58 on a subdevice node. The capabilities are specific to inputs (for DV
62 zero the ``reserved`` array. Attempts to query capabilities on a pad
98 - ``capabilities``
99 - Several flags giving more information about the capabilities. See
100 :ref:`dv-bt-cap-capabilities` for a description of the flags.
136 - BT.656/1120 timings capabilities of the hardware.
144 .. _dv-bt-cap-capabilities:
[all …]
|
| D | vidioc-create-bufs.rst | 112 - ``capabilities``
114 capabilities. In that case all you know is that the driver is
117 capabilities. See :ref:`here <v4l2-buf-capabilities>` for a list of the
118 capabilities.
120 If you want to just query the capabilities without making any
|
| D | vidioc-reqbufs.rst | 103 - ``capabilities``
105 capabilities. In that case all you know is that the driver is
108 capabilities.
110 If you want to query the capabilities with a minimum of side-effects,
122 .. _v4l2-buf-capabilities:
131 .. flat-table:: V4L2 Buffer Capabilities Flags
|
| D | vidioc-enumoutput.rst | 99 - ``capabilities``
100 - This field provides capabilities for the output. See
101 :ref:`output-capabilities` for flags.
134 .. _output-capabilities:
136 .. flat-table:: Output capabilities
|
| D | vidioc-query-dv-timings.rst | 69 capabilities), then the driver fills in whatever timings it could find
72 found timings with the hardware's capabilities in order to give more
94 capabilities.
|
| D | vidioc-subdev-g-fmt.rst | 59 capabilities and configures the device. Upon return the struct
63 Applications can query the device capabilities by setting the ``which``
82 doesn't match the device capabilities. They must instead modify the
125 - Try formats, used for querying device capabilities.
|
| D | vidioc-enuminput.rst | 104 - ``capabilities``
105 - This field provides capabilities for the input. See
106 :ref:`input-capabilities` for flags.
211 .. _input-capabilities:
213 .. flat-table:: Input capabilities
|
| D | querycap.rst | 13 Querying Capabilities
18 the same type have different capabilities and this specification permits
|
| /Documentation/media/uapi/dvb/ |
| D | fe-get-info.rst | 19 FE_GET_INFO - Query Digital TV frontend capabilities and returns information
46 obtain information about driver and hardware capabilities. The ioctl
52 frontend capabilities
55 Capabilities describe what a frontend can do. Some capabilities are
58 The frontend capabilities are described at :c:type:`fe_caps`.
|
| /Documentation/security/ |
| D | lsm.rst | 35 migrating the Linux capabilities code into such a module.
44 of the framework and the example capabilities security module provided
56 also moves most of the capabilities logic into an optional security
58 This capabilities module is discussed further in
59 `LSM Capabilities Module <#cap>`__.
157 LSM Capabilities Module
160 The LSM kernel patch moves most of the existing POSIX.1e capabilities
163 use capabilities to omit this code entirely from their kernel, instead
166 capabilities logic to maintain and enhance their code more freely,
169 In addition to moving the capabilities logic, the LSM kernel patch could
[all …]
|
| /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/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/media/uapi/cec/ |
| D | cec-ioc-adap-g-caps.rst | 19 CEC_ADAP_G_CAPS - Query device capabilities
61 - ``capabilities``
62 - The capabilities of the CEC adapter, see
63 :ref:`cec-capabilities`.
72 .. _cec-capabilities:
74 .. 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
|
| /Documentation/ABI/testing/ |
| 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.
110 device capabilities in term of speed, maximum read/write
118 device capabilities in term of exposed features. See the I3C
135 Expose the HDR (High Data Rate) capabilities of a device.
|
| /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/ia64/ |
| D | err_inject.rst | 12 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 …]
|
| /Documentation/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/sound/designs/ |
| D | compress-offload.rst | 74 to expose, translate and make use of the capabilities of the audio
110 capabilities. The intent is to make sure all the capabilities
114 the capabilities were exposed with a single descriptor, it may happen
117 it is likely that some implementations make the list of capabilities
146 - Merge of encoder/decoder capabilities
225 stream, or even implement transcoding capabilities. This routing
|
| /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
180 For capabilities, Bus implements API to read standard Slave MIPI properties
182 function that provides capabilities information. Bus needs to know a set of
183 Slave capabilities to program Slave registers and to control the Bus
|
| /Documentation/admin-guide/ |
| D | perf-security.rst | 45 to such monitoring capabilities requires to be ordered and secured
65 into distinct units, known as capabilities [6]_ , which can be
79 Other capabilities being granted to unprivileged processes can
88 Mechanisms of capabilities, privileged capability-dumb files [6]_ and
110 2. Assign the required capabilities to the Perf tool executable file and
129 capabilities.
223 .. [6] `<http://man7.org/linux/man-pages/man7/capabilities.7.html>`_
|
| /Documentation/devicetree/bindings/interconnect/ |
| D | interconnect.txt | 12 nodes, which expose the interconnect related capabilities of the interconnect
13 to consumer drivers. These capabilities can be throughput, latency, priority
|
1234567891011