| /linux/drivers/gpu/drm/nouveau/nvkm/subdev/timer/ |
| H A D | base.c | 75 /* 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/hwmon/ |
| H A D | gl518sm.rst | 40 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 D | w83791d.rst | 97 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 D | xdpe12284.rst | 49 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 D | xdpe152c4.rst | 38 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 D | lm78.rst | 43 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 D | mc34vr500.rst | 21 corresponding alarms. For the temperature, the chip can send interrupts if
27 alarms. The interrupts are mapped as follows:
|
| H A D | lm92.rst | 43 alarms for high, low, and critical thresholds. There's also an hysteresis to
44 control the thresholds for resetting alarms.
|
| H A D | sis5595.rst | 76 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 D | asb100.rst | 29 sensors, four temperature sensors, VID lines and alarms. In addition to
46 Alarms: (TODO question marks indicate may or may not work)
|
| H A D | lm80.rst | 41 seven voltage sensors, alarms, and some miscellaneous stuff.
71 miss once-only alarms.
|
| H A D | w83792d.rst | 72 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).
|
| H A D | lm87.rst | 39 rotation speed sensors, up to seven voltage sensors, alarms, and some
64 miss once-only alarms.
|
| H A D | via686a.rst | 46 sensors, five voltage sensors and alarms.
69 miss once-only alarms.
|
| /linux/tools/testing/selftests/rtc/ |
| H A D | rtctest.c | 237 SKIP(return, "Skipping test since alarms are not supported."); in TEST_F()
239 SKIP(return, "Skipping test since alarms has only minute granularity."); in TEST_F()
255 TH_LOG("skip alarms are not supported."); in TEST_F()
307 SKIP(return, "Skipping test since alarms are not supported."); in TEST_F()
309 SKIP(return, "Skipping test since alarms has only minute granularity."); in TEST_F()
327 TH_LOG("skip alarms are not supported."); in TEST_F()
371 SKIP(return, "Skipping test since alarms are not supported.");
387 TH_LOG("skip alarms are not supported.");
439 SKIP(return, "Skipping test since alarms are not supported.");
457 TH_LOG("skip alarms are not supported.");
|
| /linux/Documentation/ABI/testing/ |
| H A D | rtc-cdev | 14 for RTCs that support alarms
17 RTCs that support alarms. Can be set up to 24 hours in the
22 powerful interface, which can issue alarms beyond 24 hours and
|
| H A D | sysfs-driver-w1_therm | 1 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/net/ethernet/sfc/falcon/ |
| H A D | falcon_boards.c | 125 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/drivers/rtc/ |
| H A D | sysfs.c | 129 /* Don't show disabled alarms. For uniformity, RTC alarms are in wakealarm_show()
135 * alarms after they trigger, to ensure one-shot semantics. in wakealarm_show()
159 /* Only request alarms that trigger in the future. Disable them in wakealarm_store()
183 /* Avoid accidentally clobbering active alarms; we can't in wakealarm_store()
|
| H A D | rtc-cmos.c | 298 /* Basic alarms only support hour, minute, and seconds fields. in cmos_read_alarm()
299 * Some also support day and month, for alarms up to a year in in cmos_read_alarm()
423 "Alarms can be up to one day in the future\n"); in cmos_validate_alarm()
447 "Alarms can be up to one month in the future\n"); in cmos_validate_alarm()
466 "Alarms can be up to one year in the future\n"); in cmos_validate_alarm()
728 /* All Linux RTC alarms should be treated as if they were oneshot. in cmos_interrupt()
1131 cmos_no_alarm(&cmos_rtc) ? "no alarms" : in cmos_do_probe()
1132 cmos_rtc.mon_alrm ? "alarms up to one year" : in cmos_do_probe()
1133 cmos_rtc.day_alrm ? "alarms up to one month" : in cmos_do_probe()
1134 "alarms up to one day", in cmos_do_probe()
[all …]
|
| /linux/drivers/net/wireless/intel/iwlegacy/ |
| H A D | 4965-calib.c | 86 /* "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 D | calib.c | 101 /* "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 …]
|
| /linux/Documentation/w1/slaves/ |
| H A D | w1_therm.rst | 93 Sysfs ``alarms`` allow read or write TH and TL (Temperature High an Low) alarms.
96 the device. Lowest value is automatically put to TL. Once set, alarms could
|
| /linux/drivers/hwmon/ |
| H A D | lm90.c | 216 #define LM90_HAVE_ALARMS BIT(13) /* Create 'alarms' attribute */
767 u16 reported_alarms; /* alarms reported as sysfs/udev events */
768 u16 current_alarms; /* current alarms, reported by chip */
769 u16 alarms; /* alarms not yet reported to user */ member
1166 u16 alarms; in lm90_update_alarms_locked() local
1174 alarms = val & ~LM90_STATUS_BUSY; in lm90_update_alarms_locked()
1180 alarms |= val << 8; in lm90_update_alarms_locked()
1184 * handler) and alarm data is valid, the alarms may have been in lm90_update_alarms_locked()
1186 * register may still be cleared. Only add additional alarms in lm90_update_alarms_locked()
1187 * in this case. Alarms will be cleared later if appropriate. in lm90_update_alarms_locked()
[all …]
|
| H A D | ltc2947-core.c | 275 char alarms[LTC2947_ALERTS_SIZE + 1]; in ltc2947_alarm_read() local
278 memset(alarms, 0, sizeof(alarms)); in ltc2947_alarm_read()
290 ret = regmap_bulk_read(st->map, LTC2947_REG_STATUS, alarms, in ltc2947_alarm_read()
291 sizeof(alarms)); in ltc2947_alarm_read()
296 *val = !!(alarms[offset] & mask); in ltc2947_alarm_read()
|