summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorbgardner@wabtec.com <bgardner@wabtec.com>2005-07-27 21:43:21 +0400
committerGreg Kroah-Hartman <gregkh@suse.de>2005-09-05 20:14:05 +0400
commit0283fe6c3bdbe9ca9aefa28b24883ec1dee3ccbd (patch)
treedf4e86f58dc1708606ad09d8aea7a872d7d1a8fe
parenta61fc683ae1b7871d8d81ac5025af1a923731547 (diff)
downloadlinux-0283fe6c3bdbe9ca9aefa28b24883ec1dee3ccbd.tar.xz
[PATCH] I2C: max6875 documentation cleanup
Fix a spelling error and change a sysfs name. Signed-off-by: Ben Gardner <bgardner@wabtec.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
-rw-r--r--Documentation/i2c/chips/max68754
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/i2c/chips/max6875 b/Documentation/i2c/chips/max6875
index 46b8dc34c971..96fec562a8e9 100644
--- a/Documentation/i2c/chips/max6875
+++ b/Documentation/i2c/chips/max6875
@@ -49,14 +49,14 @@ $ modprobe max6875 force=0,0x50
The MAX6874/MAX6875 ignores address bit 0, so this driver attaches to multiple
addresses. For example, for address 0x50, it also reserves 0x51.
-The even-address instance is called 'max6875', the odd one is 'max6875-dummy'.
+The even-address instance is called 'max6875', the odd one is 'max6875 subclient'.
Programming the chip using i2c-dev
----------------------------------
Use the i2c-dev interface to access and program the chips.
-Reads and write are performed differently depending on the address range.
+Reads and writes are performed differently depending on the address range.
The configuration registers are at addresses 0x00 - 0x45.
Use i2c_smbus_write_byte_data() to write a register and