From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Dinh Nguyen <dinguyen@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: Oleksij Rempel <o.rempel@pengutronix.de>,
kernel@pengutronix.de, Russell King <linux@armlinux.org.uk>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v1] ARM: dts: socfpga: fix nand compatible
Date: Thu, 14 Sep 2017 08:49:40 +0200 [thread overview]
Message-ID: <20170914064940.5639-1-o.rempel@pengutronix.de> (raw)
the compatible was changed with patch:
|commit a56609c4c3f34de76d905e39160511b3c53310ac
|Author: Masahiro Yamada <yamada.masahiro@socionext.com>
|Date: Thu Mar 30 15:45:53 2017 +0900
|
| mtd: nand: denali_dt: enable HW_ECC_FIXUP for Altera SOCFPGA variant
|
| There are various customizable parameters, so several variants for
| this IP. A generic compatible like "denali,denali-nand-dt" is
| useless. Moreover, there are multiple things wrong with this string.
| (Refer to Rob's comment [1])
|
| The "denali,denali-nand-dt" was added by Altera for the SOCFPGA port.
| Replace it with a more specific string "altr,socfpga-denali-nand".
| There are no users (in upstream) of the old compatible string.
|
| The Denali IP on SOCFPGA incorporates the hardware ECC fixup engine.
| So, this capability should be associated with the compatible.
|
| [1] https://lkml.org/lkml/2016/12/1/450
Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
---
arch/arm/boot/dts/socfpga.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/socfpga.dtsi b/arch/arm/boot/dts/socfpga.dtsi
index 7e24dc8e82d4..d697f5062624 100644
--- a/arch/arm/boot/dts/socfpga.dtsi
+++ b/arch/arm/boot/dts/socfpga.dtsi
@@ -744,7 +744,7 @@
nand0: nand@ff900000 {
#address-cells = <0x1>;
#size-cells = <0x1>;
- compatible = "denali,denali-nand-dt";
+ compatible = "altr,socfpga-denali-nand";
reg = <0xff900000 0x100000>,
<0xffb80000 0x10000>;
reg-names = "nand_data", "denali_reg";
--
2.11.0
reply other threads:[~2017-09-14 6:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170914064940.5639-1-o.rempel@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@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).