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