1*f1fb64b0SRobert ShearmanWhat: /sys/bus/i2c/.../idle_state 2*f1fb64b0SRobert ShearmanDate: January 2019 3*f1fb64b0SRobert ShearmanKernelVersion: 5.2 4*f1fb64b0SRobert ShearmanContact: Robert Shearman <robert.shearman@att.com> 5*f1fb64b0SRobert ShearmanDescription: 6*f1fb64b0SRobert Shearman Value that exists only for mux devices that can be 7*f1fb64b0SRobert Shearman written to control the behaviour of the multiplexer on 8*f1fb64b0SRobert Shearman idle. Possible values: 9*f1fb64b0SRobert Shearman -2 - disconnect on idle, i.e. deselect the last used 10*f1fb64b0SRobert Shearman channel, which is useful when there is a device 11*f1fb64b0SRobert Shearman with an address that conflicts with another 12*f1fb64b0SRobert Shearman device on another mux on the same parent bus. 13*f1fb64b0SRobert Shearman -1 - leave the mux as-is, which is the most optimal 14*f1fb64b0SRobert Shearman setting in terms of I2C operations and is the 15*f1fb64b0SRobert Shearman default mode. 16*f1fb64b0SRobert Shearman 0..<nchans> - set the mux to a predetermined channel, 17*f1fb64b0SRobert Shearman which is useful if there is one channel that is 18*f1fb64b0SRobert Shearman used almost always, and you want to reduce the 19*f1fb64b0SRobert Shearman latency for normal operations after rare 20*f1fb64b0SRobert Shearman transactions on other channels 21