Home
last modified time | relevance | path

Searched hist:fb4504fe84b09cbf49fda19e6630a1003d79656a (Results 1 – 3 of 3) sorted by relevance

/openbmc/linux/drivers/hwmon/
H A Dpcf8591.cfb4504fe84b09cbf49fda19e6630a1003d79656a Mon Mar 30 14:46:43 CDT 2009 Jean Delvare <khali@linux-fr.org> Move the pcf8591 driver to hwmon

Directory drivers/i2c/chips is going away, so drivers there must find
new homes. For the pcf8591 driver, the best choice seems to be the
hwmon subsystem. While the Philips PCF8591 device isn't a typical
hardware monitoring chip, its DAC interface is compatible with the
hwmon one, so it fits somewhat.

If a better subsystem is ever created for ADC/DAC chips, the driver
could be moved there.

Signed-off-by: Jean Delvare <khali@linux-fr.org>
Cc: Aurelien Jarno <aurelien@aurel32.net>
H A DMakefilediff fb4504fe84b09cbf49fda19e6630a1003d79656a Mon Mar 30 14:46:43 CDT 2009 Jean Delvare <khali@linux-fr.org> Move the pcf8591 driver to hwmon

Directory drivers/i2c/chips is going away, so drivers there must find
new homes. For the pcf8591 driver, the best choice seems to be the
hwmon subsystem. While the Philips PCF8591 device isn't a typical
hardware monitoring chip, its DAC interface is compatible with the
hwmon one, so it fits somewhat.

If a better subsystem is ever created for ADC/DAC chips, the driver
could be moved there.

Signed-off-by: Jean Delvare <khali@linux-fr.org>
Cc: Aurelien Jarno <aurelien@aurel32.net>
H A DKconfigdiff fb4504fe84b09cbf49fda19e6630a1003d79656a Mon Mar 30 14:46:43 CDT 2009 Jean Delvare <khali@linux-fr.org> Move the pcf8591 driver to hwmon

Directory drivers/i2c/chips is going away, so drivers there must find
new homes. For the pcf8591 driver, the best choice seems to be the
hwmon subsystem. While the Philips PCF8591 device isn't a typical
hardware monitoring chip, its DAC interface is compatible with the
hwmon one, so it fits somewhat.

If a better subsystem is ever created for ADC/DAC chips, the driver
could be moved there.

Signed-off-by: Jean Delvare <khali@linux-fr.org>
Cc: Aurelien Jarno <aurelien@aurel32.net>