Home
last modified time | relevance | path

Searched full:p0 (Results 1 – 25 of 40) sorted by relevance

12

/Documentation/devicetree/bindings/ata/
Dceva,ahci-1v84.yaml41 ceva,p0-cominit-params:
46 ceva,p0-cominit-params = /bits/ 8 <CIBGMN CIBGMX CIBGN CINMP>;
53 ceva,p0-comwake-params:
58 ceva,p0-comwake-params = /bits/ 8 <CWBGMN CWBGMX CWBGN CWNMP>;
65 ceva,p0-burst-params:
70 ceva,p0-burst-params = /bits/ 8 <BMX BNM SFD PTST>;
77 ceva,p0-retry-params:
82 ceva,p0-retry-params = /bits/ 16 <RIT RCT>;
153 - ceva,p0-cominit-params
154 - ceva,p0-comwake-params
[all …]
/Documentation/scheduler/
Dsched-util-clamp.rst199 +- p0 +- p3 +- p4
279 p0->uclamp[UCLAMP_MIN] = 300
280 p0->uclamp[UCLAMP_MAX] = 900
285 then assuming both p0 and p1 are enqueued to the same rq, both UCLAMP_MIN
404 p0->uclamp[UCLAMP_MIN] = // system default;
405 p0->uclamp[UCLAMP_MAX] = // system default;
416 when p0 and p1 are attached to cgroup0, the values become:
420 p0->uclamp[UCLAMP_MIN] = cgroup0->cpu.uclamp.min = 20% * 1024;
421 p0->uclamp[UCLAMP_MAX] = cgroup0->cpu.uclamp.max = 60% * 1024;
426 when p0 and p1 are attached to cgroup1, these instead become:
[all …]
Dschedutil.rst65 f_cur := ----- * P0
70 P0; otherwise
/Documentation/devicetree/bindings/phy/
Dairoha,en7581-pcie-phy.yaml33 - const: p0-xr-dtime
66 "p0-xr-dtime", "p1-xr-dtime",
/Documentation/litmus-tests/atomic/
DAtomic-RMW-ops-are-atomic-WRT-atomic_set.litmus14 P0(atomic_t *v)
Dcmpxchg-fail-ordered-2.litmus12 P0(int *x, int *y)
DAtomic-RMW+mb__after_atomic-is-stronger-than-acquire.litmus14 P0(int *x, atomic_t *y)
Dcmpxchg-fail-unordered-2.litmus13 P0(int *x, int *y)
Dcmpxchg-fail-ordered-1.litmus12 P0(int *x, int *y, int *z)
Dcmpxchg-fail-unordered-1.litmus13 P0(int *x, int *y, int *z)
/Documentation/translations/zh_CN/scheduler/
Dschedutil.rst65 f_cur := ----- * P0
70 P0; 其它情况
/Documentation/devicetree/bindings/pinctrl/
Dmarvell,armada-375-pinctrl.txt40 mpp24 24 gpio, led(p0), ge1(rxd0), sd(cmd), uart0(rts)
62 mpp46 46 gpio, led(p0), ge0(txd0), ge1(txd0), dev(we1)
77 mpp61 61 gpio, i2c1(sda), uart1(rxd), spi1(cs2), led(p0)
/Documentation/arch/x86/
Dresctrl.rst884 # mkdir p0 p1
885 # echo "L3:0=3;1=c\nMB:0=50;1=50" > /sys/fs/resctrl/p0/schemata
891 Tasks that are under the control of group "p0" may only allocate from the
895 Similarly, tasks that are under the control of group "p0" may use a
907 # echo "L3:0=3;1=c\nMB:0=1024;1=500" > /sys/fs/resctrl/p0/schemata
910 In the above example the tasks in "p1" and "p0" on socket 0 would use a max b/w
936 # mkdir p0
937 # echo "L3:0=f8000;1=fffff" > p0/schemata
945 # echo 1234 > p0/tasks
962 # echo -e "L3:0=f8000;1=fffff\nMB:0=20;1=100" > p0/schemata
[all …]
/Documentation/litmus-tests/locking/
DRM-broken.litmus16 P0(int *x, atomic_t *y, spinlock_t *lck)
DRM-fixed.litmus16 P0(int *x, atomic_t *y, spinlock_t *lck)
DDCL-broken.litmus15 P0(int *flag, int *data, spinlock_t *lck)
DDCL-fixed.litmus16 P0(int *flag, int *data, spinlock_t *lck)
/Documentation/litmus-tests/rcu/
DRCU+sync+read.litmus19 P0(int *x, int *y)
DRCU+sync+free.litmus24 P0(int *x, int *z, int **y)
/Documentation/devicetree/bindings/gpio/
Dnxp,lpc3220-gpio.yaml25 0: GPIO P0
/Documentation/devicetree/bindings/soc/imx/
Dfsl,imx-anatop.yaml46 "regulator-((1p1)|(2p5)|(3p0)|(vddcore)|(vddpu)|(vddsoc))$":
70 reg_3p0: regulator-3p0 {
/Documentation/
Datomic_t.txt97 P0(atomic_t *v)
241 P0(int *x, atomic_t *y)
263 P0 P1
/Documentation/devicetree/bindings/nvmem/
Dmediatek,efuse.yaml86 u2_intr_p0: usb2-intr-p0@188,1 {
/Documentation/input/devices/
Delantech.rst470 p3 p1 p2 p0 y11 y10 y9 y8
472 p7..p0 = pressure (not EF113)
603 p3 p1 p2 p0 y11 y10 y9 y8
605 p7..p0 = pressure
728 p3 p1 p2 p0 y11 y10 y9 y8
730 p7..p0 = pressure
/Documentation/litmus-tests/
DREADME66 The counterpart to RM-broken.litmus, showing P0()'s two loads from

12