From: "Guido Günther" <agx@sigxcpu.org>
To: Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
NXP Linux Team <linux-imx@nxp.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: [PATCH] arm64: dts: imx8mq: Add system reset controller
Date: Tue, 15 Jan 2019 12:46:41 +0100 [thread overview]
Message-ID: <20190115114641.GA15870@bogon.m.sigxcpu.org> (raw)
We can reuse the src from fsl,imx51-src as with other imx SOCs.
Signed-off-by: Guido Günther <agx@sigxcpu.org>
---
I'm mostly interested in the syscon part to be able to use regmap for
MIPI DSI here.
Patch is against next-20190114 plus Lucas "arm64: dts: imx8mq: move
watchdog nodes to correct location" but also applies to
https://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git/log/?h=imx/dt64
It will conflict with "arm64: dts: imx8mq: add GPC power domains" which
is not yet in any tree I've seen.
arch/arm64/boot/dts/freescale/imx8mq.dtsi | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/arch/arm64/boot/dts/freescale/imx8mq.dtsi b/arch/arm64/boot/dts/freescale/imx8mq.dtsi
index 0225eae2216e..7b1e0bdbd932 100644
--- a/arch/arm64/boot/dts/freescale/imx8mq.dtsi
+++ b/arch/arm64/boot/dts/freescale/imx8mq.dtsi
@@ -252,6 +252,13 @@
"clk_ext1", "clk_ext2",
"clk_ext3", "clk_ext4";
};
+
+ src: src@30390000 {
+ compatible = "fsl,imx8mq-src", "fsl,imx51-src", "syscon";
+ reg = <0x30390000 0x10000>;
+ interrupts = <GIC_SPI 89 IRQ_TYPE_LEVEL_HIGH>;
+ #reset-cells = <1>;
+ };
};
bus@30400000 { /* AIPS2 */
--
2.20.1
next reply other threads:[~2019-01-15 11:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 11:46 Guido Günther [this message]
2019-01-15 11:51 ` [PATCH] arm64: dts: imx8mq: Add system reset controller Lucas Stach
2019-01-15 12:35 ` Guido Günther
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=20190115114641.GA15870@bogon.m.sigxcpu.org \
--to=agx@sigxcpu.org \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--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).