Searched refs:critical (Results 1 – 25 of 372) sorted by relevance
12345678910>>...15
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| D | smm665.rst | 79 Each monitored channel has its own high and low limits, plus a critical
149 in1_lcrit 12v input critical minimum voltage (mV)
150 in2_lcrit 3.3V (VDD) input critical minimum voltage (mV)
151 in3_lcrit Channel A critical minimum voltage (mV)
152 in4_lcrit Channel B critical minimum voltage (mV)
153 in5_lcrit Channel C critical minimum voltage (mV)
154 in6_lcrit Channel D critical minimum voltage (mV)
155 in7_lcrit Channel E critical minimum voltage (mV)
156 in8_lcrit Channel F critical minimum voltage (mV)
157 in9_lcrit AIN1 critical minimum voltage (mV)
[all …]
|
| D | isl68137.rst | 437 curr1_crit_alarm Current critical high alarm
442 curr[2-3]_crit_alarm Current critical high alarm
447 in1_lcrit_alarm Input voltage critical low alarm
449 in1_crit_alarm Input voltage critical high alarm
454 in[2-3]_lcrit_alarm Output voltage critical low alarm
456 in[2-3]_crit_alarm Output voltage critical high alarm
467 temp[1-3]_crit_alarm Chip temperature critical high alarm
479 curr1_crit_alarm Current critical high alarm
484 curr2_crit_alarm Current critical high alarm
489 in1_lcrit_alarm Input voltage critical low alarm
[all …]
|
| D | xdpe12284.rst | 44 The driver provides for current: input, maximum and critical thresholds
45 and maximum and critical alarms. Critical thresholds and critical alarm are
62 The driver provides for voltage: input, critical and low critical thresholds
63 and critical and low critical alarms.
90 The driver provides for temperature: input, maximum and critical thresholds
91 and maximum and critical alarms.
|
| D | ir38064.rst | 36 curr1_crit_alarm Current critical high alarm
43 in1_crit_alarm Input voltage critical high alarm
50 in2_lcrit_alarm Output voltage critical low alarm
52 in2_crit_alarm Output voltage critical high alarm
63 temp1_crit_alarm Chip temperature critical high alarm
|
| D | zl6100.rst | 173 in1_lcrit_alarm Input voltage critical low alarm.
174 in1_crit_alarm Input voltage critical high alarm.
182 in2_lcrit_alarm VMON/VDRV voltage critical low alarm.
183 in2_crit_alarm VMON/VDRV voltage critical high alarm.
192 inX_lcrit_alarm Critical output voltage critical low alarm.
193 inX_crit_alarm Critical output voltage critical high alarm.
201 curr1_lcrit_alarm Output current critical low alarm.
202 curr1_crit_alarm Output current critical high alarm.
211 temp[12]_lcrit_alarm Chip temperature critical low alarm.
212 temp[12]_crit_alarm Chip temperature critical high alarm.
|
| 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
|
| 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
|
| D | tps53679.rst | 84 in1_lcrit_alarm Input voltage critical low alarm.
90 in1_crit_alarm Input voltage critical high alarm.
115 in[N]_crit_alarm Output voltage critical high alarm.
130 temp[N]_crit_alarm Temperature critical high alarm.
153 curr1_crit_alarm Input current critical alarm.
173 curr[N]_crit_alarm Output current critical high alarm.
|
| 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
|
| D | max8688.rst | 57 in1_lcrit_alarm Voltage critical low alarm. From VOLTAGE_UV_FAULT
59 in1_crit_alarm Voltage critical high alarm. From VOLTAGE_OV_FAULT
70 curr1_crit_alarm Current critical high alarm. From IOUT_OC_FAULT status.
80 temp1_crit_alarm Chip temperature critical high alarm. Set by comparing
|
| 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.
|
| D | ina2xx.rst | 104 in0_lcrit_alarm Shunt voltage critical low alarm
105 in0_crit_alarm Shunt voltage critical high alarm
108 in1_lcrit_alarm Bus voltage critical low alarm
109 in1_crit_alarm Bus voltage critical high alarm
111 power1_crit_alarm Power critical high alarm
|
| /kernel/linux/linux-5.10/Documentation/locking/ |
| D | seqlock.rst | 15 read side critical section is even and the same sequence count value is
16 read again at the end of the critical section. The data in the set must
17 be copied out inside the read side critical section. If the sequence
18 count has changed between the start and the end of the critical section,
22 critical section. After starting the critical section the sequence count
24 the end of the write side critical section the sequence count becomes
27 A sequence counter write side critical section must never be preempted
43 multiple writers. Write side critical sections must thus be serialized
76 /* ... [[write-side critical section]] ... */
85 /* ... [[read-side critical section]] ... */
[all …]
|
| /kernel/linux/linux-5.10/Documentation/virt/ |
| 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-ops 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.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/thermal/ |
| D | brcm,sr-thermal.txt | 41 type = "critical";
53 type = "critical";
65 type = "critical";
77 type = "critical";
89 type = "critical";
101 type = "critical";
|
| /kernel/linux/linux-5.10/Documentation/RCU/ |
| D | lockdep.rst | 9 critical section. Each flavor of RCU is tracked separately (but note
31 Check for RCU read-side critical section.
33 Check for RCU-bh read-side critical section.
35 Check for RCU-sched read-side critical section.
37 Check for SRCU read-side critical section.
80 1. An RCU read-side critical section (implicit), or
85 RCU read-side critical sections, in case (2) the ->file_lock prevents
96 complain if this was used in an RCU read-side critical section unless one
105 critical section. However, a lockdep expression can be passed to them
108 false and they are called from outside any RCU read-side critical section.
[all …]
|
| D | lockdep-splat.rst | 15 RCU read-side critical section or (2) holding the right update-side lock.
72 This form says that it must be in a plain vanilla RCU read-side critical
84 code was invoked either from within an RCU read-side critical section
89 On the other hand, perhaps we really do need an RCU read-side critical
90 section. In this case, the critical section must span the use of the
104 read-side critical section, which again would have suppressed the
|
| D | whatisRCU.rst | 95 critical sections.
157 entering an RCU read-side critical section. It is illegal
158 to block while in an RCU read-side critical section, though
160 read-side critical sections. Any RCU-protected data structure
161 accessed during an RCU read-side critical section is guaranteed to
162 remain unreclaimed for the full duration of that critical section.
171 exiting an RCU read-side critical section. Note that RCU
172 read-side critical sections may be nested and/or overlapping.
180 read-side critical sections on all CPUs have completed.
182 any subsequent RCU read-side critical sections to complete.
[all …]
|
| /kernel/linux/linux-5.10/arch/arm64/boot/dts/ti/ |
| D | k3-am654-industrial-thermal.dtsi | 14 type = "critical";
28 type = "critical";
42 type = "critical";
|
| /kernel/linux/linux-5.10/drivers/acpi/ |
| D | thermal.c | 111 u8 critical:1; member
151 struct acpi_thermal_critical critical; member
277 tz->trips.critical.temperature = tmp; in acpi_thermal_trips_update()
285 tz->trips.critical.flags.valid = 0; in acpi_thermal_trips_update()
291 tz->trips.critical.flags.valid = 0; in acpi_thermal_trips_update()
293 tz->trips.critical.flags.valid = 1; in acpi_thermal_trips_update()
296 tz->trips.critical.temperature)); in acpi_thermal_trips_update()
298 if (tz->trips.critical.flags.valid == 1) { in acpi_thermal_trips_update()
300 tz->trips.critical.flags.valid = 0; in acpi_thermal_trips_update()
307 if (crt_k > tz->trips.critical.temperature) in acpi_thermal_trips_update()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/litmus-tests/rcu/ |
| 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.
|
| /kernel/linux/linux-5.10/arch/arm64/boot/dts/nvidia/ |
| D | tegra194-p3509-0000+p3668-0000.dts | 269 cpu_trip_critical: critical {
272 type = "critical";
295 cpu-critical {
323 gpu_alert0: critical {
326 type = "critical";
337 aux_alert0: critical {
340 type = "critical";
|
| D | tegra194-p2972-0000.dts | 273 cpu_trip_critical: critical {
276 type = "critical";
299 cpu-critical {
327 gpu_alert0: critical {
330 type = "critical";
341 aux_alert0: critical {
344 type = "critical";
|
| /kernel/linux/linux-5.10/tools/memory-model/ |
| D | lock.cat | 53 * inside a critical section (for the same lock) always deadlock.
71 let critical = ([LKW] ; po-loc ; [UL]) \ (po-loc ; [LKW | UL] ; po-loc)
73 flag ~empty UL \ range(critical) as unmatched-unlock
76 let UNMATCHED-LKW = LKW \ domain(critical)
79 (* rfi for LF events: link each LKW to the LF events in its critical section *)
102 * within one of the lock's critical sections returns False.
130 let co = (co | critical | (critical^-1 ; co))+
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | exynos5422-odroidhc1.dts | 47 type = "critical";
102 type = "critical";
146 type = "critical";
190 type = "critical";
234 type = "critical";
|
12345678910>>...15