Searched full:pi (Results 1 – 25 of 55) sorted by relevance
123
| /Documentation/locking/ |
| 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.
53 In order to support PI-aware pthread_condvar's, the kernel needs to
54 be able to requeue tasks to PI futexes. This support implies that
56 user space already holding the PI futex. The glibc implementation
81 The actual glibc implementation will likely test for PI and make the
83 calls for the PI cases. Similar changes are needed for
[all …]
|
| 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
66 Currently (without PI), if a high-prio and a low-prio task shares a lock
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
95 the futex-queue. The pi_state includes an rt-mutex, which is a PI-aware,
[all …]
|
| D | rt-mutex-design.rst | 17 inheritance (PI) algorithm that is used, as well as reasons for the
18 decisions that were made to implement PI in the manner that was done.
58 Priority Inheritance (PI)
62 for this document. Here we only discuss PI.
64 PI is where a process inherits the priority of another process if the other
77 the design that is used to implement PI.
79 PI chain
80 - The PI chain is an ordered series of locks and processes that cause
87 PI and spin locks that are used in the PI code, from now on
88 the PI locks will be called a mutex.
[all …]
|
| D | index.rst | 21 pi-futex
22 futex-requeue-pi
|
| D | rt-mutex.rst | 2 RT-mutex subsystem with PI support
5 RT-mutexes with priority inheritance are used to support PI-futexes,
7 (PTHREAD_PRIO_INHERIT). [See Documentation/locking/pi-futex.rst for more details
8 about PI-futexes.]
|
| /Documentation/hwmon/ |
| D | raspberrypi-hwmon.rst | 6 * Raspberry Pi A+ (via GPIO on SoC)
7 * Raspberry Pi B+ (via GPIO on SoC)
8 * Raspberry Pi 2 B (via GPIO on SoC)
9 * Raspberry Pi 3 B (via GPIO on port expander)
10 * Raspberry Pi 3 B+ (via PMIC)
|
| /Documentation/devicetree/bindings/gpio/ |
| D | raspberrypi,firmware-gpio.txt | 1 Raspberry Pi GPIO expander
3 The Raspberry Pi 3 GPIO expander is controlled by the VC4 firmware. The
7 The Raspberry Pi GPIO expander node must be a child node of the Raspberry Pi
|
| /Documentation/devicetree/bindings/arm/samsung/ |
| D | samsung-boards.yaml | 188 - description: Google Peach Pi Boards (Rev 10+)
190 - const: google,pi-rev16
191 - const: google,pi-rev15
192 - const: google,pi-rev14
193 - const: google,pi-rev13
194 - const: google,pi-rev12
195 - const: google,pi-rev11
196 - const: google,pi-rev10
197 - const: google,pi
|
| /Documentation/devicetree/bindings/powerpc/nintendo/ |
| D | gamecube.txt | 25 1.b) The Processor Interface (PI) node
32 - compatible : should be "nintendo,flipper-pi"
33 - reg : should contain the PI registers location and length
39 the PI node.
|
| D | wii.txt | 34 1.b) The Processor Interface (PI) node
41 - compatible : should be "nintendo,hollywood-pi","nintendo,flipper-pi"
42 - reg : should contain the PI registers location and length
48 the PI node.
|
| /Documentation/devicetree/bindings/arm/ |
| D | rda.yaml | 18 - xunlong,orangepi-2g-iot # Orange Pi 2G-IoT
19 - xunlong,orangepi-i96 # Orange Pi i96
|
| D | realtek.yaml | 48 - bananapi,bpi-m4 # Banana Pi BPI-M4
|
| /Documentation/translations/zh_CN/locking/ |
| D | index.rst | 31 * pi-futex
32 * futex-requeue-pi
|
| /Documentation/devicetree/bindings/riscv/ |
| D | thead.yaml | 24 - description: Sipeed Lichee Pi 4A board for the Sipeed Lichee Module 4A
27 - sipeed,lichee-pi-4a
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-pci-devices-pvpanic | 4 Contact: zhenwei pi <pizhenwei@bytedance.com>
18 Contact: zhenwei pi <pizhenwei@bytedance.com>
|
| /Documentation/devicetree/bindings/net/ |
| D | microchip,lan78xx.txt | 4 an external EEPROM, but some platforms (e.g. Raspberry Pi 3 B+) have neither.
20 /* Based on the configuration for a Raspberry Pi 3 B+ */
|
| D | davicom,dm9051.yaml | 45 # Raspberry Pi platform
47 /* for Raspberry Pi with pin control stuff for GPIO irq */
|
| /Documentation/devicetree/bindings/soc/bcm/ |
| D | raspberrypi,bcm2835-power.txt | 1 Raspberry Pi power domain driver
|
| /Documentation/devicetree/bindings/display/panel/ |
| D | bananapi,s070wv20-ct16.yaml | 7 title: Banana Pi 7" (S070WV20-CT16) TFT LCD Panel
|
| /Documentation/devicetree/bindings/display/ |
| D | brcm,bcm2835-vc4.yaml | 13 The VC4 device present on the Raspberry Pi includes a display system
|
| D | himax,hx8357d.txt | 4 mode, such as the Adafruit 3.5" TFT for Raspberry Pi.
|
| /Documentation/devicetree/bindings/ata/ |
| 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
|
| /Documentation/devicetree/bindings/input/touchscreen/ |
| D | raspberrypi,firmware-ts.txt | 1 Raspberry Pi firmware based 7" touchscreen
|
| /Documentation/devicetree/bindings/pwm/ |
| D | pwm-bcm2835.yaml | 7 title: BCM2835 PWM controller (Raspberry Pi controller)
|
| /Documentation/devicetree/bindings/regulator/ |
| D | google,cros-ec-regulator.yaml | 10 - Pi-Hsun Shih <pihsun@chromium.org>
|
123