Hello.
On 01/13/2016 03:52 PM, Wolfram Sang 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"?
That sounds like a question for our EPapr expert Sergei (CCed) :)
ePAPR only mentions "i2c". I'm not sure where the numeric part of the name
comes from in this case...
[...]
MBR, Sergei
--
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
