| /openbmc/phosphor-logging/test/openpower-pels/ |
| H A D | repository_test.cpp | 667 auto IDs = repo.prune(id); in TEST_F() local
685 EXPECT_TRUE(std::find(IDs.begin(), IDs.end(), 500 + i) != IDs.end()); in TEST_F()
717 auto IDs = repo.prune(id); in TEST_F() local
726 EXPECT_EQ(IDs.size(), 20); in TEST_F()
733 EXPECT_TRUE(std::find(IDs.begin(), IDs.end(), 500 + i) != IDs.end()); in TEST_F()
802 EXPECT_TRUE(IDs.empty()); in TEST_F()
813 IDs = repo.prune(id); in TEST_F()
815 ASSERT_EQ(IDs.size(), 3); in TEST_F()
1036 EXPECT_TRUE(IDs.empty()); in TEST_F()
1047 IDs = repo.prune(id); in TEST_F()
[all …]
|
| /openbmc/linux/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
|
| /openbmc/linux/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:
|
| /openbmc/linux/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
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.
|
| /openbmc/openbmc-test-automation/lib/ |
| H A D | event_notification_utils.robot | 16 Get Event Subscription IDs
17 [Documentation] Get event subscription IDs.
31 ${subscription_ids}= Get Event Subscription IDs
45 ${subscription_ids}= Get Event Subscription IDs
|
| /openbmc/qemu/docs/specs/ |
| H A D | pci-ids.rst | 2 PCI IDs for QEMU
6 virtual devices. The vendor IDs are 1af4 (formerly Qumranet ID) and 1b36.
15 Note that this allocation is separate from the virtio device IDs, which are
38 0x1040 offset. The virtio IDs are defined in the virtio
40 defines for all virtio IDs (``linux/virtio_ids.h``); QEMU has a
55 All other device IDs are reserved.
|
| /openbmc/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
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | wmi.rst | 11 and/or notification IDs. The modern bus-based interface instead maps each
13 WMI devices sharing GUIDs and/or notification IDs. Drivers can then register
|
| /openbmc/linux/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-opera1-cardlist.rst | 14 - USB IDs
|
| H A D | dvb-usb-zd1301-cardlist.rst | 14 - USB IDs
|
| H A D | dvb-usb-digitv-cardlist.rst | 14 - USB IDs
|
| H A D | dvb-usb-vp702x-cardlist.rst | 14 - USB IDs
|
| H A D | dvb-usb-umt-010-cardlist.rst | 14 - USB IDs
|
| H A D | dvb-usb-dtv5100-cardlist.rst | 14 - USB IDs
|
| H A D | dvb-usb-nova-t-usb2-cardlist.rst | 14 - USB IDs
|
| H A D | dvb-usb-lmedm04-cardlist.rst | 14 - USB IDs
|
| H A D | dvb-usb-technisat-usb2-cardlist.rst | 14 - USB IDs
|
| /openbmc/docs/designs/ |
| H A D | gpio-based-cable-presence.md | 11 most support 255 sensor IDs. On a systems with 25 cables, and 255 sensor IDs,
14 less SDR IDs.
69 On the IPMI sIDe, the presence states will be grouped into fewer SDR IDs in
70 order to save SDR IDs for ipmi. Given the following example,
126 addition, Redfish doesn't have a limit of 256 SDR IDs. Therefore, no need to
133 of 255 IDs. Meanwhile, it doesn't support stacking multiple presence states in
|
| /openbmc/linux/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
313 End of the predefined control IDs (currently
509 order to resolve this drivers use unique IDs and the
510 ``V4L2_CID_PRIVATE_BASE`` IDs are mapped to those unique IDs by the
511 kernel. Consider these ``V4L2_CID_PRIVATE_BASE`` IDs as aliases to
512 the real IDs.
514 Many applications today still use the ``V4L2_CID_PRIVATE_BASE`` IDs
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/display/tegra/ |
| H A 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.
225 description: Specification of stream IDs available for memory context device
226 use. Should be a mapping of IDs 0..n to IOMMU entries corresponding to
227 usable stream IDs.
|
| /openbmc/linux/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
|