summaryrefslogtreecommitdiff
path: root/Documentation/i2c
diff options
context:
space:
mode:
authorWolfram Sang <wsa@the-dreams.de>2016-08-25 20:27:40 +0300
committerWolfram Sang <wsa@the-dreams.de>2016-09-08 17:57:14 +0300
commit30851a7c2155d0b321485e66386ea99191d8b3f5 (patch)
treec4d9cd960ee59266338b7b3f645151c2287d2314 /Documentation/i2c
parente35478eac030990e23a56bf11dc074c5a069124a (diff)
downloadlinux-30851a7c2155d0b321485e66386ea99191d8b3f5.tar.xz
Documentation: i2c: slave-interface: add note for driver development
Make it clear that adding slave support shall not disable master functionality. We can have both, so we should. Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
Diffstat (limited to 'Documentation/i2c')
-rw-r--r--Documentation/i2c/slave-interface5
1 files changed, 5 insertions, 0 deletions
diff --git a/Documentation/i2c/slave-interface b/Documentation/i2c/slave-interface
index 80807adb8ded..7e2a228f21bc 100644
--- a/Documentation/i2c/slave-interface
+++ b/Documentation/i2c/slave-interface
@@ -145,6 +145,11 @@ If you want to add slave support to the bus driver:
* Catch the slave interrupts and send appropriate i2c_slave_events to the backend.
+Note that most hardware supports being master _and_ slave on the same bus. So,
+if you extend a bus driver, please make sure that the driver supports that as
+well. In almost all cases, slave support does not need to disable the master
+functionality.
+
Check the i2c-rcar driver as an example.