devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>
To: devicetree@vger.kernel.org, robh@kernel.org,
	mark.rutland@arm.com, shawnguo@kernel.org
Cc: Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>,
	linux-arm-kernel@lists.infradead.org, leoyang.li@nxp.com
Subject: [PATCH 1/2][RESEND] ARM: dts: Add big-endian in nor node for ls1021a
Date: Tue, 28 Aug 2018 12:29:35 +0530	[thread overview]
Message-ID: <20180828065936.8040-2-prabhakar.kushwaha@nxp.com> (raw)
In-Reply-To: <20180828065936.8040-1-prabhakar.kushwaha@nxp.com>

NOR and IFC controller connectivity is big-endian.
So add big-endian field in nor device tree node allowing
IFC controller to read/write data from/to the flash correctly.

Signed-off-by: Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>
---
Based on 147395ea40b36b "dt-bindings: mtd-physmap: Add endianness supports"
RESEND keeping Li Yang <leoyang.li@nxp.com> 

 arch/arm/boot/dts/ls1021a-qds.dts | 2 ++
 arch/arm/boot/dts/ls1021a-twr.dts | 2 ++
 2 files changed, 4 insertions(+)

diff --git a/arch/arm/boot/dts/ls1021a-qds.dts b/arch/arm/boot/dts/ls1021a-qds.dts
index 499f41a2c6f0..923a25760516 100644
--- a/arch/arm/boot/dts/ls1021a-qds.dts
+++ b/arch/arm/boot/dts/ls1021a-qds.dts
@@ -1,5 +1,6 @@
 /*
  * Copyright 2013-2014 Freescale Semiconductor, Inc.
+ * Copyright 2018 NXP
  *
  * This file is dual-licensed: you can use it either under the terms
  * of the GPL or the X11 license, at your option. Note that this dual
@@ -235,6 +236,7 @@
 		#size-cells = <1>;
 		compatible = "cfi-flash";
 		reg = <0x0 0x0 0x8000000>;
+		big-endian;
 		bank-width = <2>;
 		device-width = <1>;
 	};
diff --git a/arch/arm/boot/dts/ls1021a-twr.dts b/arch/arm/boot/dts/ls1021a-twr.dts
index f0c949d74833..8b48c3c7cd21 100644
--- a/arch/arm/boot/dts/ls1021a-twr.dts
+++ b/arch/arm/boot/dts/ls1021a-twr.dts
@@ -1,5 +1,6 @@
 /*
  * Copyright 2013-2014 Freescale Semiconductor, Inc.
+ * Copyright 2018 NXP
  *
  * This file is dual-licensed: you can use it either under the terms
  * of the GPL or the X11 license, at your option. Note that this dual
@@ -203,6 +204,7 @@
 		#size-cells = <1>;
 		compatible = "cfi-flash";
 		reg = <0x0 0x0 0x8000000>;
+		big-endian;
 		bank-width = <2>;
 		device-width = <1>;
 	};
-- 
2.14.1

  reply	other threads:[~2018-08-28  6:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28  6:59 [PATCH] arm64: dts: remove big-endian filed from IFC controller Prabhakar Kushwaha
2018-08-28  6:59 ` Prabhakar Kushwaha [this message]
2018-08-28 20:46   ` [PATCH 1/2][RESEND] ARM: dts: Add big-endian in nor node for ls1021a Li Yang
2018-08-28 22:25   ` Fabio Estevam
2018-08-29  2:55     ` Prabhakar Kushwaha
2018-09-02 23:58   ` Shawn Guo
2018-08-28  6:59 ` [PATCH 2/2][RESEND] arm64: dts: Add big-endian in nor node for ls104xa Prabhakar Kushwaha
2018-08-28 20:44   ` Li Yang
2018-08-28 22:26   ` Fabio Estevam
2018-08-28 18:38 ` [PATCH] arm64: dts: remove big-endian filed from IFC controller Li Yang

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=20180828065936.8040-2-prabhakar.kushwaha@nxp.com \
    --to=prabhakar.kushwaha@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=leoyang.li@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=robh@kernel.org \
    --cc=shawnguo@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).