From: Robert Shearman <robert.shearman@xxxxxxx> Update the binding docs for i2c-mux-pca954x to reflect that the driver now defaults to idle-disconnect behaviour by removing the documentation of the previous i2c-mux-idle-disconnect property and introducing a new inverse i2c-mux-no-idle-disconnect property. Signed-off-by: Robert Shearman <robert.shearman@xxxxxxx> --- Documentation/devicetree/bindings/i2c/i2c-mux-pca954x.txt | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/Documentation/devicetree/bindings/i2c/i2c-mux-pca954x.txt b/Documentation/devicetree/bindings/i2c/i2c-mux-pca954x.txt index 30ac6a60f041..c3a94de8b3ef 100644 --- a/Documentation/devicetree/bindings/i2c/i2c-mux-pca954x.txt +++ b/Documentation/devicetree/bindings/i2c/i2c-mux-pca954x.txt @@ -25,9 +25,11 @@ Required Properties: Optional Properties: - reset-gpios: Reference to the GPIO connected to the reset input. - - i2c-mux-idle-disconnect: Boolean; if defined, forces mux to disconnect all - children in idle state. This is necessary for example, if there are several - multiplexers on the bus and the devices behind them use same I2C addresses. + - i2c-mux-no-idle-disconnect: Boolean; if defined, asks mux to not + disconnect children in idle state. This optimises I2C parent + operations and is useful if it is guaranteed that there are no + multiplexers on the bus with devices behind them using the same + I2C address. - interrupts: Interrupt mapping for IRQ. - interrupt-controller: Marks the device node as an interrupt controller. - #interrupt-cells : Should be two. -- 2.20.1
