Searched full:sides (Results 1 – 25 of 283) sorted by relevance
12345678910>>...12
| /kernel/linux/linux-5.10/drivers/net/wireless/ath/ |
| 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]
|
| /kernel/linux/linux-6.6/drivers/net/wireless/ath/ |
| 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]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/i2c/ |
| D | i2c-arb-gpio-challenge.txt | 33 2. Waits a little bit for the other sides to notice (slew time, say 10
45 - their-claim-gpios: The GPIOs that the other sides use to claim the bus.
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/i2c/ |
| 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
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/ivytown/ |
| 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 …]
|
| /kernel/linux/linux-6.6/drivers/usb/host/ |
| 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.
|
| /kernel/linux/linux-5.10/drivers/usb/host/ |
| 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.
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | rbtree_latch.h | 12 * lookups; but has the constraint (inherent to the seqlock) that read sides
13 * cannot nest in write sides.
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | rbtree_latch.h | 12 * lookups; but has the constraint (inherent to the seqlock) that read sides
13 * cannot nest in write sides.
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/snowridgex/ |
| 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 …]
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/v4l/ |
| D | dev-mem2mem.rst | 20 both sides and finally call :ref:`VIDIOC_STREAMON <VIDIOC_STREAMON>`
|
| D | pixfmt-intro.rst | 8 necessary to have standard image data formats which both sides will
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | dev-mem2mem.rst | 20 both sides and finally call :ref:`VIDIOC_STREAMON <VIDIOC_STREAMON>`
|
| D | pixfmt-intro.rst | 8 necessary to have standard image data formats which both sides will
|
| /kernel/linux/linux-6.6/Documentation/core-api/ |
| 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.
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| 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.
|
| /kernel/linux/linux-5.10/drivers/staging/vc04_services/interface/vchiq_arm/ |
| D | vchiq_arm.h | 47 ** This means that both sides should be fully ready, and we should
|
| /kernel/linux/linux-6.6/drivers/infiniband/hw/hfi1/ |
| D | opfn.h | 46 * for both sides and therefore can select the right parameters
|
| /kernel/linux/linux-5.10/drivers/infiniband/hw/hfi1/ |
| D | opfn.h | 46 * for both sides and therefore can select the right parameters
|
| /kernel/linux/linux-6.6/arch/x86/include/asm/shared/ |
| D | tdx.h | 100 * guest sides of these calls.
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/jaketown/ |
| 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 …]
|
| /kernel/linux/linux-6.6/drivers/thunderbolt/ |
| D | clx.c | 311 * CLx is enabled only if both sides of the link support CLx, and if both sides
|
| /kernel/linux/linux-5.10/Documentation/networking/ |
| 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.
|
| /kernel/linux/linux-6.6/Documentation/networking/ |
| 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.
|
| /kernel/linux/linux-6.6/Documentation/driver-api/ |
| D | xillybus.rst | 54 building block, with electrical wires dangling on the sides for connection to
268 sides, the implementation relies on a set of DMA buffers which is allocated
277 control mechanisms exist on both sides to prevent underflows and overflows.
|
12345678910>>...12