summaryrefslogtreecommitdiffstats
path: root/drivers/staging
diff options
context:
space:
mode:
authorJean Delvare <khali@linux-fr.org>2013-05-04 14:49:36 +0200
committerJean Delvare <khali@endymion.delvare>2013-05-04 14:49:36 +0200
commit0cd2c72d765191f24d7be14366c0413bf139f3e3 (patch)
tree77d19cabe37cd11b6c5c5f14e8e5dc05da81802f /drivers/staging
parent87d0621ae2bdf2e2c60aadbbcb8b6c680777c1bf (diff)
downloadop-kernel-dev-0cd2c72d765191f24d7be14366c0413bf139f3e3.zip
op-kernel-dev-0cd2c72d765191f24d7be14366c0413bf139f3e3.tar.gz
hwmon: (lm75) Tune resolution and sample time per chip
Most LM75-compatible chips can either sample much faster or with a much better resolution than the original LM75 chip. So far the lm75 driver did not let the user take benefit of these improvements. Do it now. I decided to almost always configure the chip to use the best resolution possible, which also means the longest sample time. The only chips for which I didn't are the DS75, DS1775 and STDS75, because they are really too slow in 12-bit mode (1.2 to 1.5 second worst case) so I went for 11-bit mode as a more reasonable tradeoff. This choice is dictated by the fact that the hwmon subsystem is meant for system monitoring, it has never been supposed to be ultra-fast, and as a matter of fact we do cache the sampled values in almost all drivers. If anyone isn't pleased with these default settings, they can always introduce a platform data structure or DT support for the lm75. That being said, it seems nobody ever complained that the driver wouldn't refresh the value faster than every 1.5 second, and the change made it faster for all chips even in 12-bit mode, so I don't expect any complaint. Signed-off-by: Jean Delvare <khali@linux-fr.org> Acked-by: Guenter Roeck <linux@roeck-us.net>
Diffstat (limited to 'drivers/staging')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud