CCing linux-pm, maybe they know more... > The extra I2C traffic consumes extra power. If the bus is terminated > using 2k resistors, approximately 1mA of current (assuming ~2V > signals) is flowing when the bus is pulled low. On low power > designs, this extra power consumption is noticable. There is no way > to turn the mux "off" from either user or kernel space. The signals > going through the mux to a place where no I2C device is actually > listening are only wasting power. I only have an overview of current linux pm mechanisms. I wonder if those can't be used somehow. Like if devices on the multiplexed bus are idle (well, only regarding transfers), then we can switch off the muxer. > The I2C signals are used to control sensitive codecs. When looking > at the sampled data, the I2C traffic is visible in the captured > analog signal. To prevent this from happening, the mux can be I wonder: Is this really a feature of sensitive codecs or an issue of the board design? > disabled whenever not communicating with the codec. This could be > accomplished with the "deselect_on_exit" boolean, but because audio > driver sends the codec parameters in dozens of small transactions, > this will result in a lot more needless I2C traffic, constantly > switching the mux for each codec setting. Has this been looked at? ASoC supports grouping of tranfers IIRC. Maybe your I2C driver is only missing I2C_M_NOSTART?. > Would it be acceptable if I made the timeout optional, by making the > "deselect_on_exit" boolean into a three-state value (off, on, > timeout)? Or, alternatively, implement "deselect_on_exit" using the > timeout scheme (probably with a very short timeout)? I have a number of concerns designwise. First, if we do something like shutting-down-a-bus-if-there-are-no-transfers-expected, it definately should be in the core, not the driver. As said before, I have the assumption it should even be connected to the runtime pm core via some callback. And if we have that for I2C, we surely want that for other buses as well, at least SPI. Also, the timeout thing sounds too heuristic to me. Later, people might want to change the timeout value depending on workloads or so, and then a governor, etc... No, thanks. BTW is it feasible to shut down the whole I2C bus at controller level after transfers? No needless transfers and maybe even more power savings. Anyway, thanks for letting me know about your requirements (they should have been in the original commit message, though ;))
Attachment:
signature.asc
Description: Digital signature
