diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2015-06-18 23:02:27 -0400 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2015-06-18 23:02:27 -0400 |
commit | e640a280ccb9c448a3d9d522ea730ce00efa8cf0 (patch) | |
tree | 331237e268c9f06eb56c6edb7858760ac7344f6c | |
parent | 5ca62d65030d8295f54c490d2072563545dbd9d9 (diff) | |
parent | 8366610283d08564f65a1af2ec8458df08418727 (diff) |
Merge branch 'i2c/for-current' of git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux
Pull i2c documentation fix from Wolfram Sang:
"Here is a small documentation fix for I2C.
We already had a user who unsuccessfully tried to get the new slave
framework running with the currently broken example. So, before this
happens again, I'd like to have this how-to-use section fixed for 4.1
already. So that no more hacking time is wasted"
* 'i2c/for-current' of git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux:
i2c: slave: fix the example how to instantiate from userspace
-rw-r--r-- | Documentation/i2c/slave-interface | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/i2c/slave-interface b/Documentation/i2c/slave-interface index 389bb5d61854..b228ca54bcf4 100644 --- a/Documentation/i2c/slave-interface +++ b/Documentation/i2c/slave-interface | |||
@@ -31,10 +31,10 @@ User manual | |||
31 | =========== | 31 | =========== |
32 | 32 | ||
33 | I2C slave backends behave like standard I2C clients. So, you can instantiate | 33 | I2C slave backends behave like standard I2C clients. So, you can instantiate |
34 | them like described in the document 'instantiating-devices'. A quick example | 34 | them as described in the document 'instantiating-devices'. A quick example for |
35 | for instantiating the slave-eeprom driver from userspace: | 35 | instantiating the slave-eeprom driver from userspace at address 0x64 on bus 1: |
36 | 36 | ||
37 | # echo 0-0064 > /sys/bus/i2c/drivers/i2c-slave-eeprom/bind | 37 | # echo slave-24c02 0x64 > /sys/bus/i2c/devices/i2c-1/new_device |
38 | 38 | ||
39 | Each backend should come with separate documentation to describe its specific | 39 | Each backend should come with separate documentation to describe its specific |
40 | behaviour and setup. | 40 | behaviour and setup. |