diff options
author | Robert Shearman <robert.shearman@att.com> | 2019-02-28 14:43:43 +0300 |
---|---|---|
committer | Peter Rosin <peda@axentia.se> | 2019-04-22 00:44:37 +0300 |
commit | f1fb64b04bf414ab04e31ac107bb28137105c5fd (patch) | |
tree | 6557ff556070c3185c10de61e2e58118ca8e014d /Documentation/ABI/testing/sysfs-bus-i2c-devices-pca954x | |
parent | 590085f0f25a169772180f57f56deb92b18ea302 (diff) | |
download | linux-f1fb64b04bf414ab04e31ac107bb28137105c5fd.tar.xz |
i2c: mux: pca954x: allow management of device idle state via sysfs
The behaviour, by default, to not deselect after each transfer is
unsafe when there is a device with an address that conflicts with
another device on another mux on the same parent bus, and it
may not be convenient to use devicetree to set the deselect mux,
e.g. when running on x86_64 when ACPI is used to discover most of the
device hierarchy.
Therefore, provide the ability to set the idle state behaviour using a
new sysfs file, idle_state as a complement to the method of
instantiating the device via sysfs. The possible behaviours are
disconnect, i.e. to deselect all channels from the mux, as-is (the
default), i.e. leave the last channel selected, and set a
predetermined channel.
The current behaviour of leaving the channel as-is after each
transaction is preserved.
Signed-off-by: Robert Shearman <robert.shearman@att.com>
Signed-off-by: Peter Rosin <peda@axentia.se>
Diffstat (limited to 'Documentation/ABI/testing/sysfs-bus-i2c-devices-pca954x')
-rw-r--r-- | Documentation/ABI/testing/sysfs-bus-i2c-devices-pca954x | 20 |
1 files changed, 20 insertions, 0 deletions
diff --git a/Documentation/ABI/testing/sysfs-bus-i2c-devices-pca954x b/Documentation/ABI/testing/sysfs-bus-i2c-devices-pca954x new file mode 100644 index 000000000000..0b0de8cd0d13 --- /dev/null +++ b/Documentation/ABI/testing/sysfs-bus-i2c-devices-pca954x @@ -0,0 +1,20 @@ +What: /sys/bus/i2c/.../idle_state +Date: January 2019 +KernelVersion: 5.2 +Contact: Robert Shearman <robert.shearman@att.com> +Description: + Value that exists only for mux devices that can be + written to control the behaviour of the multiplexer on + idle. Possible values: + -2 - disconnect on idle, i.e. deselect the last used + channel, which is useful when there is a device + with an address that conflicts with another + device on another mux on the same parent bus. + -1 - leave the mux as-is, which is the most optimal + setting in terms of I2C operations and is the + default mode. + 0..<nchans> - set the mux to a predetermined channel, + which is useful if there is one channel that is + used almost always, and you want to reduce the + latency for normal operations after rare + transactions on other channels |