diff options
| author | Wolfram Sang <wsa@the-dreams.de> | 2016-07-23 22:04:20 +0200 |
|---|---|---|
| committer | Wolfram Sang <wsa@the-dreams.de> | 2016-07-23 22:04:20 +0200 |
| commit | b4cdaf32ce04366ec143c2255492918c35f58691 (patch) | |
| tree | ffff0161de80ee92d411e9d72d3179637ead0e53 | |
| parent | 38fa8afff0a99fe8caabbde0d590df3067cf695a (diff) | |
| download | linux-b4cdaf32ce04366ec143c2255492918c35f58691.tar.bz2 | |
Documentation: i2c: slave: give proper example for pm usage
pm_runtime_forbid was the wrong knob, this is the better one.
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
| -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 abd10186a9e9..80807adb8ded 100644 --- a/Documentation/i2c/slave-interface +++ b/Documentation/i2c/slave-interface @@ -139,9 +139,9 @@ If you want to add slave support to the bus driver: * implement calls to register/unregister the slave and add those to the struct i2c_algorithm. When registering, you probably need to set the i2c slave address and enable slave specific interrupts. If you use runtime pm, you - should use pm_runtime_forbid() because your device usually needs to be powered - on always to be able to detect its slave address. When unregistering, do the - inverse of the above. + should use pm_runtime_get_sync() because your device usually needs to be + powered on always to be able to detect its slave address. When unregistering, + do the inverse of the above. * Catch the slave interrupts and send appropriate i2c_slave_events to the backend. |