| Message ID | 20240814182210.15382-2-wsa+renesas@sang-engineering.com (mailing list archive) |
|---|---|
| State | Handled Elsewhere |
| Delegated to: | Geert Uytterhoeven |
| Headers | show |
| Series | i2c: testunit: let it trigger SMBusAlerts | expand |
On Wed, Aug 14, 2024 at 08:22:07PM +0200, Wolfram Sang wrote: > The testunit can also be instantiated via firmware nodes. Give a > devicetree node as an example. > > Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com> Applied to for-next, thanks!
diff --git a/Documentation/i2c/slave-testunit-backend.rst b/Documentation/i2c/slave-testunit-backend.rst index d3ab5944877d..3743188ecfc7 100644 --- a/Documentation/i2c/slave-testunit-backend.rst +++ b/Documentation/i2c/slave-testunit-backend.rst @@ -20,6 +20,18 @@ Instantiating the device is regular. Example for bus 0, address 0x30:: # echo "slave-testunit 0x1030" > /sys/bus/i2c/devices/i2c-0/new_device +Or using firmware nodes. Here is a devicetree example (note this is only a +debug device, so there are no official DT bindings):: + + &i2c0 { + ... + + testunit@30 { + compatible = "slave-testunit"; + reg = <(0x30 | I2C_OWN_SLAVE_ADDRESS)>; + }; + }; + After that, you will have the device listening. Reading will return a single byte. Its value is 0 if the testunit is idle, otherwise the command number of the currently running command.
The testunit can also be instantiated via firmware nodes. Give a devicetree node as an example. Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com> --- Documentation/i2c/slave-testunit-backend.rst | 12 ++++++++++++ 1 file changed, 12 insertions(+)