From: "Yang,Wei" <Wei.Yang@windriver.com>
To: Tang Yuantian-B29983 <B29983@freescale.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Jia Hongtao-B38951 <B38951@freescale.com>
Subject: Re: [PATCH] powerpc: Add I2C bus multiplexer node for B4 and T4240QDS
Date: Wed, 4 Sep 2013 12:27:11 +0800 [thread overview]
Message-ID: <5226B69F.207@windriver.com> (raw)
In-Reply-To: <D07C73A334FF604B95B3CBD2A545D07B15056D2E@039-SN2MPN1-011.039d.mgd.msft.net>
On 09/04/2013 12:03 PM, Tang Yuantian-B29983 wrote:
> Hi,
> I noticed that there are already some nodes in i2c bus.
Sorry for my late response, yeah, just as you noticed, some eeprom nodes
already are inside i2c bus.:-)
Wei
> You should at least move the existing node into PCA9547.
>
> Thanks,
> Yuantian
>
>
>> -----Original Message-----
>> From: Linuxppc-dev [mailto:linuxppc-dev-
>> bounces+b29983=freescale.com@lists.ozlabs.org] On Behalf Of Jia Hongtao-
>> B38951
>> Sent: 2013年9月4日 星期三 11:38
>> To: Yang,Wei
>> Cc: Wood Scott-B07421; linuxppc-dev@lists.ozlabs.org
>> Subject: RE: [PATCH] powerpc: Add I2C bus multiplexer node for B4 and
>> T4240QDS
>>
>> Hi Wei,
>>
>> I totally agree that the i2c nodes topology should end up like you said.
>>
>> But I think adding sub-nodes should step by step.
>> Actually the hardware i2c topology are huge like on T4.
>> So I'd like to adding nodes when we needed.
>> If you think the sub-nodes are needed please send another patch based on
>> mine.
>> I think this is the more reasonable way.
>>
>> Thanks.
>>
>> -Hongtao
>>
>>
>>> -----Original Message-----
>>> From: Yang,Wei [mailto:Wei.Yang@windriver.com]
>>> Sent: Wednesday, September 04, 2013 9:27 AM
>>> To: Jia Hongtao-B38951
>>> Cc: linuxppc-dev@lists.ozlabs.org; Wood Scott-B07421; Jia
>>> Hongtao-B38951
>>> Subject: Re: [PATCH] powerpc: Add I2C bus multiplexer node for B4 and
>>> T4240QDS
>>>
>>> On 09/03/2013 03:51 PM, Jia Hongtao wrote:
>>>> In both B4 and T4240QDS platform PCA9547 I2C bus multiplexer is used.
>>> Hi Hongtao,
>>>
>>> If you want to support I2C bus multiplexer, for T4 and B4QDS platform,
>>> since some eeprom devices is connected to PCA9574 I2C bus multiplexer,
>>> so these devices should be connected to pca9547 node. Just like the
>>> following, what do you think of it?
>>>
>>> + pca9547@77 {
>>> + compatible = "philips,pca9547";
>>> + reg = <0x77>;
>>> + #address-cells = <1>;
>>> + #size-cells = <0>;
>>> + channel@0 {
>>> + #address-cells = <1>;
>>> + #size-cells = <0>;
>>> + reg = <0>;
>>> + eeprom@51 {
>>> + compatible =
>>> "at24,24c256";
>>> + reg = <0x51>;
>>> + };
>>> + eeprom@52 {
>>> + compatible =
>>> "at24,24c256";
>>> + reg = <0x52>;
>>> + };
>>> + eeprom@53 {
>>> + compatible =
>>> "at24,24c256";
>>> + reg = <0x53>;
>>> + };
>>> + eeprom@54 {
>>> + compatible =
>>> "at24,24c256";
>>> + reg = <0x54>;
>>> + };
>>> + eeprom@55 {
>>> + compatible =
>>> "at24,24c256";
>>> + reg = <0x55>;
>>> + };
>>> + eeprom@56 {
>>> + compatible =
>>> "at24,24c256";
>>> + reg = <0x56>;
>>> + };
>>> + rtc@68 {
>>> + compatible =
>>> "dallas,ds3232";
>>> + reg = <0x68>;
>>> + interrupts =
>>> <0x1 0x1 0 0>;
>>> + };
>>> + };
>>>
>>> Wei
>>>> Signed-off-by: Jia Hongtao <hongtao.jia@freescale.com>
>>>> ---
>>>> arch/powerpc/boot/dts/b4qds.dtsi | 4 ++++
>>>> arch/powerpc/boot/dts/t4240qds.dts | 4 ++++
>>>> 2 files changed, 8 insertions(+)
>>>>
>>>> diff --git a/arch/powerpc/boot/dts/b4qds.dtsi
>>>> b/arch/powerpc/boot/dts/b4qds.dtsi
>>>> index e6d2f8f..2aa3399 100644
>>>> --- a/arch/powerpc/boot/dts/b4qds.dtsi
>>>> +++ b/arch/powerpc/boot/dts/b4qds.dtsi
>>>> @@ -120,6 +120,10 @@
>>>> };
>>>>
>>>> i2c@118000 {
>>>> + pca9547@77 {
>>>> + compatible = "philips,pca9547";
>>>> + reg = <0x77>;
>>>> + };
>>>> eeprom@50 {
>>>> compatible = "at24,24c64";
>>>> reg = <0x50>;
>>>> diff --git a/arch/powerpc/boot/dts/t4240qds.dts
>>>> b/arch/powerpc/boot/dts/t4240qds.dts
>>>> index 0555976..084db57 100644
>>>> --- a/arch/powerpc/boot/dts/t4240qds.dts
>>>> +++ b/arch/powerpc/boot/dts/t4240qds.dts
>>>> @@ -118,6 +118,10 @@
>>>> };
>>>>
>>>> i2c@118000 {
>>>> + pca9547@77 {
>>>> + compatible = "philips,pca9547";
>>>> + reg = <0x77>;
>>>> + };
>>>> eeprom@51 {
>>>> compatible = "at24,24c256";
>>>> reg = <0x51>;
>>
>> _______________________________________________
>> Linuxppc-dev mailing list
>> Linuxppc-dev@lists.ozlabs.org
>> https://lists.ozlabs.org/listinfo/linuxppc-dev
prev parent reply other threads:[~2013-09-04 4:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 7:51 [PATCH] powerpc: Add I2C bus multiplexer node for B4 and T4240QDS Jia Hongtao
2013-09-04 1:27 ` Yang,Wei
2013-09-04 3:30 ` Tang Yuantian-B29983
2013-09-05 18:40 ` Scott Wood
2013-09-06 2:30 ` Tang Yuantian-B29983
2013-09-06 15:17 ` Scott Wood
2013-09-04 3:37 ` Jia Hongtao-B38951
2013-09-04 4:03 ` Tang Yuantian-B29983
2013-09-04 4:10 ` Jia Hongtao-B38951
2013-09-04 4:27 ` Yang,Wei [this message]
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=5226B69F.207@windriver.com \
--to=wei.yang@windriver.com \
--cc=B07421@freescale.com \
--cc=B29983@freescale.com \
--cc=B38951@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
/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).