Searched full:capabilities (Results 1 – 25 of 287) sorted by relevance
12345678910>>...12
| /Documentation/userspace-api/media/ |
| D | videodev2.h.rst.exceptions | 152 replace define V4L2_CAP_VIDEO_CAPTURE device-capabilities
153 replace define V4L2_CAP_VIDEO_CAPTURE_MPLANE device-capabilities
154 replace define V4L2_CAP_VIDEO_OUTPUT device-capabilities
155 replace define V4L2_CAP_VIDEO_OUTPUT_MPLANE device-capabilities
156 replace define V4L2_CAP_VIDEO_M2M device-capabilities
157 replace define V4L2_CAP_VIDEO_M2M_MPLANE device-capabilities
158 replace define V4L2_CAP_VIDEO_OVERLAY device-capabilities
159 replace define V4L2_CAP_VBI_CAPTURE device-capabilities
160 replace define V4L2_CAP_VBI_OUTPUT device-capabilities
161 replace define V4L2_CAP_SLICED_VBI_CAPTURE device-capabilities
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-querycap.rst | 13 VIDIOC_QUERYCAP - Query device capabilities
36 information about driver and hardware capabilities. The ioctl takes a
105 - ``capabilities``
106 - Available capabilities of the physical device as a whole, see
107 :ref:`device-capabilities`. The same physical device can export
109 /dev/radioZ). The ``capabilities`` field should contain a union of
110 all capabilities available around the several V4L2 devices
111 exported to userspace. For all those devices the ``capabilities``
112 field returns the same set of capabilities. This allows
118 - 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 | vidioc-reqbufs.rst | 95 - ``capabilities``
97 capabilities. In that case all you know is that the driver is
100 capabilities.
102 If you want to query the capabilities with a minimum of side-effects,
114 .. _v4l2-buf-capabilities:
125 .. flat-table:: V4L2 Buffer Capabilities Flags
|
| 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-subdev-g-fmt.rst | 52 capabilities and configures the device. Upon return the struct
56 Applications can query the device capabilities by setting the ``which``
80 doesn't match the device capabilities. They must instead modify the
121 - Try formats, used for querying device capabilities.
|
| D | vidioc-enuminput.rst | 95 - ``capabilities``
96 - This field provides capabilities for the input. See
97 :ref:`input-capabilities` for flags.
199 .. _input-capabilities:
201 .. flat-table:: Input capabilities
|
| D | dev-radio.rst | 17 Querying Capabilities
22 ``capabilities`` field of struct
|
| D | dv-timings.rst | 36 Applications can make use of the :ref:`input-capabilities` and
37 :ref:`output-capabilities` flags to determine whether the digital
|
| /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/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
|
| /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.
111 device capabilities in term of speed, maximum read/write
119 device capabilities in term of exposed features. See the I3C
136 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/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>>...12