| /linux/Documentation/hwmon/ |
| H A D | xdpe152c4.rst | 37 The driver provides for current: input, maximum and critical thresholds
38 and maximum and critical alarms. Low Critical thresholds and Low critical alarm are
61 The driver provides for voltage: input, critical and low critical thresholds
62 and critical and low critical alarms.
106 The driver provides for temperature: input, maximum and critical thresholds
107 and maximum and critical alarms.
|
| H A D | xdpe12284.rst | 48 The driver provides for current: input, maximum and critical thresholds
49 and maximum and critical alarms. Critical thresholds and critical alarm are
66 The driver provides for voltage: input, critical and low critical thresholds
67 and critical and low critical alarms.
94 The driver provides for temperature: input, maximum and critical thresholds
95 and maximum and critical alarms.
|
| H A D | spd5118.rst | 34 minimum, maximum, and critical temperature can be configured. There are alarms
35 for low critical, low, high, and critical thresholds.
43 temp1_lcrit Low critical high temperature (RW)
48 temp1_lcrit_alarm Temperature low critical alarm
51 temp1_crit_alarm Temperature critical alarm
|
| H A D | stpddc60.rst | 63 in1_lcrit_alarm Input voltage critical low alarm.
64 in1_crit_alarm Input voltage critical high alarm.
70 in2_lcrit_alarm Critical output voltage critical low alarm.
71 in2_crit_alarm Critical output voltage critical high alarm.
78 curr1_crit_alarm Output current critical high alarm.
83 power1_crit_alarm Output power critical high alarm.
|
| H A D | ir38064.rst | 60 curr1_crit_alarm Current critical high alarm
67 in1_crit_alarm Input voltage critical high alarm
74 in2_lcrit_alarm Output voltage critical low alarm
76 in2_crit_alarm Output voltage critical high alarm
87 temp1_crit_alarm Chip temperature critical high alarm
|
| H A D | pxe1610.rst | 81 curr[2-4]_crit_alarm Current critical high alarm
86 in1_crit_alarm Input voltage critical high alarm
91 in[2-4]_lcrit_alarm Output voltage critical low alarm
93 in[2-4]_crit_alarm Output voltage critical high alarm
104 temp[1-3]_crit_alarm Chip temperature critical high alarm
|
| H A D | ir35221.rst | 47 curr[2-3]_crit_alarm Current critical high alarm
56 in1_crit_alarm Input voltage critical high alarm
65 in[2-3]_lcrit_alarm Output voltage critical low alarm
67 in[2-3]_crit_alarm Output voltage critical high alarm
87 temp[1-2]_crit_alarm Chip temperature critical high alarm
|
| H A D | adt7410.rst | 54 exceeded, as well as a critical temperature (CT) pin to indicate that the
55 critical temperature set point has been exceeded. Both pins can be set up with a
75 maximum and critical temperature, it can only be set for temp#_max_hyst.
87 temp#_crit critical temperature setpoint
90 temp#_crit_hyst hysteresis for critical temperature (read-only)
93 temp#_crit_alarm critical temperature alarm flag
|
| H A D | pli1209bc.rst | 39 in1_crit_alarm Input voltage critical alarm.
52 curr1_crit_alarm Input current critical alarm.
57 curr2_crit_alarm Output current critical alarm.
74 temp1_crit_alarm Die temperature critical alarm.
|
| H A D | acbel-fsg032.rst | 30 curr1_crit_alarm Input current critical alarm.
37 curr2_crit_alarm Output current critical alarm.
56 in2_crit_alarm Output voltage critical high alarm.
60 in2_lcrit_alarm Output voltage critical low alarm.
|
| H A D | ucd9200.rst | 70 in1_lcrit_alarm Voltage critical low alarm. From VIN_UV_FAULT status.
71 in1_crit_alarm Voltage critical high alarm. From VIN_OV_FAULT status.
82 in[2-5]_lcrit_alarm Voltage critical low alarm. From VOLTAGE_UV_FAULT
84 in[2-5]_crit_alarm Voltage critical high alarm. From VOLTAGE_OV_FAULT
98 curr[2-5]_crit_alarm Current critical high alarm. From IOUT_OC_FAULT status.
119 temp[1-5]_crit_alarm Temperature critical high alarm.
|
| H A D | lt7182s.rst | 60 in[1-2]_crit_alarm Input voltage critical high alarm
76 in[3-4|6-7]_lcrit_alarm Output voltage critical low alarm
82 in[3-4|6-7]_crit_alarm Output voltage critical high alarm
89 temp1_crit_alarm Chip temperature critical high alarm
|
| /linux/arch/arm64/boot/dts/ti/ |
| H A D | k3-j721s2-thermal.dtsi | 17 type = "critical";
31 type = "critical";
45 type = "critical";
59 type = "critical";
73 type = "critical";
87 type = "critical";
101 type = "critical";
|
| H A D | k3-j721e-thermal.dtsi | 18 type = "critical";
32 type = "critical";
46 type = "critical";
60 type = "critical";
74 type = "critical";
|
| H A D | k3-j7200-thermal.dtsi | 18 type = "critical";
32 type = "critical";
46 type = "critical";
|
| H A D | k3-am654-industrial-thermal.dtsi | 17 type = "critical";
31 type = "critical";
45 type = "critical";
|
| H A D | k3-am62a-thermal.dtsi | 24 type = "critical";
55 type = "critical";
86 type = "critical";
|
| H A D | k3-am62p-j722s-common-thermal.dtsi | 24 type = "critical";
55 type = "critical";
86 type = "critical";
|
| /linux/Documentation/virt/ |
| H A D | paravirt_ops.rst | 11 hypervisors. It allows each hypervisor to override critical operations and
16 corresponding to low-level critical instructions and high-level
18 time by enabling binary patching of the low-level critical operations
28 Usually these operations correspond to low-level critical instructions. They
29 are called frequently and are performance critical. The overhead is
35 them are very performance critical.
|
| /linux/arch/arm64/boot/dts/qcom/ |
| H A D | glymur.dtsi | 5455 "critical";
5470 "critical";
5485 "critical";
5500 "critical";
5515 "critical";
5530 "critical";
5545 "critical";
5560 "critical";
8170 aoss-0-critical {
8173 type = "critical";
[all …]
|
| /linux/tools/memory-model/ |
| H A D | lock.cat | 53 * inside a critical section (for the same lock) always deadlock.
58 * In the same way, spin_is_locked() inside a critical section must always
59 * return True (no RU events can be in a critical section for the same lock).
77 let critical = ([LKW] ; po-loc ; [UL]) \ (po-loc ; [LKW | UL] ; po-loc)
79 flag ~empty UL \ range(critical) as unmatched-unlock
82 let UNMATCHED-LKW = LKW \ domain(critical)
85 (* rfi for LF events: link each LKW to the LF events in its critical section *)
92 * If a given LF event e is outside a critical section, it cannot read
144 let co = (co | critical | (critical^-1 ; co))+
|
| /linux/Documentation/litmus-tests/rcu/ |
| H A D | RCU+sync+read.litmus | 7 * sees all stores done in prior RCU read-side critical sections. Such
8 * read-side critical sections would have ended before the grace period ended.
11 * other things) that an RCU read-side critical section cannot span a grace period.
|
| /linux/arch/arm/boot/dts/samsung/ |
| H A D | exynos5422-odroidhc1.dts | 49 type = "critical";
104 type = "critical";
148 type = "critical";
192 type = "critical";
236 type = "critical";
|
| /linux/Documentation/userspace-api/ |
| H A D | rseq.rst | 64 - The rseq_cs critical section field
84 are rewritten and eventually active critical sections are aborted
89 active critical sections are aborted before these threads return to
102 updates and critical section checks even if not strictly required by the
122 critical section to avoid contention on a resource when the thread is
123 scheduled out inside of the critical section.
186 If the request bit is still set when the leaving the critical section,
190 leaving the critical section to relinquish the CPU. The kernel enforces
195 critical section, then this indicates that a grant was revoked and no
228 critical section and requesting the time slice extension has no control
[all …]
|
| /linux/Documentation/RCU/Design/Requirements/ |
| H A D | Requirements.rst | 74 of all pre-existing RCU read-side critical sections. An RCU read-side
75 critical section begins with the marker rcu_read_lock() and ends
77 RCU treats a nested set as one big RCU read-side critical section.
173 The RCU read-side critical section in do_something_dlm() works with
191 critical section must not contain calls to synchronize_rcu().
192 Similarly, an RCU read-side critical section must not contain anything
370 outermost RCU read-side critical section containing that
387 #. Wait for all pre-existing RCU read-side critical sections to complete
427 read-side critical section or in a code segment where the pointer
487 #. Each CPU that has an RCU read-side critical section that begins
[all …]
|