Searched full:ids (Results 1 – 25 of 345) sorted by relevance
12345678910>>...14
| /Documentation/filesystems/ |
| D | idmappings.rst | 14 An idmapping is essentially a translation of a range of ids into another or the
15 same range of ids. The notational convention for idmappings that is widely used
22 indicates the range of the idmapping, i.e. how many ids are mapped. From now
23 on, we will always prefix ids with ``u`` or ``k`` to make it clear whether
39 the set of all possible ids usable on a given system.
80 third idmapping. The kernel will report unmapped ids as the overflowuid
126 of userspace ids into a range of kernel ids::
136 The kernel is mostly concerned with kernel ids. They are used when performing
145 For the rest of this document we will prefix all userspace ids with ``u`` and
146 all kernel ids with ``k``. Ranges of idmappings will be prefixed with ``r``. So
[all …]
|
| /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
|
| /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
40 Some users need to allocate IDs larger than ``INT_MAX``. So far all of
42 idr_alloc_u32(). If you need IDs that will not fit in a u32,
45 If you need to allocate IDs sequentially, you can use
47 with larger IDs, so using this function comes at a slight cost.
61 IDs currently allocated.
|
| /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 | microchip,mpfs-clkcfg.yaml | 45 PolarFire clock IDs.
56 PolarFire clock IDs.
|
| D | armada3700-periph-clock.txt | 12 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:
|
| /Documentation/devicetree/bindings/hsi/ |
| D | client-devices.txt | 7 - hsi-channel-ids: A list of channel ids
21 hsi-channel-ids property
31 hsi-channel-ids = <0>, <1>, <2>, <3>;
|
| /Documentation/devicetree/bindings/sound/ |
| D | nvidia,tegra30-i2s.yaml | 38 nvidia,ahub-cif-ids:
39 description: list of AHUB CIF IDs
51 - nvidia,ahub-cif-ids
62 nvidia,ahub-cif-ids = <4 4>;
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | riscv,imsics.yaml | 78 riscv,num-ids:
85 riscv,num-guest-ids:
92 riscv,num-ids property.
131 - riscv,num-ids
150 riscv,num-ids = <127>;
168 riscv,num-ids = <127>;
|
| /Documentation/devicetree/bindings/firmware/ |
| D | gunyah-hypervisor.yaml | 14 Gunyah virtual machines use this information to determine the capability IDs
23 description: Number of cells needed to represent 64-bit capability IDs.
27 description: must be 0, because capability IDs are not memory address
|
| /Documentation/driver-api/acpi/ |
| D | scan_handlers.rst | 42 const struct acpi_device_id *ids;
48 where ids is the list of IDs of device nodes the given handler is supposed to
56 to match a scan handler against each of them using the ids arrays of the
|
| /Documentation/userspace-api/media/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
317 End of the predefined control IDs (currently
513 order to resolve this drivers use unique IDs and the
514 ``V4L2_CID_PRIVATE_BASE`` IDs are mapped to those unique IDs by the
515 kernel. Consider these ``V4L2_CID_PRIVATE_BASE`` IDs as aliases to
516 the real IDs.
518 Many applications today still use the ``V4L2_CID_PRIVATE_BASE`` IDs
[all …]
|
| D | pixfmt-compressed.rst | 76 :ref:`associated Codec Control IDs <v4l2-codec-stateless-h264>`.
126 See the :ref:`associated Codec Control IDs <v4l2-codec-stateless-mpeg2>`.
167 See the :ref:`associated Codec Control IDs <v4l2-codec-stateless-vp8>`.
190 See the :ref:`associated Codec Control IDs <v4l2-codec-stateless-vp9>`.
220 See the :ref:`associated Codec Control IDs <v4l2-codec-stateless-hevc>`.
271 See the :ref:`associated Codec Control IDs <v4l2-codec-stateless-av1>`.
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | fsl,mxs-pinctrl.txt | 42 - fsl,pinmux-ids: An integer array. Each integer in the array specify a pin
87 fsl,pinmux-ids = <
106 fsl,pinmux-ids = <MX28_PAD_SSP0_DETECT__SSP0_CARD_DETECT>;
111 fsl,pinmux-ids = <MX28_PAD_SSP0_SCK__SSP0_SCK>;
|
| 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 */
|
| /Documentation/driver-api/driver-model/ |
| D | binding.rst | 28 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
|
| /Documentation/admin-guide/namespaces/ |
| D | compatibility-list.rst | 23 1. Both the IPC and the PID namespaces provide IDs to address
33 2. Intentionally, two equal user IDs in different user namespaces
|
| /Documentation/admin-guide/media/ |
| D | dvb-usb-dibusb-mb-cardlist.rst | 14 - USB IDs
21 * - Artec T1 USB1.1 TVBOX with AN2235 (faulty USB IDs)
|
| D | dvb-usb-au6610-cardlist.rst | 14 - USB IDs
|
| /Documentation/admin-guide/ |
| D | pnp.rst | 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
205 1. first make a list of supported EISA IDS
225 Supported PnP card IDs can optionally be defined.
|
| /Documentation/devicetree/bindings/memory-controllers/ddr/ |
| D | jedec,lpddr-props.yaml | 24 (from MR5) and ZZZZ is the revision ID (from MR6 and MR7). Both IDs are
39 Revision IDs read from Mode Register 6 and 7. One byte per uint32 cell (i.e. <MR6 MR7>).
|
| /Documentation/devicetree/bindings/display/tegra/ |
| D | nvidia,tegra20-host1x.yaml | 174 description: Specification of stream IDs available for memory context device
175 use. Should be a mapping of IDs 0..n to IOMMU entries corresponding to
176 usable stream IDs.
234 description: Specification of stream IDs available for memory context device
235 use. Should be a mapping of IDs 0..n to IOMMU entries corresponding to
236 usable stream IDs.
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | mediatek,gce-props.yaml | 30 GCE has an event table in SRAM, consisting of 1024 event IDs (0~1023).
32 The property mediatek,gce-events is used to obtain the event IDs.
|
| /Documentation/devicetree/bindings/arm/ |
| D | psci.yaml | 46 Function IDs are not required and should be ignored by an OS with
172 * A DTB may provide IDs for use by kernels without PSCI 0.2 support,
174 * These IDs will be ignored by kernels with PSCI 0.2 support, which will
175 * use the standard PSCI 0.2 IDs exclusively.
|
12345678910>>...14