Hi Wolfram,
On Wed, Jan 6, 2016 at 2:51 PM, Wolfram Sang <wsa@xxxxxxxxxxxxx> wrote:
> These bindings allow an I2C bus to switch between multiple masters. This
> is not hot-swichting because connected I2C slaves will be
> re-instantiated. It is meant to select the best I2C core at runtime once
> the task is known. Example: Prefer i2c-gpio over another I2C core
> because of HW errata affetcing your use case.
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/i2c/i2c-demux-pinctrl.txt
> @@ -0,0 +1,155 @@
> +Here is a snipplet for a bus to be demuxed. It contains various i2c clients for
snippet
> +HDMI, so the bus is named "i2c-hdmi":
> +
> + i2chdmi: i2c@8 {
Would it make sense to call the node "i2c-bus@8"?
> +
> + compatible = "i2c-demux-pinctrl";
> + i2c-parent = <&gpioi2c>, <&iic2>, <&i2c2>;
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
