| commit | 764c16918fb2347b3cbc8f6030b2b6561911bc32 | |
| author | Jean Delvare <khali@linux-fr.org> | |
| Sat, 28 Mar 2009 20:34:40 +0000 (28 21:34 +0100) | ||
| committer | Jean Delvare <khali@linux-fr.org> | |
| Sat, 28 Mar 2009 20:34:40 +0000 (28 21:34 +0100) | ||
| tree | 0420f4263f89f5a5658af473c39168189a02b300 | treesnapshot (tar.gz zip) |
| parent | 5d80f8e5a9dc9c9a94d4aeaa567e219a808b8a4a | commitdiff |
i2c: Document the different ways to instantiate i2c devices
On popular demand, here comes some documentation about how to
instantiate i2c devices in the new (standard) i2c device driver
binding model.
I have also clarified how the class bitfield lets driver authors
control which buses are probed in the auto-detect case, and warned
more loudly against the abuse of this method.
Signed-off-by: Jean Delvare <khali@linux-fr.org>
Acked-by: Michael Lawnick <nospam_lawnick@gmx.de>
Acked-by: Hans Verkuil <hverkuil@xs4all.nl>
On popular demand, here comes some documentation about how to
instantiate i2c devices in the new (standard) i2c device driver
binding model.
I have also clarified how the class bitfield lets driver authors
control which buses are probed in the auto-detect case, and warned
more loudly against the abuse of this method.
Signed-off-by: Jean Delvare <khali@linux-fr.org>
Acked-by: Michael Lawnick <nospam_lawnick@gmx.de>
Acked-by: Hans Verkuil <hverkuil@xs4all.nl>
| Documentation/i2c/instantiating-devices | [new file with mode: 0644] | blob |
| Documentation/i2c/writing-clients | diffblobblamehistory |