Home
last modified time | relevance | path

Searched full:alarms (Results 1 – 25 of 168) sorted by relevance

1234567

/linux/Documentation/hwmon/
H A Dbt1-pvt.rst27 transistors performance. The driver can optionally provide the hwmon alarms
28 for each sensor the PVT controller supports. The alarms functionality is made
33 these in order to have the hwmon alarms automatically detected the driver code
37 the system performance. So in case if alarms are unnecessary in your system
39 periodically raised to get the data cache/alarms status up to date. By default
56 In case if the alarms kernel config is enabled in the driver the temperature input
73 In case if the alarms config is enabled in the driver the voltage inputs
H A Dw83791d.rst97 specific alarms. You need both the global beep enable bit and the
107 A similar change has occurred for the bitmap corresponding to the alarms. The
108 original legacy method used a single sysfs alarms file containing a bitmap
109 of triggered alarms. The newer method uses multiple sysfs `*_alarm` files
115 responsible for handling the fact that the alarms and beep_mask bitmaps
149 Alarms bitmap vs. beep_mask bitmask
152 For legacy code using the alarms and beep_mask files:
155 Signal Alarms beep_mask Obs
H A Dgl518sm.rst40 sensors, and four voltage sensors. It can report alarms through the
66 alarms work fine, though.
70 beeping for some alarms.
73 is read at least once (except for temperature alarms). This means that the
77 you can easily miss once-only alarms.
H A Dxdpe12284.rst49 and maximum and critical alarms. Critical thresholds and critical alarm are
67 and critical and low critical alarms.
83 The driver provides for power: input and alarms. Power alarm is supported only
95 and maximum and critical alarms.
H A Dxdpe152c4.rst38 and maximum and critical alarms. Low Critical thresholds and Low critical alarm are
62 and critical and low critical alarms.
92 The driver provides for power: input and alarms.
107 and maximum and critical alarms.
H A Dsysfs-interface.rst57 Alarms are direct indications read from the chips. The drivers do NOT
162 Also see the Alarms section for status flags associated with voltages.
193 Also see the Alarms section for status flags associated with fans.
312 Also see the Alarms section for status flags associated with temperatures.
360 Also see the Alarms section for status flags associated with currents.
461 Also see the Alarms section for status flags associated with power readings.
502 Alarms section in Attribute access
508 Usually a given chip will either use channel-related alarms, or
509 limit-related alarms, not both. The driver should just reflect the hardware
563 Old drivers provided a different, non-standard interface to alarms and
[all …]
H A Dlm78.rst43 seven voltage sensors, VID lines, alarms, and some miscellaneous stuff.
49 this case, alarms are issued during all the time when the actual temperature
77 miss once-only alarms.
H A Dmc34vr500.rst21 corresponding alarms. For the temperature, the chip can send interrupts if
27 alarms. The interrupts are mapped as follows:
H A Dlm92.rst43 alarms for high, low, and critical thresholds. There's also an hysteresis to
44 control the thresholds for resetting alarms.
H A Dsis5595.rst76 sensors, four or five voltage sensors, and alarms.
105 In addition to the alarms described above, there is a BTI alarm, which gets
115 once-only alarms.
H A Dasb100.rst29 sensors, four temperature sensors, VID lines and alarms. In addition to
46 Alarms: (TODO question marks indicate may or may not work)
H A Dw83792d.rst72 Alarms are provided as output from "realtime status register". Following bits
107 In addition to the alarms described above, there is a CHAS alarm on the chips
109 to realtime alarms).
/linux/drivers/gpu/drm/nouveau/nvkm/subdev/timer/
H A Dbase.c75 /* Process pending alarms. */ in nvkm_timer_alarm_trigger()
77 list_for_each_entry_safe(alarm, atemp, &tmr->alarms, head) { in nvkm_timer_alarm_trigger()
93 /* Shut down interrupt if no more pending alarms. */ in nvkm_timer_alarm_trigger()
94 if (list_empty(&tmr->alarms)) in nvkm_timer_alarm_trigger()
122 list_for_each_entry(list, &tmr->alarms, head) { in nvkm_timer_alarm()
130 list = list_first_entry(&tmr->alarms, typeof(*list), head); in nvkm_timer_alarm()
195 INIT_LIST_HEAD(&tmr->alarms); in nvkm_timer_new_()
/linux/Documentation/ABI/testing/
H A Drtc-cdev14 for RTCs that support alarms
17 RTCs that support alarms. Can be set upto 24 hours in the
22 powerful interface, which can issue alarms beyond 24 hours and
H A Dsysfs-driver-w1_therm1 What: /sys/bus/w1/devices/.../alarms
5 (RW) read or write TH and TL (Temperature High an Low) alarms.
10 automatically put to TL. Once set, alarms could be search at
/linux/drivers/hwmon/
H A Dadm1026.c281 long alarms; /* Register encoding, combined */ member
324 long value, alarms, gpio; in adm1026_update_device() local
355 /* GPIO16 is MSbit of alarms, move it to gpio */ in adm1026_update_device()
356 alarms = adm1026_read_value(client, ADM1026_REG_STATUS4); in adm1026_update_device()
357 gpio = alarms & 0x80 ? 0x0100 : 0; /* GPIO16 */ in adm1026_update_device()
358 alarms &= 0x7f; in adm1026_update_device()
359 alarms <<= 8; in adm1026_update_device()
360 alarms |= adm1026_read_value(client, ADM1026_REG_STATUS3); in adm1026_update_device()
361 alarms <<= 8; in adm1026_update_device()
362 alarms |= adm1026_read_value(client, ADM1026_REG_STATUS2); in adm1026_update_device()
[all …]
H A Dmax1619.c110 int alarms, ret; in max1619_chip_read() local
121 alarms = get_alarms(regmap); in max1619_chip_read()
122 if (alarms < 0) in max1619_chip_read()
123 return alarms; in max1619_chip_read()
124 *val = alarms; in max1619_chip_read()
H A Dadc128d818.c75 u8 alarms; /* alarm register value */ member
131 data->alarms |= rv; in adc128_update_device()
232 u8 alarms; in adc128_alarm_show() local
241 alarms = data->alarms; in adc128_alarm_show()
242 data->alarms &= ~mask; in adc128_alarm_show()
244 return sprintf(buf, "%u\n", !!(alarms & mask)); in adc128_alarm_show()
H A Dbt1-pvt.c173 * This driver can optionally provide the hwmon alarms for each sensor the PVT
174 * controller supports. The alarms functionality is made compile-time
176 * described further in this comment. So in case if alarms are unnecessary in
178 * IRQs being periodically raised to get the data cache/alarms status up to
185 * threshold value alarms. Alas the wrapper interface hasn't been fully thought
188 * completed. Due to this if alarms need to be implemented for all available
191 * the alarms by itself at each conversion. This also makes pointless to handle
192 * the alarms interrupts, since in occasion they happen synchronously with
195 * driver data cache. This solution is implemented if hwmon alarms are enabled
196 * in this driver. In case if the alarms are disabled, the conversion is
[all …]
H A Dgl518sm.c16 * anyway (changing limits and watching alarms trigger and wear off).
123 u8 alarms; /* Register value */ member
162 data->alarms = gl518_read_value(client, GL518_REG_INT); in gl518_update_device()
197 data->alarms &= data->alarm_mask; in gl518_update_device()
250 show(RAW, alarms, alarms);
442 static DEVICE_ATTR(alarms, 0444, show_alarms, NULL);
453 return sprintf(buf, "%u\n", (data->alarms >> bitnr) & 1); in alarm_show()
/linux/drivers/net/ethernet/sfc/falcon/
H A Dfalcon_boards.c125 u16 alarms; in ef4_check_lm87() local
135 alarms = reg; in ef4_check_lm87()
139 alarms |= reg << 8; in ef4_check_lm87()
140 alarms &= mask; in ef4_check_lm87()
143 if (alarms & LM87_ALARM_TEMP_INT) { in ef4_check_lm87()
150 if (alarms & LM87_ALARM_TEMP_EXT1) { in ef4_check_lm87()
157 elec_fault = alarms & ~(LM87_ALARM_TEMP_INT | LM87_ALARM_TEMP_EXT1); in ef4_check_lm87()
160 if (alarms) in ef4_check_lm87()
165 alarms & 0xff, alarms >> 8, in ef4_check_lm87()
166 (alarms & LM87_ALARM_TEMP_INT) ? in ef4_check_lm87()
[all …]
/linux/tools/testing/selftests/rtc/
H A Drtctest.c232 SKIP(return, "Skipping test since alarms are not supported."); in TEST_F()
248 TH_LOG("skip alarms are not supported."); in TEST_F()
300 SKIP(return, "Skipping test since alarms are not supported."); in TEST_F()
318 TH_LOG("skip alarms are not supported."); in TEST_F()
362 SKIP(return, "Skipping test since alarms are not supported.");
378 TH_LOG("skip alarms are not supported.");
430 SKIP(return, "Skipping test since alarms are not supported.");
448 TH_LOG("skip alarms are not supported.");
/linux/drivers/rtc/
H A Dsysfs.c134 /* Don't show disabled alarms. For uniformity, RTC alarms are in wakealarm_show()
140 * alarms after they trigger, to ensure one-shot semantics. in wakealarm_show()
163 /* Only request alarms that trigger in the future. Disable them in wakealarm_store()
187 /* Avoid accidentally clobbering active alarms; we can't in wakealarm_store()
/linux/drivers/net/wireless/intel/iwlegacy/
H A D4965-calib.c86 /* "false alarms" are signals that our DSP tries to lock onto,
108 * numbers of false alarms within the measured period of actual Rx in il4965_sens_energy_cck()
109 * (Rx is off when we're txing), vs the min/max expected false alarms in il4965_sens_energy_cck()
178 * false alarms. */ in il4965_sens_energy_cck()
183 D_CALIB("consecutive bcns with few false alarms = %u\n", in il4965_sens_energy_cck()
186 /* If we got too many false alarms this time, reduce sensitivity */ in il4965_sens_energy_cck()
204 * healthy number or too many false alarms */ in il4965_sens_energy_cck()
213 * 1a) previous beacon did *not* have *too many* false alarms in il4965_sens_energy_cck()
217 * false alarms */ in il4965_sens_energy_cck()
230 /* Else we got a healthy number of false alarms, keep status quo */ in il4965_sens_energy_cck()
[all …]
/linux/drivers/net/wireless/intel/iwlwifi/dvm/
H A Dcalib.c101 /* "false alarms" are signals that our DSP tries to lock onto,
124 * numbers of false alarms within the measured period of actual Rx in iwl_sens_energy_cck()
125 * (Rx is off when we're txing), vs the min/max expected false alarms in iwl_sens_energy_cck()
195 * false alarms. */ in iwl_sens_energy_cck()
200 IWL_DEBUG_CALIB(priv, "consecutive bcns with few false alarms = %u\n", in iwl_sens_energy_cck()
203 /* If we got too many false alarms this time, reduce sensitivity */ in iwl_sens_energy_cck()
221 * healthy number or too many false alarms */ in iwl_sens_energy_cck()
230 * 1a) previous beacon did *not* have *too many* false alarms in iwl_sens_energy_cck()
234 * false alarms */ in iwl_sens_energy_cck()
247 /* Else we got a healthy number of false alarms, keep status quo */ in iwl_sens_energy_cck()
[all …]

1234567