1. 28 5月, 2010 4 次提交
  2. 25 5月, 2010 1 次提交
  3. 30 3月, 2010 1 次提交
  4. 06 3月, 2010 5 次提交
  5. 12 1月, 2010 1 次提交
  6. 11 1月, 2010 1 次提交
  7. 18 12月, 2009 1 次提交
  8. 17 12月, 2009 2 次提交
  9. 16 12月, 2009 1 次提交
  10. 10 12月, 2009 8 次提交
  11. 10 10月, 2009 1 次提交
  12. 24 9月, 2009 2 次提交
  13. 17 9月, 2009 2 次提交
  14. 15 9月, 2009 2 次提交
  15. 18 7月, 2009 1 次提交
  16. 17 6月, 2009 1 次提交
  17. 16 6月, 2009 3 次提交
  18. 14 4月, 2009 1 次提交
    • J
      hwmon: sht15 humidity sensor driver · 251eb40f
      Jonathan Cameron 提交于
      Data sheet at:
      http://www.sensirion.ch/en/pdf/product_information/Datasheet-humidity-sensor-SHT1x.pdf
      
      These sensors communicate over a 2 wire bus running a device specific
      protocol.  The complexity of the driver is mainly due to handling the
      substantial delays between requesting a reading and the device pulling the
      data line low to indicate that the data is available.  This is handled by
      an interrupt that is disabled under all other conditions.
      
      I wasn't terribly clear on the best way to handle this, so comments on
      that aspect would be particularly welcome!
      
      Interpretation of the temperature depends on knowing the supply voltage.
      If configured in a board config as a regulator consumer this is obtained
      from the regulator subsystem.  If not it should be provided in the
      platform data.
      
      I've placed this driver in the hwmon subsystem as it is definitely a
      device that may be used for hardware monitoring and with it's relatively
      slow response times (up to 120 millisecs to get a reading) a caching
      strategy certainly seems to make sense!
      Signed-off-by: NJonathan Cameron <jic23@cam.ac.uk>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      251eb40f
  19. 07 4月, 2009 2 次提交