From: Fabio Estevam <festevam@gmail.com>
To: shawnguo@kernel.org
Cc: Fabio Estevam <fabio.estevam@nxp.com>,
devicetree@vger.kernel.org, robh+dt@kernel.org,
linux-arm-kernel@lists.infradead.org, kernel@pengutronix.de
Subject: [PATCH v2 2/3] ARM: dts: imx51: Add M4IF support
Date: Mon, 9 Jul 2018 15:19:14 -0300 [thread overview]
Message-ID: <1531160355-12384-2-git-send-email-festevam@gmail.com> (raw)
In-Reply-To: <1531160355-12384-1-git-send-email-festevam@gmail.com>
From: Fabio Estevam <fabio.estevam@nxp.com>
As per the i.MX51 Reference Manual the M4IF register region
starts at 0x83fd8000 and has a 4kB address range.
Add support for it.
Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
Tested-by: Sergey Lapin <sergey.lapin@cogentembedded.com>
---
Changes since v1:
- None
arch/arm/boot/dts/imx51.dtsi | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/imx51.dtsi b/arch/arm/boot/dts/imx51.dtsi
index 66e4187..b417c39 100644
--- a/arch/arm/boot/dts/imx51.dtsi
+++ b/arch/arm/boot/dts/imx51.dtsi
@@ -531,6 +531,11 @@
status = "disabled";
};
+ m4if: m4if@83fd8000 {
+ compatible = "fsl,imx51-m4if";
+ reg = <0x83fd8000 0x1000>;
+ };
+
weim: weim@83fda000 {
#address-cells = <2>;
#size-cells = <1>;
--
2.7.4
next prev parent reply other threads:[~2018-07-09 18:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 18:19 [PATCH v2 1/3] dt-bindings: freescale: Add bindings for the M4IF module Fabio Estevam
2018-07-09 18:19 ` Fabio Estevam [this message]
2018-07-10 8:01 ` [PATCH v2 2/3] ARM: dts: imx51: Add M4IF support Lucas Stach
2018-07-09 18:19 ` [PATCH v2 2/2] ARM: imx51: Configure M4IF to avoid visual artifacts Fabio Estevam
2018-07-09 18:23 ` Fabio Estevam
2018-07-10 7:59 ` [PATCH v2 1/3] dt-bindings: freescale: Add bindings for the M4IF module Lucas Stach
2018-07-11 19:15 ` Rob Herring
2018-07-12 1:46 ` Shawn Guo
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=1531160355-12384-2-git-send-email-festevam@gmail.com \
--to=festevam@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robh+dt@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).