1. 06 3月, 2010 16 次提交
  2. 06 2月, 2010 3 次提交
    • J
      hwmon: (w83781d) Request I/O ports individually for probing · b0bcdd3c
      Jean Delvare 提交于
      Different motherboards have different PNP declarations for
      W83781D/W83782D chips. Some declare the whole range of I/O ports (8
      ports), some declare only the useful ports (2 ports at offset 5) and
      some declare fancy ranges, for example 4 ports at offset 4. To
      properly handle all cases, request all ports individually for probing.
      After we have determined that we really have a W83781D or W83782D
      chip, the useful port range will be requested again, as a single
      block.
      
      I did not see a board which needs this yet, but I know of one for lm78
      driver and I'd like to keep the logic of these two drivers in sync.
      Signed-off-by: NJean Delvare <khali@linux-fr.org>
      Cc: stable@kernel.org
      b0bcdd3c
    • J
      hwmon: (lm78) Request I/O ports individually for probing · 197027e6
      Jean Delvare 提交于
      Different motherboards have different PNP declarations for LM78/LM79
      chips. Some declare the whole range of I/O ports (8 ports), some
      declare only the useful ports (2 ports at offset 5) and some declare
      fancy ranges, for example 4 ports at offset 4. To properly handle all
      cases, request all ports individually for probing. After we have
      determined that we really have an LM78 or LM79 chip, the useful port
      range will be requested again, as a single block.
      
      This fixes the driver on the Olivetti M3000 DT 540, at least.
      Signed-off-by: NJean Delvare <khali@linux-fr.org>
      Cc: stable@kernel.org
      197027e6
    • R
      hwmon: (adt7462) Wrong ADT7462_VOLT_COUNT · 85f8d3e5
      Ray Copeland 提交于
      The #define ADT7462_VOLT_COUNT is wrong, it should be 13 not 12. All the 
      for loops that use this as a limit count are of the typical form, "for 
      (n = 0; n < ADT7462_VOLT_COUNT; n++)", so to loop through all voltages 
      w/o missing the last one it is necessary for the count to be one greater 
      than it is.  (Specifically, you will miss the +1.5V 3GPIO input with count 
      = 12 vs. 13.)
      Signed-off-by: NRay Copeland <ray.copeland@aprius.com>
      Acked-by: N"Darrick J. Wong" <djwong@us.ibm.com>
      Signed-off-by: NJean Delvare <khali@linux-fr.org>
      Cc: stable@kernel.org
      85f8d3e5
  3. 03 2月, 2010 1 次提交
  4. 25 1月, 2010 4 次提交
  5. 12 1月, 2010 1 次提交
  6. 11 1月, 2010 6 次提交
  7. 18 12月, 2009 1 次提交
  8. 17 12月, 2009 7 次提交
  9. 16 12月, 2009 1 次提交
    • S
      lis3: scale output values to mg · 32496c76
      Samu Onkalo 提交于
      Report output values as 1/1000 of earth gravity.
      
      Output values from lis3 can be read from sysfs position entry and from
      input device.  Input device can be accessed as event device and as
      joystick device.  Joystick device can be in two modes.  Meaning of the
      output values varies from case to case depending on the chip type and
      configuration (scale).  Only joystick interface in JS_CORR_BROKEN mode
      returned somehow similar output values in different configurations.
      Joystick device is in that state by default in case of lis3.
      
      Position sysfs entry, input event device and raw joystick device have been
      little bit broken since meaning of the output values has been varied
      between 12 and 8 bit devices.  Applications which relayed on those methods
      failed if the chip is different than the expected one.
      
      This patch converts output values to mean similar thing in different
      configurations.  Both 8 and 12 bit devices reports now same acceleration
      values.  If somebody implements full scale support to the driver, output
      values will still mean the same.  Scaling factor and input device range
      must be updated in that case.
      
      Joystick interface in JS_CORR_BROKEN mode is not touched by this patch.
      All other interfaces have different scale after this change.  For 12 bit
      device scaling factor is 0.977 which keeps scaled and unscaled values are
      quite close to each others.  For 8 bit device, scaled values are 18 times
      bigger than unscaled values.
      Signed-off-by: NSamu Onkalo <samu.p.onkalo@nokia.com>
      Acked-by: NÉric Piel <Eric.Piel@tremplin-utc.net>
      Cc: Pavel Machek <pavel@ucw.cz>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      32496c76