From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Wolfram Sang <wsa@the-dreams.de>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux I2C <linux-i2c@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
Jan Luebbe <jlu@pengutronix.de>
Subject: Re: [RFC v2 2/4] dt-bindings: i2c: mux: demux-pinctrl: add bindings
Date: Wed, 13 Jan 2016 17:07:55 +0300 [thread overview]
Message-ID: <56965A3B.60208@cogentembedded.com> (raw)
In-Reply-To: <20160113125227.GD1540@katana>
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
next prev parent reply other threads:[~2016-01-13 14:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 13:51 [RFC v2 0/4] i2c/of: switch I2C IP cores at runtime via OF_DYNAMIC Wolfram Sang
2016-01-06 13:51 ` [RFC v2 1/4] of: make of_mutex public Wolfram Sang
2016-01-06 14:26 ` Geert Uytterhoeven
2016-01-06 13:51 ` [RFC v2 2/4] dt-bindings: i2c: mux: demux-pinctrl: add bindings Wolfram Sang
2016-01-06 14:30 ` Geert Uytterhoeven
2016-01-13 12:52 ` Wolfram Sang
2016-01-13 14:07 ` Sergei Shtylyov [this message]
2016-01-07 16:56 ` Jan Lübbe
2016-01-13 13:02 ` Wolfram Sang
2016-01-11 2:52 ` Rob Herring
2016-01-11 8:01 ` Geert Uytterhoeven
2016-01-06 13:51 ` [RFC v2 3/4] i2c: mux: demux-pinctrl: add driver Wolfram Sang
[not found] ` <1452088285-6427-4-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2016-01-06 14:20 ` Geert Uytterhoeven
2016-01-13 12:55 ` Wolfram Sang
2016-01-13 16:16 ` Geert Uytterhoeven
2016-01-06 17:08 ` Rob Herring
2016-01-13 12:55 ` Wolfram Sang
2016-01-06 13:51 ` [RFC v2 4/4] ARM: shmobile: r8a7790: rework dts to use i2c demuxer Wolfram Sang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56965A3B.60208@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=jlu@pengutronix.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=pantelis.antoniou@konsulko.com \
--cc=wsa@the-dreams.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).