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>
This commit is contained in:
parent
38fa8afff0
commit
b4cdaf32ce
1 changed files with 3 additions and 3 deletions
|
@ -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
|
* implement calls to register/unregister the slave and add those to the
|
||||||
struct i2c_algorithm. When registering, you probably need to set the i2c
|
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
|
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
|
should use pm_runtime_get_sync() because your device usually needs to be
|
||||||
on always to be able to detect its slave address. When unregistering, do the
|
powered on always to be able to detect its slave address. When unregistering,
|
||||||
inverse of the above.
|
do the inverse of the above.
|
||||||
|
|
||||||
* Catch the slave interrupts and send appropriate i2c_slave_events to the backend.
|
* Catch the slave interrupts and send appropriate i2c_slave_events to the backend.
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue