| /linux-6.15/Documentation/networking/pse-pd/ |
| H A D | pse-pi.rst | 3 PSE Power Interface (PSE PI) Documentation 24 PSE PI and Single Pair Ethernet 36 Understanding PSE PI 94 PSE PI compatibilities 154 Simple PSE PI Configuration for Alternative A 167 | PSE PI | 197 | PSE PI | 218 **Simple PSE PI Configuration:** 228 **Complex PSE PI Configuration:** 249 PSE PI Node: Essential Information [all …]
|
| /linux-6.15/Documentation/locking/ |
| H A D | futex-requeue-pi.rst | 2 Futex Requeue PI 5 Requeueing of tasks from a non-PI futex to a PI futex requires 7 left without an owner if it has waiters; doing so would break the PI 11 "PI". 51 previously mentioned PI-boosting algorithms. 54 be able to requeue tasks to PI futexes. This support implies that 56 user space already holding the PI futex. The glibc implementation 83 calls for the PI cases. Similar changes are needed for 106 to be requeued to a PI-aware futex. The implementation is the 116 PI futex on behalf of the top waiter. If it can, this waiter is [all …]
|
| H A D | pi-futex.rst | 2 Lightweight PI-futexes 7 - in the user-space fastpath a PI-enabled futex involves no kernel work 8 (or any other PI complexity) at all. No registration, no extra kernel 14 - the in-kernel PI implementation is streamlined around the mutex 23 The short reply: user-space PI helps achieving/improving determinism for 25 determinism and well-bound latencies. Even in the worst-case, PI will 78 As mentioned before, the userspace fastpath of PI-enabled pthread 94 own TID into the futex value], and attaches a 'PI state' structure to 114 there is no prior 'registration' of a PI-futex. [which is not quite 117 Also, under this scheme, 'robustness' and 'PI' are two orthogonal [all …]
|
| H A D | rt-mutex-design.rst | 58 Priority Inheritance (PI) 62 for this document. Here we only discuss PI. 77 the design that is used to implement PI. 79 PI chain 87 PI and spin locks that are used in the PI code, from now on 88 the PI locks will be called a mutex. 128 PI chain 205 Task PI Tree 208 To keep track of the PI chains, each process has its own PI rbtree. This is 224 Depth of the PI Chain [all …]
|
| H A D | rt-mutex.rst | 2 RT-mutex subsystem with PI support 5 RT-mutexes with priority inheritance are used to support PI-futexes, 8 about PI-futexes.]
|
| /linux-6.15/arch/m68k/fpsp040/ |
| H A D | stan.S | 84 |--TERM IN SGL. NOTE THAT PI IS 64-BIT LONG, THUS N*PI/2 IS AT 181 cmpil #0x4004BC7E,%d0 | ...|X| < 15 PI? 187 |--THIS IS THE USUAL CASE, |X| <= 15 PI. 190 fmuld TWOBYPI,%fp1 | ...X*2/PI 322 | ;create 2**16383*PI/2 327 | ;PI/2 at FP_SCR3 340 |--ON ENTRY, FP0 IS X, ON RETURN, FP0 IS X REM PI/2, |X| <= PI/4. 362 |--THAT INT( X * (2/PI) / 2**(L) ) < 2**29. 364 |--CREATE 2**(-L) * (2/PI), SIGN(INARG)*2**(63), 367 movel #0x00003FFE,%d2 | ...BIASED EXPO OF 2/PI [all …]
|
| H A D | sacos.S | 48 PI: .long 0x40000000,0xC90FDAA2,0x2168C235,0x00000000 label 57 |--ACOS(X) = PI/2 FOR DENORMALIZED X
|
| H A D | ssin.S | 194 cmpil #0x4004BC7E,%d0 | ...|X| < 15 PI? 199 |--THIS IS THE USUAL CASE, |X| <= 15 PI. 202 fmuld TWOBYPI,%fp1 | ...X*2/PI 205 lea PITBL+0x200,%a1 | ...TABLE OF N*PI/2, N = -32,...,32 459 addil #0x00003FFF,%d2 | ...BIASED EXPO OF 2**L * (PI/2) 548 cmpil #0x4004BC7E,%d0 | ...|X| < 15 PI? 554 |--THIS IS THE USUAL CASE, |X| <= 15 PI. 557 fmuld TWOBYPI,%fp1 | ...X*2/PI 560 lea PITBL+0x200,%a1 | ...TABLE OF N*PI/2, N = -32,...,32
|
| H A D | do_func.S | 57 PPIBY2: .long 0x3FFF0000,0xC90FDAA2,0x2168C235 |+PI/2 58 MPIBY2: .long 0xbFFF0000,0xC90FDAA2,0x2168C235 |-PI/2 504 |**Returns +PI/2 510 |**Returns -PI/2
|
| H A D | sasin.S | 92 |--|X| = 1, ASIN(X) = +- PI/2.
|
| H A D | satan.S | 402 |--IF |X| > 2^(100), RETURN SIGN(X)*(PI/2 - TINY). OTHERWISE, 403 |--RETURN SIGN(X)*PI/2 + ATAN(-1/X).
|
| /linux-6.15/Documentation/devicetree/bindings/net/pse-pd/ |
| H A D | pse-controller.yaml | 50 PSE PI for power delivery via pairsets, compliant with IEEE 59 Address describing the PSE PI index. 103 Polarity configuration supported by the PSE PI pairsets. 114 description: Regulator power supply for the PSE PI.
|
| /linux-6.15/Documentation/devicetree/bindings/powerpc/nintendo/ |
| H A D | gamecube.txt | 25 1.b) The Processor Interface (PI) node 33 - reg : should contain the PI registers location and length 39 the PI node.
|
| H A D | wii.txt | 34 1.b) The Processor Interface (PI) node 42 - reg : should contain the PI registers location and length 48 the PI node.
|
| /linux-6.15/arch/arm/boot/dts/nxp/imx/ |
| H A D | imx6q-pico-pi.dts | 15 model = "TechNexion PICO-IMX6 Quad Board and PI baseboard";
|
| H A D | imx6dl-pico-pi.dts | 15 model = "TechNexion PICO-IMX6 DualLite/Solo Board and PI baseboard";
|
| H A D | imx7d-pico-pi.dts | 8 model = "TechNexion PICO-IMX7D Board and PI baseboard";
|
| H A D | imx6ul-pico-pi.dts | 12 model = "TechNexion PICO-IMX6UL and PI baseboard";
|
| /linux-6.15/arch/arm64/boot/dts/freescale/ |
| H A D | imx8mp-aristainetos3-adpismarc.dts | 13 model = "Aristainetos3 ADLink PI SMARC carrier";
|
| /linux-6.15/arch/arm/boot/dts/ |
| H A D | cros-adc-thermistors.dtsi | 7 * Exynos5800 based Peach PI.
|
| /linux-6.15/Documentation/devicetree/bindings/ata/ |
| H A D | ahci-common.yaml | 72 Mask that indicates which ports the HBA supports. Useful if PI is not 96 more than 32 ports due to the CAP.NP fields and PI register size
|
| /linux-6.15/drivers/media/test-drivers/vidtv/ |
| H A D | vidtv_s302m.c | 48 #define PI 180 macro 262 pos = (2 * PI * ctx->note_offset * ctx->last_tone) / S302M_SAMPLING_RATE_HZ; in vidtv_s302m_get_sample() 265 return (fixp_sin32(pos % (2 * PI)) >> 16) + 0x8000; in vidtv_s302m_get_sample()
|
| /linux-6.15/drivers/staging/vc04_services/ |
| H A D | Kconfig | 10 by the Raspberry PI.
|
| /linux-6.15/drivers/net/wireless/realtek/rtl818x/ |
| H A D | Kconfig | 28 TrendNET TEW-288PI
|
| /linux-6.15/Documentation/driver-api/firmware/ |
| H A D | fallback-mechanisms.rst | 270 Initialization (PI) spec's Firmware Volume protocol. This has been rejected 271 because the FV Protocol relies on *internal* interfaces of the PI spec, and: 272 1. The PI spec does not define peripheral firmware at all 273 2. The internal interfaces of the PI spec do not guarantee any backward
|