Home
last modified time | relevance | path

Searched refs:IDs (Results 1 – 25 of 251) sorted by relevance

1234567891011

/linux/Documentation/driver-api/usb/
A Dbulk-streams.rst38 allocate memory so the driver can use up to num_streams stream IDs. They must
40 IDs. This is to ensure that a UASP driver will be able to use the same stream
46 declares how many stream IDs it can support, and each bulk endpoint on a
47 SuperSpeed device will say how many stream IDs it can handle. Therefore,
48 drivers should be able to deal with being allocated less stream IDs than they
60 Picking new Stream IDs to use
69 driver supports secondary stream IDs.
82 All stream IDs will be deallocated when the driver releases the interface, to
/linux/Documentation/devicetree/bindings/clock/
A Dmvebu-core-clock.txt7 The following is a list of provided IDs and clock names on Armada 370/XP:
14 The following is a list of provided IDs and clock names on Armada 375:
20 The following is a list of provided IDs and clock names on Armada 380/385:
26 The following is a list of provided IDs and clock names on Armada 39x:
34 The following is a list of provided IDs and clock names on 98dx3236:
40 The following is a list of provided IDs and clock names on Kirkwood and Dove:
46 The following is a list of provided IDs and clock names on Orion5x:
A Dmvebu-gated-clock.txt10 The following is a list of provided IDs for Armada 370:
27 The following is a list of provided IDs for Armada 375:
54 The following is a list of provided IDs for Armada 380/385:
81 The following is a list of provided IDs for Armada 39x:
95 The following is a list of provided IDs for Armada XP:
122 The following is a list of provided IDs for 98dx3236:
132 The following is a list of provided IDs for Dove:
155 The following is a list of provided IDs for Kirkwood:
A Darmada3700-periph-clock.txt12 The following is a list of provided IDs for Armada 3700 North bridge clocks:
33 The following is a list of provided IDs for Armada 3700 South bridge clocks:
/linux/Documentation/core-api/
A Didr.rst12 A common problem to solve is allocating identifiers (IDs); generally
14 process IDs, packet identifiers in networking protocols, SCSI tags
37 Some users need to allocate IDs larger than ``INT_MAX``. So far all of
39 idr_alloc_u32(). If you need IDs that will not fit in a u32,
42 If you need to allocate IDs sequentially, you can use
44 with larger IDs, so using this function comes at a slight cost.
58 IDs currently allocated.
/linux/Documentation/userspace-api/media/v4l/
A Dcontrol.rst18 All controls are accessed using an ID value. V4L2 defines several IDs
21 pre-defined control IDs have the prefix ``V4L2_CID_``, and are listed in
29 or a driver specific panel application. Predefined IDs were introduced
59 Control IDs
304 End of the predefined control IDs (currently
500 order to resolve this drivers use unique IDs and the
501 ``V4L2_CID_PRIVATE_BASE`` IDs are mapped to those unique IDs by the
502 kernel. Consider these ``V4L2_CID_PRIVATE_BASE`` IDs as aliases to
503 the real IDs.
505 Many applications today still use the ``V4L2_CID_PRIVATE_BASE`` IDs
[all …]
A Dpixfmt-compressed.rst76 :ref:`associated Codec Control IDs <v4l2-codec-stateless-h264>`.
121 See the :ref:`associated Codec Control IDs <v4l2-codec-stateless-mpeg2>`.
162 See the :ref:`associated Codec Control IDs <v4l2-codec-stateless-vp8>`.
200 See the :ref:`associated Codec Control IDs <v4l2-mpeg-hevc>`.
/linux/Documentation/devicetree/bindings/iommu/
A Darm,smmu.yaml102 set of matched IDs does not result in conflicts.
135 specifies a mask of bits to ignore when matching stream IDs (e.g. this may
139 input IDs). This property is not valid for SMMUs using stream indexing, or
201 /* device with two stream IDs, 0 and 7 */
222 /* device with stream IDs 0 and 7 */
228 /* device with stream IDs 1, 17, 33 and 49 */
/linux/Documentation/admin-guide/media/
A Ddvb-usb-dibusb-mb-cardlist.rst14 - USB IDs
21 * - Artec T1 USB1.1 TVBOX with AN2235 (faulty USB IDs)
A Ddvb-usb-au6610-cardlist.rst14 - USB IDs
A Ddvb-usb-anysee-cardlist.rst14 - USB IDs
A Ddvb-usb-digitv-cardlist.rst14 - USB IDs
A Ddvb-usb-opera1-cardlist.rst14 - USB IDs
A Ddvb-usb-zd1301-cardlist.rst14 - USB IDs
A Ddvb-usb-umt-010-cardlist.rst14 - USB IDs
A Ddvb-usb-vp702x-cardlist.rst14 - USB IDs
A Ddvb-usb-dtv5100-cardlist.rst14 - USB IDs
/linux/Documentation/admin-guide/namespaces/
A Dcompatibility-list.rst23 1. Both the IPC and the PID namespaces provide IDs to address
33 2. Intentionally, two equal user IDs in different user namespaces
/linux/Documentation/devicetree/bindings/arm/
A Dpsci.yaml50 Function IDs are not required and should be ignored by an OS with
176 * A DTB may provide IDs for use by kernels without PSCI 0.2 support,
178 * These IDs will be ignored by kernels with PSCI 0.2 support, which will
179 * use the standard PSCI 0.2 IDs exclusively.
/linux/Documentation/devicetree/bindings/mfd/
A Dmc13xxx.txt28 MC13783 LED IDs:
42 MC13892 LED IDs:
50 MC34708 LED IDs:
/linux/Documentation/firmware-guide/acpi/
A Denumeration.rst42 for the device and add supported ACPI IDs. If this same IP-block is used on
51 /* ACPI IDs here */
171 The SPI device drivers only need to add ACPI IDs in a similar way than with
232 The slaves behind I2C bus controller only need to add the ACPI IDs like
424 list the IDs of devices the given one is compatible with, but those IDs must
444 be used to find a driver for the device along with the device IDs listed by _CID
447 Analogously, if PRP0001 is present in the list of device IDs returned by _CID,
450 case their relative priority with respect to the other device IDs listed by
452 Specifically, the device IDs returned by _HID and preceding PRP0001 in the _CID
/linux/Documentation/driver-api/driver-model/
A Dbinding.rst28 ID of the device must match one of the device IDs that the driver
29 supports. The format and semantics for comparing IDs is bus-specific.
32 a device against the IDs of a driver. The bus returns 1 if a match was
/linux/Documentation/admin-guide/
A Dpnp.rst26 - id - displays a list of support EISA IDs
168 1. the protocol must use EISA IDs
190 adds an EISA ID to the list of supported IDs for the specified device
225 Supported PnP card IDs can optionally be defined.
/linux/Documentation/devicetree/bindings/display/exynos/
A Dexynos_hdmi.txt22 - clocks: list of clock IDs from SoC clock driver.
33 - clock-names: aliases as per driver requirements for above clock IDs:
/linux/Documentation/userspace-api/media/mediactl/
A Dmedia-ioc-g-topology.rst135 do not hardcode entity IDs in an application.
172 do not hardcode interface IDs in an application.
222 do not hardcode pad IDs in an application.
257 do not hardcode link IDs in an application.

Completed in 25 milliseconds

1234567891011