devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ray Jui <rjui@broadcom.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
	Rob Herring <robh+dt@kernel.org>, Arnd Bergmann <arnd@arndb.de>
Cc: Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	bcm-kernel-feedback-list@broadcom.com,
	devicetree@vger.kernel.org, Ray Jui <rjui@broadcom.com>
Subject: [PATCH v3 9/9] ARM: dts: fix Cygnus nand device node
Date: Mon, 21 Sep 2015 15:12:50 -0700	[thread overview]
Message-ID: <1442873570-20947-10-git-send-email-rjui@broadcom.com> (raw)
In-Reply-To: <1442873570-20947-1-git-send-email-rjui@broadcom.com>

The third compatible string "brcm,brcmnand" in bcm-cygnus.dtsi nand node
is incorrect, redundant and should be removed. "brcm,brcmnand" is meant to
be used by STB based Broadcom SoCs. All iProc based SoCs should use
"brcm,nand-iproc".

Signed-off-by: Ray Jui <rjui@broadcom.com>
---
 arch/arm/boot/dts/bcm-cygnus.dtsi | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/arch/arm/boot/dts/bcm-cygnus.dtsi b/arch/arm/boot/dts/bcm-cygnus.dtsi
index 24e058c..b5f9f34 100644
--- a/arch/arm/boot/dts/bcm-cygnus.dtsi
+++ b/arch/arm/boot/dts/bcm-cygnus.dtsi
@@ -234,8 +234,7 @@
 		};
 
 		nand: nand@18046000 {
-			compatible = "brcm,nand-iproc", "brcm,brcmnand-v6.1",
-				     "brcm,brcmnand";
+			compatible = "brcm,nand-iproc", "brcm,brcmnand-v6.1";
 			reg = <0x18046000 0x600>, <0xf8105408 0x600>,
 			      <0x18046f00 0x20>;
 			reg-names = "nand", "iproc-idm", "iproc-ext";
-- 
1.9.1

      parent reply	other threads:[~2015-09-21 22:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-21 22:12 [PATCH v3 0/9] Broadcom Cygnus device tree changes Ray Jui
     [not found] ` <1442873570-20947-1-git-send-email-rjui-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2015-09-21 22:12   ` [PATCH v3 1/9] ARM: dts: consolidate aliases for Cygnus dt files Ray Jui
2015-09-21 22:12   ` [PATCH v3 8/9] ARM: dts: enable touchscreen support on Cygnus Ray Jui
2015-09-23  0:58   ` [PATCH v3 0/9] Broadcom Cygnus device tree changes Florian Fainelli
2015-09-21 22:12 ` [PATCH v3 2/9] ARM: dts: Use label for device nodes in Cygnus dts Ray Jui
2015-09-21 22:12 ` [PATCH v3 3/9] ARM: dts: Put Cygnus core components under core bus Ray Jui
2015-09-21 22:12 ` [PATCH v3 4/9] ARM: dts: Move all Cygnus peripherals into axi bus Ray Jui
2015-09-21 22:12 ` [PATCH v3 5/9] ARM: dts: Reorder Cygnus peripherals Ray Jui
2015-09-21 22:12 ` [PATCH v3 6/9] ARM: dts: Enable various peripherals on bcm958305k Ray Jui
2015-09-21 22:12 ` [PATCH v3 7/9] ARM: dts: Enable NAND support on bcm911360_entphn Ray Jui
2015-09-21 22:12 ` Ray Jui [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=1442873570-20947-10-git-send-email-rjui@broadcom.com \
    --to=rjui@broadcom.com \
    --cc=arnd@arndb.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.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).