From: Florian Fainelli <f.fainelli@gmail.com>
To: Jaedon Shin <jaedon.shin@gmail.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Kevin Cernekee <cernekee@gmail.com>,
linux-mips@linux-mips.org, devicetree@vger.kernel.org,
computersforpeace@gmail.com
Subject: Re: [PATCH 1/4] MIPS: BMIPS: bcm7346: add nodes for NAND
Date: Thu, 25 Jun 2015 20:00:32 -0700 [thread overview]
Message-ID: <558CC050.6040101@gmail.com> (raw)
In-Reply-To: <EFAFA0BE-CC2F-4342-9C89-DED8EC6CF377@gmail.com>
Le 06/25/15 01:52, Jaedon Shin a écrit :
>
>> On Jun 25, 2015, at 4:32 AM, Florian Fainelli <f.fainelli@gmail.com> wrote:
>>
>> +Brian,
>>
>> On 23/06/15 23:08, Jaedon Shin wrote:
>>> Add NAND device nodes to BMIPS based BCM7346 platform.
>>>
>>> Signed-off-by: Jaedon Shin <jaedon.shin@gmail.com>
>>> ---
>>
>> [snip]
>>
>>> +
>>> +&nand0 {
>>> + status = "okay";
>>> +
>>> + nandcs@1 {
>>> + compatible = "brcm,nandcs";
>>> + reg = <1>;
>>> + nand-ecc-step-size = <512>;
>>> + nand-ecc-strength = <8>;
>>> + nand-on-flash-bbt;
>>> +
>>> + #size-cells = <2>;
>>> + #address-cells = <2>;
>>> +
>>> + flash1.rootfs0@0 {
>>> + reg = <0x0 0x0 0x0 0x80000000>;
>>> + };
>>> +
>>> + flash1.rootfs1@80000000 {
>>> + reg = <0x0 0x80000000 0x0 0x80000000>;
>>> + };
>>> + };
>>> +};
>>
>> Should we create something like brcmnand-cs1-512-8 to reduce the amount
>> of duplication between DTS files?
>> --
>> Florian
>
> I Think that is not duplication.
>
> I have no reference boards, but this node is maybe explaining for hardware
> description of the BCM97346DBSMB reference board. The nodes are changed by
> EBI CS and ECC capabilities of NAND flash. I used brcmnand-cs2-512-4 and
> brcmnand-cs1-512-4 for others.
Then I am confused, your 4 patches add identical NAND flash chip
properties for 7346, 7358, 7360 and 7362: CS#1, 512 bytes of ECC step
size and 8 bits of ECC strength, am I missing something?
--
Florian
WARNING: multiple messages have this Message-ID (diff)
From: Florian Fainelli <f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Jaedon Shin <jaedon.shin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Ralf Baechle <ralf-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org>,
Kevin Cernekee <cernekee-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-mips-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
computersforpeace-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: [PATCH 1/4] MIPS: BMIPS: bcm7346: add nodes for NAND
Date: Thu, 25 Jun 2015 20:00:32 -0700 [thread overview]
Message-ID: <558CC050.6040101@gmail.com> (raw)
In-Reply-To: <EFAFA0BE-CC2F-4342-9C89-DED8EC6CF377-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Le 06/25/15 01:52, Jaedon Shin a écrit :
>
>> On Jun 25, 2015, at 4:32 AM, Florian Fainelli <f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>>
>> +Brian,
>>
>> On 23/06/15 23:08, Jaedon Shin wrote:
>>> Add NAND device nodes to BMIPS based BCM7346 platform.
>>>
>>> Signed-off-by: Jaedon Shin <jaedon.shin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>>> ---
>>
>> [snip]
>>
>>> +
>>> +&nand0 {
>>> + status = "okay";
>>> +
>>> + nandcs@1 {
>>> + compatible = "brcm,nandcs";
>>> + reg = <1>;
>>> + nand-ecc-step-size = <512>;
>>> + nand-ecc-strength = <8>;
>>> + nand-on-flash-bbt;
>>> +
>>> + #size-cells = <2>;
>>> + #address-cells = <2>;
>>> +
>>> + flash1.rootfs0@0 {
>>> + reg = <0x0 0x0 0x0 0x80000000>;
>>> + };
>>> +
>>> + flash1.rootfs1@80000000 {
>>> + reg = <0x0 0x80000000 0x0 0x80000000>;
>>> + };
>>> + };
>>> +};
>>
>> Should we create something like brcmnand-cs1-512-8 to reduce the amount
>> of duplication between DTS files?
>> --
>> Florian
>
> I Think that is not duplication.
>
> I have no reference boards, but this node is maybe explaining for hardware
> description of the BCM97346DBSMB reference board. The nodes are changed by
> EBI CS and ECC capabilities of NAND flash. I used brcmnand-cs2-512-4 and
> brcmnand-cs1-512-4 for others.
Then I am confused, your 4 patches add identical NAND flash chip
properties for 7346, 7358, 7360 and 7362: CS#1, 512 bytes of ECC step
size and 8 bits of ECC strength, am I missing something?
--
Florian
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-06-26 3:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 6:08 [PATCH 0/4] MIPS: BMIPS: dts: add NAND device nodes for bcm7xxx platforms Jaedon Shin
2015-06-24 6:08 ` Jaedon Shin
2015-06-24 6:08 ` [PATCH 1/4] MIPS: BMIPS: bcm7346: add nodes for NAND Jaedon Shin
2015-06-24 6:08 ` Jaedon Shin
2015-06-24 19:32 ` Florian Fainelli
2015-06-24 19:32 ` Florian Fainelli
2015-06-25 8:52 ` Jaedon Shin
2015-06-25 8:52 ` Jaedon Shin
2015-06-26 3:00 ` Florian Fainelli [this message]
2015-06-26 3:00 ` Florian Fainelli
2015-06-26 13:54 ` Jaedon Shin
2015-06-26 13:54 ` Jaedon Shin
2015-06-26 13:54 ` Jaedon Shin
2015-06-26 16:32 ` Florian Fainelli
2015-06-26 16:32 ` Florian Fainelli
2015-06-24 6:08 ` [PATCH 2/4] MIPS: BMIPS: bcm7358: " Jaedon Shin
2015-06-24 6:08 ` Jaedon Shin
2015-06-24 6:08 ` [PATCH 3/4] MIPS: BMIPS: bcm7360: " Jaedon Shin
2015-06-24 6:08 ` Jaedon Shin
2015-06-24 6:08 ` [PATCH 4/4] MIPS: BMIPS: bcm7362: " Jaedon Shin
2015-06-24 6:08 ` Jaedon Shin
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=558CC050.6040101@gmail.com \
--to=f.fainelli@gmail.com \
--cc=cernekee@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jaedon.shin@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.