linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: peng.fan@nxp.com
To: shawnguo@kernel.org, s.hauer@pengutronix.de, festevam@gmail.com,
	robh+dt@kernel.org
Cc: kernel@pengutronix.de, linux-imx@nxp.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	krzk@kernel.org, Peng Fan <peng.fan@nxp.com>
Subject: [PATCH 3/4] arm64: dts: imx8mn: add spba bus node
Date: Tue, 29 Dec 2020 20:00:44 +0800	[thread overview]
Message-ID: <1609243245-9671-4-git-send-email-peng.fan@nxp.com> (raw)
In-Reply-To: <1609243245-9671-1-git-send-email-peng.fan@nxp.com>

From: Peng Fan <peng.fan@nxp.com>

According to RM, there is a spba bus inside aips3 and aips1, add it.

Signed-off-by: Peng Fan <peng.fan@nxp.com>
---
 arch/arm64/boot/dts/freescale/imx8mn.dtsi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm64/boot/dts/freescale/imx8mn.dtsi b/arch/arm64/boot/dts/freescale/imx8mn.dtsi
index 73602832ccaa..033fa90570ff 100644
--- a/arch/arm64/boot/dts/freescale/imx8mn.dtsi
+++ b/arch/arm64/boot/dts/freescale/imx8mn.dtsi
@@ -749,7 +749,7 @@ uart2: serial@30890000 {
 					clock-names = "ipg", "per";
 					status = "disabled";
 				};
-			}
+			};
 
 			crypto: crypto@30900000 {
 				compatible = "fsl,sec-v4.0";
-- 
2.28.0


  parent reply	other threads:[~2020-12-29 12:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-29 12:00 [PATCH 0/4] arm64: dts: imx8m: add spda bus peng.fan
2020-12-29 12:00 ` [PATCH 1/4] arm64: dts: imx8mn: add spba bus node of aips3 peng.fan
2020-12-29 12:00 ` [PATCH 2/4] arm64: dts: imx8mn: add spba bus node peng.fan
2020-12-29 12:26   ` Adam Ford
2020-12-29 16:12     ` Krzysztof Kozlowski
2020-12-30  2:34       ` Peng Fan
2021-03-31 18:23         ` Adam Ford
2020-12-29 12:00 ` peng.fan [this message]
2020-12-29 16:13   ` [PATCH 3/4] " Krzysztof Kozlowski
2020-12-30  2:32     ` Peng Fan
2020-12-29 12:00 ` [PATCH 4/4] arm64: dts: imx8mq: " peng.fan

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=1609243245-9671-4-git-send-email-peng.fan@nxp.com \
    --to=peng.fan@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).