| /kernel/linux/linux-6.6/Documentation/hwmon/ |
| D | bt1-pvt.rst | 27 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
|
| 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.
|
| 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
|
| 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.
|
| 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.
|
| D | sysfs-interface.rst | 57 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 …]
|
| 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.
|
| D | mc34vr500.rst | 21 corresponding alarms. For the temperature, the chip can send interrupts if
27 alarms. The interrupts are mapped as follows:
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/nouveau/nvkm/subdev/timer/ |
| 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_()
|
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| D | bt1-pvt.rst | 27 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
|
| 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.
|
| 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
|
| D | xdpe12284.rst | 45 and maximum and critical alarms. Critical thresholds and critical alarm are
63 and critical and low critical alarms.
79 The driver provides for power: input and alarms. Power alarm is supported only
91 and maximum and critical alarms.
|
| 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.
|
| D | sysfs-interface.rst | 57 Alarms are direct indications read from the chips. The drivers do NOT
258 Also see the Alarms section for status flags associated with voltages.
345 Also see the Alarms section for status flags associated with fans.
614 Also see the Alarms section for status flags associated with temperatures.
709 Also see the Alarms section for status flags associated with currents.
889 Also see the Alarms section for status flags associated with power readings.
951 Alarms chapter
957 Usually a given chip will either use channel-related alarms, or
958 limit-related alarms, not both. The driver should just reflect the hardware
1027 Old drivers provided a different, non-standard interface to alarms and
[all …]
|
| D | lm92.rst | 43 alarms for high, low, and critical thresholds. There's also an hysteresis to
44 control the thresholds for resetting alarms.
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/nouveau/nvkm/subdev/timer/ |
| 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_()
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | rtc-cdev | 14 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
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | rtc-cdev | 14 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
|
| /kernel/linux/linux-6.6/drivers/hwmon/ |
| D | max1619.c | 87 u8 alarms; member
119 data->alarms = i2c_smbus_read_byte_data(client, in max1619_update_device()
124 data->alarms ^= 0x02; in max1619_update_device()
172 return sprintf(buf, "%d\n", data->alarms); in alarms_show()
180 return sprintf(buf, "%d\n", (data->alarms >> bitnr) & 1); in alarm_show()
190 static DEVICE_ATTR_RO(alarms);
|
| D | adm1026.c | 281 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 …]
|
| /kernel/linux/linux-5.10/drivers/hwmon/ |
| D | max1619.c | 87 u8 alarms; member
119 data->alarms = i2c_smbus_read_byte_data(client, in max1619_update_device()
124 data->alarms ^= 0x02; in max1619_update_device()
172 return sprintf(buf, "%d\n", data->alarms); in alarms_show()
180 return sprintf(buf, "%d\n", (data->alarms >> bitnr) & 1); in alarm_show()
190 static DEVICE_ATTR_RO(alarms);
|
| D | adm1026.c | 281 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 …]
|
| /kernel/linux/linux-6.6/drivers/net/ethernet/sfc/falcon/ |
| 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 …]
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/sfc/falcon/ |
| 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 …]
|