From: rjui@broadcom.com (Ray Jui)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/2] arm64: dts: Add BRCM IPROC NAND DT node for NS2
Date: Tue, 27 Oct 2015 17:25:32 -0700 [thread overview]
Message-ID: <563015FC.9040006@broadcom.com> (raw)
In-Reply-To: <20151028001920.GY13239@google.com>
On 10/27/2015 5:19 PM, Brian Norris wrote:
> On Fri, Oct 23, 2015 at 10:46:13AM +0530, Anup Patel wrote:
>> The NAND controller on NS2 SoC is compatible with existing
>> BRCM IPROC NAND driver so let's enable it in NS2 DT and
>> NS2 SVK DT.
>>
>> This patch also fixes use of node labels in ns2-svk.dts.
>>
>> Signed-off-by: Anup Patel <anup.patel@broadcom.com>
>> Reviewed-by: Ray Jui <rjui@broadcom.com>
>> Reviewed-by: Scott Branden <sbranden@broadcom.com>
>> ---
>> arch/arm64/boot/dts/broadcom/ns2-svk.dts | 30 ++++++++++++++++++++----------
>> arch/arm64/boot/dts/broadcom/ns2.dtsi | 14 ++++++++++++++
>> 2 files changed, 34 insertions(+), 10 deletions(-)
>>
>> diff --git a/arch/arm64/boot/dts/broadcom/ns2-svk.dts b/arch/arm64/boot/dts/broadcom/ns2-svk.dts
>> index e5950d5..6bb3d4d 100644
>> --- a/arch/arm64/boot/dts/broadcom/ns2-svk.dts
>> +++ b/arch/arm64/boot/dts/broadcom/ns2-svk.dts
>> @@ -50,18 +50,28 @@
>> device_type = "memory";
>> reg = <0x000000000 0x80000000 0x00000000 0x40000000>;
>> };
>> +};
>>
>> - soc: soc {
>> - i2c0: i2c at 66080000 {
>> - status = "ok";
>> - };
>> +&i2c0 {
>> + status = "ok";
>> +};
>>
>> - i2c1: i2c at 660b0000 {
>> - status = "ok";
>> - };
>> +&i2c1 {
>> + status = "ok";
>> +};
>> +
>> +&uart3 {
>> + status = "ok";
>> +};
>>
>> - uart3: serial at 66130000 {
>> - status = "ok";
>> - };
>> +&nand {
>> + nandcs at 0 {
>> + compatible = "brcm,nandcs";
>> + reg = <0>;
>> + nand-ecc-mode = "hw";
>> + nand-ecc-strength = <8>;
>> + nand-ecc-step-size = <512>;
>> + #address-cells = <1>;
>> + #size-cells = <1>;
>> };
>> };
>> diff --git a/arch/arm64/boot/dts/broadcom/ns2.dtsi b/arch/arm64/boot/dts/broadcom/ns2.dtsi
>> index f603277..9610822 100644
>> --- a/arch/arm64/boot/dts/broadcom/ns2.dtsi
>> +++ b/arch/arm64/boot/dts/broadcom/ns2.dtsi
>> @@ -212,5 +212,19 @@
>> compatible = "brcm,iproc-rng200";
>> reg = <0x66220000 0x28>;
>> };
>> +
>> + nand: nand at 66460000 {
>> + compatible = "brcm,nand-iproc", "brcm,brcmnand-v6.1";
>
> Technically, the binding says you should also have "brcm,brcmnand" as a
> last resort. Otherwise (for the NAND parts):
>
I believe Anup was seeing issues when both "brcm,nand-iproc" and
"brcm,brcmnand" are present.
Note "brcm,nand-iproc" invokes 'iproc_nand_probe', which calls
'brcmnand_probe' in the end.
"brcm,brcmnand" invokes 'brcmstb_nand_probe', which also calls
'brcmstb_probe', but without all the prep configuration required for
"brcm,nand-iproc".
> Reviewed-by: Brian Norris <computersforpeace@gmail.com>
next prev parent reply other threads:[~2015-10-28 0:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 5:16 [PATCH v3 0/2] NAND support for Broadcom NS2 SoC Anup Patel
2015-10-23 5:16 ` [PATCH v3 1/2] mtd: brcmnand: Force 8bit mode before doing nand_scan_ident() Anup Patel
2015-10-28 0:14 ` Brian Norris
2015-10-28 9:13 ` Anup Patel
2015-10-23 5:16 ` [PATCH v3 2/2] arm64: dts: Add BRCM IPROC NAND DT node for NS2 Anup Patel
2015-10-28 0:19 ` Brian Norris
2015-10-28 0:25 ` Ray Jui [this message]
2015-10-28 0:39 ` Brian Norris
2015-10-28 0:46 ` Ray Jui
2015-10-28 9:06 ` Anup Patel
2015-10-28 16:08 ` Ray Jui
2015-10-28 18:55 ` Florian Fainelli
2015-10-30 18:49 ` Brian Norris
2015-10-30 18:55 ` Ray Jui
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=563015FC.9040006@broadcom.com \
--to=rjui@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.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).