From: Pankaj Bansal <pankaj.bansal@nxp.com>
To: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Shawn Guo <shawnguo@kernel.org>, Leo Li <leoyang.li@nxp.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Pankaj Bansal <pankaj.bansal@nxp.com>
Subject: [PATCH 3/3] dts: arm64: fsl: lsch2: Fix the endianness property in nodes
Date: Wed, 12 Dec 2018 07:09:58 +0000 [thread overview]
Message-ID: <20181212123505.32415-4-pankaj.bansal@nxp.com> (raw)
In-Reply-To: <20181212123505.32415-1-pankaj.bansal@nxp.com>
The endianness ought to be mentioned in dts nodes if the device
is big endian. this helps the software to read/write device registers.
refer Documentation/devicetree/bindings/common-properties.txt
Signed-off-by: Pankaj Bansal <pankaj.bansal@nxp.com>
---
arch/arm64/boot/dts/freescale/fsl-ls1043a.dtsi | 3 +++
arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi | 5 +++--
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1043a.dtsi b/arch/arm64/boot/dts/freescale/fsl-ls1043a.dtsi
index eea23b84daee..9e497757229f 100644
--- a/arch/arm64/boot/dts/freescale/fsl-ls1043a.dtsi
+++ b/arch/arm64/boot/dts/freescale/fsl-ls1043a.dtsi
@@ -240,6 +240,7 @@
ranges = <0x0 0x00 0x1700000 0x100000>;
reg = <0x00 0x1700000 0x0 0x100000>;
interrupts = <0 75 0x4>;
+ big-endian;
sec_jr0: jr@10000 {
compatible = "fsl,sec-v5.4-job-ring",
@@ -367,6 +368,7 @@
reg = <0x0 0x1880000 0x0 0x10000>;
interrupts = <GIC_SPI 45 IRQ_TYPE_LEVEL_HIGH>;
memory-region = <&qman_fqd &qman_pfdr>;
+ big-endian;
};
bman: bman@1890000 {
@@ -374,6 +376,7 @@
reg = <0x0 0x1890000 0x0 0x10000>;
interrupts = <GIC_SPI 45 IRQ_TYPE_LEVEL_HIGH>;
memory-region = <&bman_fbpr>;
+ big-endian;
};
bportals: bman-portals@508000000 {
diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi b/arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi
index 49a363abf2ad..60a0bad946ed 100644
--- a/arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi
+++ b/arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi
@@ -245,6 +245,7 @@
ranges = <0x0 0x00 0x1700000 0x100000>;
reg = <0x00 0x1700000 0x0 0x100000>;
interrupts = <GIC_SPI 75 IRQ_TYPE_LEVEL_HIGH>;
+ big-endian;
sec_jr0: jr@10000 {
compatible = "fsl,sec-v5.4-job-ring",
@@ -284,7 +285,7 @@
reg = <0x0 0x1880000 0x0 0x10000>;
interrupts = <GIC_SPI 45 IRQ_TYPE_LEVEL_HIGH>;
memory-region = <&qman_fqd &qman_pfdr>;
-
+ big-endian;
};
bman: bman@1890000 {
@@ -292,7 +293,7 @@
reg = <0x0 0x1890000 0x0 0x10000>;
interrupts = <GIC_SPI 45 IRQ_TYPE_LEVEL_HIGH>;
memory-region = <&bman_fbpr>;
-
+ big-endian;
};
qportals: qman-portals@500000000 {
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2018-12-12 7:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 7:09 [PATCH 0/3] dts: fsl: lsch2: dts modifications for chassis 2 devices Pankaj Bansal
2018-12-12 7:09 ` [PATCH 1/3] dts: arm64: fsl: lsch2: fix status field of serdes controlled devices Pankaj Bansal
2019-01-11 2:38 ` Shawn Guo
2018-12-12 7:09 ` [PATCH 2/3] dts: arm64: fsl: lsch2: fix the rgmii phy type Pankaj Bansal
2018-12-12 7:09 ` Pankaj Bansal [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=20181212123505.32415-4-pankaj.bansal@nxp.com \
--to=pankaj.bansal@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.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