| /openbmc/u-boot/drivers/demo/ |
| H A D | demo-pdata.c | 12 .sides = 4.
16 .sides = 3.
20 .sides = 6.
|
| H A D | demo-uclass.c | 70 pdata->sides = fdtdec_get_int(gd->fdt_blob, dn, "sides", 0); in demo_parse_dt()
72 if (!pdata->sides || !pdata->colour) { in demo_parse_dt()
|
| H A D | demo-simple.c | 20 pdata->sides); in simple_hello()
|
| /openbmc/u-boot/include/ |
| H A D | dm-demo.h | 15 * @sides: Numbers of sides
20 int sides; member
|
| /openbmc/entity-manager/ |
| H A D | OWNERS | 41 - christopher.sides@hpe.com
71 - name: Christopher Sides
72 email: christopher.sides@hpe.com
|
| /openbmc/qemu/docs/devel/migration/ |
| H A D | compatibility.rst | 54 we have the same QEMU version in both sides (qemu-5.2) but we are using
62 both sides are the same QEMU and both sides have exactly the same
167 Here we have the same QEMU in both sides. So it doesn't matter a
220 A device with different features on both sides
223 Let's assume that we are using the same QEMU binary on both sides,
225 different features on both sides of the migration. That can be
233 features of both sides, and that is the way that you should launch
313 binary in both sides of the migration. If we use different QEMU
|
| H A D | postcopy.rst | 207 QEMU instances. On the other hand, when issue happens QEMU on both sides
225 - When both sides of QEMU successfully reconnect using a new or fixed up
234 postcopy migration on both sides and go back to **POSTCOPY_ACTIVE**
256 identical; i.e. RAMBlocks on both sides must use the same page size.
|
| /openbmc/linux/drivers/net/wireless/ath/ |
| H A D | dfs_pattern_detector.h | 24 /* tolerated deviation of radar time stamp in usecs on both sides
68 * @max_pri_tolerance: pulse time stamp tolerance on both sides [us]
|
| /openbmc/u-boot/arch/sandbox/dts/ |
| H A D | sandbox64.dts | 79 sides = <6>;
232 sides = <4>;
251 sides = <3>;
|
| H A D | sandbox.dts | 89 sides = <6>;
267 sides = <4>;
287 sides = <3>;
|
| /openbmc/linux/Documentation/devicetree/bindings/i2c/ |
| H A D | i2c-arb-gpio-challenge.yaml | 41 2. Waits a little bit for the other sides to notice (slew time, say 10
72 The GPIOs that the other sides use to claim the bus. Note that some
|
| /openbmc/u-boot/doc/device-tree-bindings/misc/ |
| H A D | intel,baytrail-fsp.txt | 80 - fsp,dimm-sides
143 fsp,dimm-sides = <DIMM_SIDES_1RANKS>;
|
| /openbmc/qemu/include/qemu/ |
| H A D | sys_membarrier.h | 21 /* Keep it simple, execute a real memory barrier on both sides. */
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/ivytown/ |
| H A D | uncore-cache.json | 201 …, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
210 …, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
219 …, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
228 … 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.; Filt…
237 … 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.; Filt…
246 … 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.; Filt…
255 … 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.; Filt…
264 …, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
273 … 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.; Filt…
282 … 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.; Filt…
[all …]
|
| /openbmc/linux/drivers/usb/host/ |
| H A D | sl811.h | 28 /* TRANSFER REGISTERS: host and peripheral sides are similar
105 * that's 240 bytes, which we'll split evenly between A and B sides.
|
| /openbmc/linux/include/linux/ |
| H A D | rbtree_latch.h | 12 * lookups; but has the constraint (inherent to the seqlock) that read sides
13 * cannot nest in write sides.
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/snowridgex/ |
| H A D | uncore-interconnect.json | 1531 …, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
1540 …, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
1549 …, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
1558 …, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
1567 …, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
1576 …, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
1585 …, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
1594 …, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
1603 …, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
1612 …, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
[all …]
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | dev-mem2mem.rst | 20 both sides and finally call :ref:`VIDIOC_STREAMON <VIDIOC_STREAMON>`
|
| H A D | pixfmt-intro.rst | 8 necessary to have standard image data formats which both sides will
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | circular-buffers.rst | 145 There are two sides to this: the producer that fills the buffer, and the
148 two sides can operate simultaneously.
|
| /openbmc/linux/drivers/infiniband/hw/hfi1/ |
| H A D | opfn.h | 46 * for both sides and therefore can select the right parameters
|
| /openbmc/linux/arch/x86/include/asm/shared/ |
| H A D | tdx.h | 109 * guest sides of these calls.
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/jaketown/ |
| H A D | uncore-cache.json | 144 …, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
153 …, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
162 …, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
171 …, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
180 …, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
189 …, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
198 …, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
207 …, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
216 …, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
225 …, Cbo 0 UP AD is NOT the same ring as CBo 2 UP AD because they are on opposite sides of the ring.",
[all …]
|
| /openbmc/linux/drivers/thunderbolt/ |
| H A D | clx.c | 311 * CLx is enabled only if both sides of the link support CLx, and if both sides
|
| /openbmc/linux/Documentation/networking/ |
| H A D | plip.rst | 99 10^6/HZ usecs. If both sides of a PLIP connection are used in IRQ-less mode,
100 this timeout is required on both sides.
|