On 11/26/2013 10:06 AM, Wolfram Sang wrote:
On Tue, Nov 26, 2013 at 07:32:00AM +0100, Mike Looijmans wrote:
Leaving the mux enabled causes needless I2C traffic on the downstream
bus. De-selecting after every request causes excess I2C traffic and
switching.
This patch implements a hybrid solution: After 200ms of inactivity,
the mux is disabled.
Signed-off-by: Mike Looijmans <mike.looijmans@xxxxxxxx>
You still haven't answered my initial question. Also, please don't
resend without saying what changed since the last version.
Sorry, I never received the patch mail nor any replies into my own mailbox, so
I assumed the message was never actually sent (probably our mail server
considered it spam). I found it online though, so I'll try to answer your
questions now.
Michael Lawnick:
> Have you checked against behavior on cascaded muxes?
No, I didn't even realize it was at all possible to cascade muxes. And you're
right, this patch will break those.
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)?
Wolfram Sang:
> This is a bus. Why is this bad?
My customer has two reasons for wanting this change:
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.
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 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.
Kind regards,
Mike.
--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
