diff options
| author | Jean Delvare <khali@linux-fr.org> | 2009-10-04 22:53:41 +0200 |
|---|---|---|
| committer | Jean Delvare <khali@linux-fr.org> | 2009-10-04 22:53:41 +0200 |
| commit | b835d7fbd54c42d7b9abb5e8a64f32690ebfad43 (patch) | |
| tree | e5ce6f25bef922df78da1116baf50916f122ce19 /Documentation | |
| parent | f546c65cd59275c7b95eba4f9b3ab83b38a5e9cb (diff) | |
| download | op-kernel-dev-b835d7fbd54c42d7b9abb5e8a64f32690ebfad43.zip op-kernel-dev-b835d7fbd54c42d7b9abb5e8a64f32690ebfad43.tar.gz | |
max6875: Discard obsolete detect method
There is no point in implementing a detect callback for the MAX6875, as
this device can't be detected. It was there solely to handle "force"
module parameters to instantiate devices, but now we have a better sysfs
interface that can do the same.
So we can get rid of the ugly module parameters and the detect callback.
This basically divides the binary module size by 2.
Signed-off-by: Jean Delvare <khali@linux-fr.org>
Acked-by: Wolfram Sang <w.sang@pengutronix.de>
Acked-by: Ben Gardner <gardner.ben@gmail.com>
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/misc-devices/max6875 | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/Documentation/misc-devices/max6875 b/Documentation/misc-devices/max6875 index 10ca43c..1e89ee3 100644 --- a/Documentation/misc-devices/max6875 +++ b/Documentation/misc-devices/max6875 @@ -42,10 +42,12 @@ General Remarks Valid addresses for the MAX6875 are 0x50 and 0x52. Valid addresses for the MAX6874 are 0x50, 0x52, 0x54 and 0x56. -The driver does not probe any address, so you must force the address. +The driver does not probe any address, so you explicitly instantiate the +devices. Example: -$ modprobe max6875 force=0,0x50 +$ modprobe max6875 +$ echo max6875 0x50 > /sys/bus/i2c/devices/i2c-0/new_device The MAX6874/MAX6875 ignores address bit 0, so this driver attaches to multiple addresses. For example, for address 0x50, it also reserves 0x51. |
