| /OK3568_Linux_fs/external/xserver/dbe/ |
| H A D | dbe.c | 245 pDbeWindowPriv->IDs = pDbeWindowPriv->initIDs; in ProcDbeAllocateBackBufferName()
249 pDbeWindowPriv->IDs[0] = stuff->buffer; in ProcDbeAllocateBackBufferName()
253 pDbeWindowPriv->IDs[i] = DBE_FREE_ID_ELEMENT; in ProcDbeAllocateBackBufferName()
269 if (pDbeWindowPriv->IDs[i] == DBE_FREE_ID_ELEMENT) { in ProcDbeAllocateBackBufferName()
286 pIDs = pDbeWindowPriv->IDs; in ProcDbeAllocateBackBufferName()
290 pDbeWindowPriv->IDs = in ProcDbeAllocateBackBufferName()
294 if (!pDbeWindowPriv->IDs) { in ProcDbeAllocateBackBufferName()
297 memset(&pDbeWindowPriv->IDs[pDbeWindowPriv->nBufferIDs], 0, in ProcDbeAllocateBackBufferName()
306 memcpy(pDbeWindowPriv->IDs, pDbeWindowPriv->initIDs, in ProcDbeAllocateBackBufferName()
322 pDbeWindowPriv->IDs[add_index] = stuff->buffer; in ProcDbeAllocateBackBufferName()
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/usb/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/Documentation/core-api/ |
| H A 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 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.
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/clock/ |
| H A 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:
|
| H A 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:
|
| H A 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
|
| H A 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:
|
| H A D | brcm,iproc-clocks.txt | 98 These clock IDs are defined in:
162 Northstar Plus. These clock IDs are defined in:
193 These clock IDs are defined in:
254 These clock IDs are defined in:
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-graphics/wayland/wayland/ |
| H A D | CVE-2021-3782.patch | 6 Since server IDs are basically indistinguishable from really big client
7 IDs at many points in the source, it's theoretically possible to overflow
8 a map and either overflow server IDs into the client ID space, or grow
9 client IDs into the server ID space. This would currently take a massive
16 IDs. It will still take an improbable amount of RAM to hit this, and a
|
| /OK3568_Linux_fs/kernel/Documentation/userspace-api/media/v4l/ |
| H A 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 …]
|
| H A D | pixfmt-compressed.rst | 70 :ref:`associated Codec Control IDs <v4l2-mpeg-h264>`. Exactly
119 See the :ref:`associated Codec Control IDs <v4l2-mpeg-mpeg2>`.
160 See the :ref:`associated Codec Control IDs <v4l2-mpeg-vp8>`.
203 See the :ref:`associated Codec Control IDs <v4l2-mpeg-hevc>`.
225 See the :ref:`associated Codec Control IDs <v4l2-mpeg-fwht>`.
|
| /OK3568_Linux_fs/u-boot/doc/device-tree-bindings/clock/ |
| H A D | nvidia,tegra20-car.txt | 18 registers. These IDs often match those in the CAR's RST_DEVICES registers,
20 this case, those clocks are assigned IDs above 95 in order to highlight
21 this issue. Implementations that interpret these clock IDs as bit values
25 The balance of the clocks controlled by the CAR are assigned IDs of 96 and
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/media/ |
| H A D | dvb-usb-dibusb-mb-cardlist.rst | 14 - USB IDs
21 * - Artec T1 USB1.1 TVBOX with AN2235 (faulty USB IDs)
|
| H A D | dvb-usb-au6610-cardlist.rst | 14 - USB IDs
|
| H A D | dvb-usb-anysee-cardlist.rst | 14 - USB IDs
|
| H A D | dvb-usb-digitv-cardlist.rst | 14 - USB IDs
|
| H A D | dvb-usb-zd1301-cardlist.rst | 14 - USB IDs
|
| H A D | dvb-usb-opera1-cardlist.rst | 14 - USB IDs
|
| /OK3568_Linux_fs/kernel/Documentation/firmware-guide/acpi/ |
| H A D | enumeration.rst | 42 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
392 list the IDs of devices the given one is compatible with, but those IDs must
412 be used to find a driver for the device along with the device IDs listed by _CID
415 Analogously, if PRP0001 is present in the list of device IDs returned by _CID,
418 case their relative priority with respect to the other device IDs listed by
420 Specifically, the device IDs returned by _HID and preceding PRP0001 in the _CID
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/namespaces/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/mfd/ |
| H A D | mc13xxx.txt | 28 MC13783 LED IDs:
42 MC13892 LED IDs:
50 MC34708 LED IDs:
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/driver-model/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/ |
| H A 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
225 Supported PnP card IDs can optionally be defined.
|
| /OK3568_Linux_fs/kernel/Documentation/userspace-api/media/mediactl/ |
| H A D | media-ioc-g-topology.rst | 135 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.
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/display/exynos/ |
| H A 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:
|