1. 20 10月, 2011 1 次提交
  2. 14 10月, 2011 1 次提交
    • J
      hwmon: (w83627ehf) Properly report thermal diode sensors · bf164c58
      Jean Delvare 提交于
      The w83627ehf driver is improperly reporting thermal diode sensors as
      type 2, instead of 3. This caused "sensors" and possibly other
      monitoring tools to report these sensors as "transistor" instead of
      "thermal diode".
      
      Furthermore, diode subtype selection (CPU vs. external) is only
      supported by the original W83627EHF/EHG. All later models only support
      CPU diode type, and some (NCT6776F) don't even have the register in
      question so we should avoid reading from it.
      Signed-off-by: NJean Delvare <khali@linux-fr.org>
      Cc: stable@kernel.org
      Signed-off-by: NGuenter Roeck <guenter.roeck@ericsson.com>
      bf164c58
  3. 15 3月, 2011 11 次提交
  4. 09 1月, 2011 1 次提交
  5. 17 9月, 2010 1 次提交
  6. 15 8月, 2010 2 次提交
  7. 16 12月, 2009 1 次提交
  8. 15 9月, 2009 1 次提交
  9. 16 6月, 2009 1 次提交
  10. 31 3月, 2009 3 次提交
  11. 18 2月, 2009 1 次提交
  12. 07 1月, 2009 2 次提交
  13. 08 2月, 2008 2 次提交
    • J
      hwmon: (w83627ehf) The W83627DHG has 8 VID pins · cbe311f2
      Jean Delvare 提交于
      While the W83627EHF/EHG has only 6 VID pins, the W83627DHG has 8 VID
      pins, to support VRD 11.0. Add support for this.
      Signed-off-by: NJean Delvare <khali@linux-fr.org>
      Signed-off-by: NMark M. Hoffman <mhoffman@lightlink.com>
      cbe311f2
    • J
      hwmon: Let the user override the detected Super-I/O device ID · 67b671bc
      Jean Delvare 提交于
      While it is possible to force SMBus-based hardware monitoring chip
      drivers to drive a not officially supported device, we do not have this
      possibility for Super-I/O-based drivers. That's unfortunate because
      sometimes newer chips are fully compatible and just forcing the driver
      to load would work. Instead of that we have to tell the users to
      recompile the kernel driver, which isn't an easy task for everyone.
      
      So, I propose that we add a module parameter to all Super-I/O based
      hardware monitoring drivers, letting advanced users force the driver
      to load on their machine. The user has to provide the device ID of a
      supposedly compatible device. This requires looking at the source code or
      a datasheet, so I am confident that users can't randomly force a driver
      without knowing what they are doing. Thus this should be relatively safe.
      
      As you can see from the code, the implementation is pretty simple and
      unintrusive.
      Signed-off-by: NJean Delvare <khali@linux-fr.org>
      Acked-by: NHans de Goede <j.w.r.degoede@hhs.nl>
      Signed-off-by: NMark M. Hoffman <mhoffman@lightlink.com>
      67b671bc
  14. 03 1月, 2008 1 次提交
  15. 10 10月, 2007 2 次提交
  16. 13 8月, 2007 2 次提交
  17. 20 7月, 2007 7 次提交