Home
last modified time | relevance | path

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

12345678

/linux/Documentation/driver-api/usb/
H 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/core-api/
H A Didr.rst12 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.
/linux/Documentation/ABI/testing/
H A Ddebugfs-alienware-wmi24 fan IDs and internal temp IDs.
39 profile IDs.
/linux/Documentation/userspace-api/media/v4l/
H A Dcontrol.rst19 All controls are accessed using an ID value. V4L2 defines several IDs
22 pre-defined control IDs have the prefix ``V4L2_CID_``, and are listed in
30 or a driver specific panel application. Predefined IDs were introduced
60 Control IDs
320 End of the predefined control IDs (currently
516 order to resolve this drivers use unique IDs and the
517 ``V4L2_CID_PRIVATE_BASE`` IDs are mapped to those unique IDs by the
518 kernel. Consider these ``V4L2_CID_PRIVATE_BASE`` IDs as aliases to
519 the real IDs.
521 Many applications today still use the ``V4L2_CID_PRIVATE_BASE`` IDs
[all …]
/linux/Documentation/admin-guide/media/
H A Ddvb-usb-dibusb-mb-cardlist.rst14 - USB IDs
21 * - Artec T1 USB1.1 TVBOX with AN2235 (faulty USB IDs)
H A Ddvb-usb-au6610-cardlist.rst14 - USB IDs
H A Ddvb-usb-anysee-cardlist.rst14 - USB IDs
H A Ddvb-usb-opera1-cardlist.rst14 - USB IDs
H A Ddvb-usb-digitv-cardlist.rst14 - USB IDs
H A Ddvb-usb-zd1301-cardlist.rst14 - USB IDs
H A Ddvb-usb-nova-t-usb2-cardlist.rst14 - USB IDs
H A Ddvb-usb-vp702x-cardlist.rst14 - USB IDs
H A Ddvb-usb-dtv5100-cardlist.rst14 - USB IDs
H A Ddvb-usb-umt-010-cardlist.rst14 - USB IDs
H A Ddvb-usb-lmedm04-cardlist.rst14 - USB IDs
H A Ddvb-usb-cinergyT2-cardlist.rst14 - USB IDs
H A Ddvb-usb-technisat-usb2-cardlist.rst14 - USB IDs
H A Ddvb-usb-a800-cardlist.rst14 - USB IDs
H A Ddvb-usb-ec168-cardlist.rst14 - USB IDs
H A Ddvb-usb-ce6230-cardlist.rst14 - USB IDs
H A Ddvb-usb-az6007-cardlist.rst14 - USB IDs
/linux/Documentation/admin-guide/namespaces/
H 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/driver-api/surface_aggregator/
H A Dssh.rst154 Sequence IDs are not synchronized between the two parties, meaning that they
261 zero. If instance IDs are used, they, in general, start with a value of one,
277 Events are identified by unique and reserved request IDs. These IDs should
280 event handler. Request IDs for events are chosen by the host and directed to
293 and target IDs swapped when compared to the original request (i.e. the request
303 IDs indicating different physical ECs with potentially different feature sets.
310 with up to ``U16_MAX`` pending requests (neglecting request IDs reserved for
/linux/Documentation/devicetree/bindings/pinctrl/
H A Dpinctrl-bindings.txt39 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 */
/linux/Documentation/userspace-api/media/mediactl/
H 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.

12345678