Re: [PATCH] i2c: Make I2C ID tables non-mandatory for DT'ed and/or ACPI'ed devices

Am 12.06.2014 09:55, schrieb Linus Walleij: On Wed, Jun 4, 2014 at 8:09 AM, Michael Lawnick wrote: Am 03.06.2014 13:18, schrieb Linus Walleij: On Mon, Jun 2, 2014 at 4:29 PM, Michael Lawnick wrote: Am 02.06.2014 14:16, schrieb Linus Walleij: Is this really so useful on embedded systems

Re: [PATCH] i2c: Make I2C ID tables non-mandatory for DT'ed and/or ACPI'ed devices

Am 03.06.2014 13:18, schrieb Linus Walleij: On Mon, Jun 2, 2014 at 4:29 PM, Michael Lawnick wrote: Am 02.06.2014 14:16, schrieb Linus Walleij: Is this really so useful on embedded systems? I was under the impression that this method was something used on say PC desktops with temperature

Re: [PATCH] i2c: Make I2C ID tables non-mandatory for DT'ed and/or ACPI'ed devices

Am 02.06.2014 14:16, schrieb Linus Walleij: On Sat, May 31, 2014 at 3:48 PM, Wolfram Sang wrote: Right, I read the function which provides the functionality, but my point is; I don't think my patch changes the semantics in a way which would adversely affect this option. If you think that it

Re: [PATCH] i2c-mux-pca954x: Disable mux after 200ms timeout

Hi, Am 25.11.2013 14:43, schrieb Mike Looijmans: 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. ... Ha