Searched refs:w83781d (Results 1 – 7 of 7) sorted by relevance
62 enum chips { w83781d, w83782d, w83783s, as99127f }; enumerator199 ((type == w83781d || type == as99127f) ? 8 : 128)) >> 1; in DIV_TO_REG()474 int bitnr = (data->type == w83781d) ? 5 : 13; in show_temp3_alarm()521 if (data->type != w83781d && data->type != as99127f) { in beep_mask_store()595 int bitnr = (data->type == w83781d) ? 5 : 13; in show_temp3_beep()679 if (data->type != w83781d && data->type != as99127f) { in store_fan_div()1045 if (kind != as99127f && kind != w83781d && kind != w83783s) { in w83781d_create_files()1055 if (kind != w83781d) { in w83781d_create_files()1064 if (kind != w83781d && kind != as99127f) { in w83781d_create_files()1075 if (kind != as99127f && kind != w83781d) { in w83781d_create_files()[all …]
21 obj-$(CONFIG_SENSORS_W83781D) += w83781d.o
1775 will be called w83781d.
49 initialization that were required in the w83781d driver.52 use the w83781d driver. However this is not the preferred method64 For further information on this driver see the w83781d driver documentation.
1 Kernel driver w83781d6 Prefix: 'w83781d'8 Datasheet: http://www.winbond-usa.com/products/winbond_products/pdfs/PCIC/w83781d.pdf60 w83781d 7 3 0 3 0x10-1 0x5ca3 yes yes157 In most cases it is treated as a w83781d (although revision 2 of the396 long as we don't know more, the w83781d driver doesn't handle PWM on
62 I.e. it behaves the same as w83781d.
12 This driver was derived from the w83781d.c and w83792d.c source files.15 w83781d.c:
