Searched refs:IDs (Results 1 – 25 of 175) sorted by relevance
1234567
| /Linux-v4.19/Documentation/driver-api/usb/ |
| D | bulk-streams.rst | 38 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-v4.19/Documentation/devicetree/bindings/clock/ |
| D | mvebu-core-clock.txt | 7 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:
|
| D | mvebu-gated-clock.txt | 10 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:
|
| D | ti,sci-clk.txt | 17 exposed by the PM firmware. The list of valid values for the device IDs
18 and clocks IDs for 66AK2G SoC are documented at
|
| D | armada3700-periph-clock.txt | 12 The following is a list of provided IDs for Armada 370 North bridge clocks:
33 The following is a list of provided IDs for Armada 370 South bridge clocks:
|
| D | imx6sl-clock.txt | 10 for the full list of i.MX6 SoloLite clock IDs.
|
| D | efm32-clock.txt | 11 IDs.
|
| D | clps711x-clock.txt | 11 for the full list of CLPS711X clock IDs.
|
| D | imx7d-clock.txt | 13 for the full list of i.MX7 Dual clock IDs.
|
| D | imx6sx-clock.txt | 13 for the full list of i.MX6 SoloX clock IDs.
|
| /Linux-v4.19/Documentation/core-api/ |
| D | idr.rst | 12 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 :c:func:`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-v4.19/Documentation/devicetree/bindings/iommu/ |
| D | arm,smmu.txt | 47 the set of matched IDs does not result in conflicts.
65 when matching stream IDs (e.g. this may be programmed
69 configurations given globally unique input IDs). This
79 and their corresponding Stream IDs. Each device node
100 /* device with two stream IDs, 0 and 7 */
113 /* device with stream IDs 0 and 7 */
119 /* device with stream IDs 1, 17, 33 and 49 */
|
| /Linux-v4.19/Documentation/devicetree/bindings/arm/ |
| D | psci.txt | 28 For these cases function IDs must be provided.
31 Function IDs are not required and should be ignored by
93 A DTB may provide IDs for use by kernels without PSCI 0.2 support,
95 These IDs will be ignored by kernels with PSCI 0.2 support, which will
96 use the standard PSCI 0.2 IDs exclusively.
|
| /Linux-v4.19/Documentation/media/uapi/v4l/ |
| D | control.rst | 18 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
301 End of the predefined control IDs (currently
497 order to resolve this drivers use unique IDs and the
498 ``V4L2_CID_PRIVATE_BASE`` IDs are mapped to those unique IDs by the
499 kernel. Consider these ``V4L2_CID_PRIVATE_BASE`` IDs as aliases to
500 the real IDs.
502 Many applications today still use the ``V4L2_CID_PRIVATE_BASE`` IDs
[all …]
|
| /Linux-v4.19/Documentation/namespaces/ |
| D | compatibility-list.txt | 18 1. Both the IPC and the PID namespaces provide IDs to address
28 2. Intentionally, two equal user IDs in different user namespaces
|
| /Linux-v4.19/Documentation/acpi/ |
| D | enumeration.txt | 37 for the device and add supported ACPI IDs. If this same IP-block is used on
46 /* ACPI IDs here */
164 The SPI device drivers only need to add ACPI IDs in a similar way than with
224 The slaves behind I2C bus controller only need to add the ACPI IDs like
381 list the IDs of devices the given one is compatible with, but those IDs must
401 be used to find a driver for the device along with the device IDs listed by _CID
404 Analogously, if PRP0001 is present in the list of device IDs returned by _CID,
407 case their relative priority with respect to the other device IDs listed by
409 Specifically, the device IDs returned by _HID and preceding PRP0001 in the _CID
|
| /Linux-v4.19/Documentation/devicetree/bindings/mfd/ |
| D | mc13xxx.txt | 28 MC13783 LED IDs:
42 MC13892 LED IDs:
50 MC34708 LED IDs:
|
| /Linux-v4.19/Documentation/media/v4l-drivers/ |
| D | au0828-cardlist.rst | 13 - USB IDs
|
| D | saa7164-cardlist.rst | 13 - PCI IDs
|
| /Linux-v4.19/arch/powerpc/include/asm/ |
| D | hydra.h | 32 u_int IDs; member
|
| /Linux-v4.19/Documentation/driver-model/ |
| D | binding.txt | 27 ID of the device must match one of the device IDs that the driver
28 supports. The format and semantics for comparing IDs is bus-specific.
31 a device against the IDs of a driver. The bus returns 1 if a match was
|
| /Linux-v4.19/Documentation/devicetree/bindings/display/exynos/ |
| D | exynos_hdmi.txt | 22 - clocks: list of clock IDs from SoC clock driver.
33 - clock-names: aliases as per driver requirements for above clock IDs:
|
| /Linux-v4.19/Documentation/ |
| D | pnp.txt | 26 - 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-v4.19/Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-bindings.txt | 39 those names to the integer IDs.
43 IDs that must be provided, or whether to define the set of state names that
83 /* For the same device if using state IDs */
227 how pin IDs and pin multiplexing configuration are defined and assembled
315 - pins takes a list of pin names or IDs as a required argument. The specific
319 - pinmux takes a list of pin IDs and mux settings as required argument. The
321 - How pin IDs and mux settings are defined and assembled together in a single
|
| /Linux-v4.19/Documentation/media/uapi/mediactl/ |
| D | media-ioc-enum-entities.rst | 47 Entity IDs can be non-contiguous. Applications must *not* try to
69 do not hardcode entity IDs in an application.
|
1234567
