| /Linux-v4.19/Documentation/hwmon/ |
| D | smm665 | 52 Each monitored channel has its own high and low limits, plus a critical
120 in1_lcrit 12v input critical minimum voltage (mV)
121 in2_lcrit 3.3V (VDD) input critical minimum voltage (mV)
122 in3_lcrit Channel A critical minimum voltage (mV)
123 in4_lcrit Channel B critical minimum voltage (mV)
124 in5_lcrit Channel C critical minimum voltage (mV)
125 in6_lcrit Channel D critical minimum voltage (mV)
126 in7_lcrit Channel E critical minimum voltage (mV)
127 in8_lcrit Channel F critical minimum voltage (mV)
128 in9_lcrit AIN1 critical minimum voltage (mV)
[all …]
|
| D | zl6100 | 121 in1_lcrit_alarm Input voltage critical low alarm.
122 in1_crit_alarm Input voltage critical high alarm.
130 in2_lcrit_alarm VMON/VDRV voltage critical low alarm.
131 in2_crit_alarm VMON/VDRV voltage critical high alarm.
140 inX_lcrit_alarm Critical output voltage critical low alarm.
141 inX_crit_alarm Critical output voltage critical high alarm.
149 curr1_lcrit_alarm Output current critical low alarm.
150 curr1_crit_alarm Output current critical high alarm.
159 temp[12]_lcrit_alarm Chip temperature critical low alarm.
160 temp[12]_crit_alarm Chip temperature critical high alarm.
|
| D | ir35221 | 43 curr[2-3]_crit_alarm Current critical high alarm
52 in1_crit_alarm Input voltage critical high alarm
61 in[2-3]_lcrit_alarm Output voltage critical low alarm
63 in[2-3]_crit_alarm Output voltage critical high alarm
83 temp[1-2]_crit_alarm Chip temperature critical high alarm
|
| D | adt7410 | 35 exceeded, as well as a critical temperature (CT) pin to indicate that the
36 critical temperature set point has been exceeded. Both pins can be set up with a
56 maximum and critical temperature, it can only be set for temp#_max_hyst.
67 temp#_crit - critical temperature setpoint
70 temp#_crit_hyst - hysteresis for critical temperature (read-only)
73 temp#_crit_alarm - critical temperature alarm flag
|
| D | max8688 | 51 in1_lcrit_alarm Voltage critical low alarm. From VOLTAGE_UV_FAULT status.
52 in1_crit_alarm Voltage critical high alarm. From VOLTAGE_OV_FAULT status.
61 curr1_crit_alarm Current critical high alarm. From IOUT_OC_FAULT status.
71 temp1_crit_alarm Chip temperature critical high alarm. Set by comparing
|
| D | ucd9200 | 63 in1_lcrit_alarm Voltage critical low alarm. From VIN_UV_FAULT status.
64 in1_crit_alarm Voltage critical high alarm. From VIN_OV_FAULT status.
74 in[2-5]_lcrit_alarm Voltage critical low alarm. From VOLTAGE_UV_FAULT status.
75 in[2-5]_crit_alarm Voltage critical high alarm. From VOLTAGE_OV_FAULT status.
87 curr[2-5]_crit_alarm Current critical high alarm. From IOUT_OC_FAULT status.
108 temp[1-5]_crit_alarm Temperature critical high alarm.
|
| D | pmbus | 50 Each monitored channel has its own high and low limits, plus a critical
162 inX_lcrit_alarm Voltage critical low alarm.
164 inX_crit_alarm Voltage critical high alarm.
179 currX_lcrit_alarm Output current critical low alarm.
181 currX_crit_alarm Current critical high alarm.
193 powerX_crit_alarm Output power critical high alarm.
211 tempX_lcrit_alarm Chip temperature critical low alarm. Set by comparing
214 tempX_crit_alarm Chip temperature critical high alarm. Set by comparing
|
| D | ltc2978 | 111 in1_lcrit_alarm Input voltage critical low alarm.
114 in1_crit_alarm Input voltage critical high alarm.
135 in[N]_lcrit_alarm Output voltage critical low alarm.
136 in[N]_crit_alarm Output voltage critical high alarm.
162 temp[N]_lcrit_alarm Temperature critical low alarm.
163 temp[N]_crit_alarm Temperature critical high alarm.
206 curr[N]_crit_alarm Output current critical high alarm.
207 curr[N]_lcrit_alarm Output current critical low alarm.
|
| D | lm77 | 22 critical (temp1_crit.) It also implements an hysteresis mechanism which
29 difference staying unchanged. For example, if the old critical limit
31 the critical limit to 90 degrees C, then the hysteresis will
|
| D | max20751 | 50 in1_lcrit_alarm Input voltage critical low alarm.
61 in2_lcrit_alarm Output voltage critical low alarm.
74 temp1_crit_alarm Chip temperature critical high alarm.
|
| D | max31785 | 40 in[1-6]_crit_alarm Output voltage critical high alarm
44 in[1-6]_lcrit_alarm Output voltage critical low alarm
57 temp[1-11]_crit_alarm Chip temperature critical high alarm
|
| D | max16064 | 51 in[1-4]_lcrit_alarm Voltage critical low alarm. From VOLTAGE_UV_FAULT status.
52 in[1-4]_crit_alarm Voltage critical high alarm. From VOLTAGE_OV_FAULT status.
62 temp1_crit_alarm Chip temperature critical high alarm. Set by comparing
|
| D | emc1403 | 42 (tempX_max) and critical (tempX_crit.) The chips also implement an
50 difference staying unchanged. For example, if the old critical limit
52 the critical limit to 90 degrees C, then the hysteresis will
|
| /Linux-v4.19/Documentation/virtual/ |
| D | paravirt_ops.txt | 8 hypervisors. It allows each hypervisor to override critical operations and
13 corresponding to low level critical instructions and high level
15 time by enabling binary patching of the low-ops critical operations
25 Usually these operations correspond to low level critical instructions. They
26 are called frequently and are performance critical. The overhead is
32 them are very performance critical.
|
| /Linux-v4.19/Documentation/RCU/ |
| D | lockdep.txt | 5 critical section. Each flavor of RCU is tracked separately (but note
27 Check for RCU read-side critical section.
29 Check for RCU-bh read-side critical section.
31 Check for RCU-sched read-side critical section.
33 Check for SRCU read-side critical section.
76 1. An RCU read-side critical section (implicit), or
81 RCU read-side critical sections, in case (2) the ->file_lock prevents
92 complain if this was used in an RCU read-side critical section unless one
101 being in an RCU read-side critical section. In the future, separate
|
| D | lockdep-splat.txt | 9 RCU read-side critical section or (2) holding the right update-side lock.
67 This form says that it must be in a plain vanilla RCU read-side critical
79 code was invoked either from within an RCU read-side critical section
84 On the other hand, perhaps we really do need an RCU read-side critical
85 section. In this case, the critical section must span the use of the
99 read-side critical section, which again would have suppressed the
|
| D | whatisRCU.txt | 83 critical sections.
143 entering an RCU read-side critical section. It is illegal
144 to block while in an RCU read-side critical section, though
146 read-side critical sections. Any RCU-protected data structure
147 accessed during an RCU read-side critical section is guaranteed to
148 remain unreclaimed for the full duration of that critical section.
157 exiting an RCU read-side critical section. Note that RCU
158 read-side critical sections may be nested and/or overlapping.
166 read-side critical sections on all CPUs have completed.
168 any subsequent RCU read-side critical sections to complete.
[all …]
|
| D | UP.txt | 47 all RCU read-side critical sections currently executing have completed.
65 the same critical section, then the code would need to create
102 list, and is therefore within an RCU read-side critical section.
104 read-side critical section, and is not permitted to block.
119 the process-context critical section. This would result in
132 of an RCU read-side critical section. If synchronize_rcu()
|
| D | checklist.txt | 55 2. Do the RCU read-side critical sections make proper use of
69 critical section is every bid as bad as letting them leak out
72 -before- letting them out of the RCU read-side critical section.
152 of an RCU read-side critical section. See lockdep.txt
183 be traversed by an RCU read-side critical section.
308 critical section or must be protected by appropriate update-side
309 locks. RCU read-side critical sections are delimited by
321 10. Conversely, if you are in an RCU read-side critical section,
329 critical sections complete. It does -not- necessarily guarantee
332 read-side critical sections are protected by something other
[all …]
|
| /Linux-v4.19/drivers/acpi/ |
| D | thermal.c | 124 u8 critical:1; member
164 struct acpi_thermal_critical critical; member
293 tz->trips.critical.temperature = tmp; in acpi_thermal_trips_update()
301 tz->trips.critical.flags.valid = 0; in acpi_thermal_trips_update()
307 tz->trips.critical.flags.valid = 0; in acpi_thermal_trips_update()
309 tz->trips.critical.flags.valid = 1; in acpi_thermal_trips_update()
312 tz->trips.critical.temperature)); in acpi_thermal_trips_update()
314 if (tz->trips.critical.flags.valid == 1) { in acpi_thermal_trips_update()
316 tz->trips.critical.flags.valid = 0; in acpi_thermal_trips_update()
322 if (crt_k > tz->trips.critical.temperature) in acpi_thermal_trips_update()
[all …]
|
| /Linux-v4.19/tools/memory-model/ |
| D | lock.cat | 56 * inside a critical section (for the same lock) always deadlock.
74 let critical = ([LKW] ; po-loc ; [UL]) \ (po-loc ; [LKW | UL] ; po-loc)
76 flag ~empty UL \ range(critical) as unmatched-unlock
79 let UNMATCHED-LKW = LKW \ domain(critical)
82 (* rfi for LF events: link each LKW to the LF events in its critical section *)
105 * within one of the lock's critical sections returns False.
133 let co = (co | critical | (critical^-1 ; co))+
|
| /Linux-v4.19/arch/arm/boot/dts/ |
| D | exynos5422-odroidhc1.dts | 47 type = "critical";
96 type = "critical";
134 type = "critical";
172 type = "critical";
|
| /Linux-v4.19/include/net/ |
| D | geneve.h | 48 u8 critical:1; member
54 u8 critical:1;
|
| /Linux-v4.19/arch/powerpc/platforms/pseries/ |
| D | ras.c | 254 int critical; in ras_epow_interrupt() local
260 critical = 1; /* Time Critical */ in ras_epow_interrupt()
262 critical = 0; in ras_epow_interrupt()
270 critical, __pa(&ras_log_buf), in ras_epow_interrupt()
|
| /Linux-v4.19/Documentation/ABI/testing/ |
| D | sysfs-driver-intel-rapid-start | 8 critical level
13 critical level.
|
