From: Jiaxun Yang <jiaxun.yang@flygoat.com>
To: Lee Jones <lee@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Burton <paulburton@kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mips@vger.kernel.org,
Jiaxun Yang <jiaxun.yang@flygoat.com>
Subject: [PATCH 2/2] MIPS: dts: Boston: Add simple-mfd compatible
Date: Mon, 13 May 2024 19:58:15 +0100 [thread overview]
Message-ID: <20240513-boston-syscon-v1-2-93ff557d3548@flygoat.com> (raw)
In-Reply-To: <20240513-boston-syscon-v1-0-93ff557d3548@flygoat.com>
We certainly want subnodes of system-controller node to
be populated, add simple-mfd compatible to make that happen.
Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
---
arch/mips/boot/dts/img/boston.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/mips/boot/dts/img/boston.dts b/arch/mips/boot/dts/img/boston.dts
index 72f7605d2e31..f7a2c46f1eb8 100644
--- a/arch/mips/boot/dts/img/boston.dts
+++ b/arch/mips/boot/dts/img/boston.dts
@@ -203,7 +203,7 @@ cpc@16200000 {
};
plat_regs: system-controller@17ffd000 {
- compatible = "img,boston-platform-regs", "syscon";
+ compatible = "img,boston-platform-regs", "syscon", "simple-mfd";
reg = <0x17ffd000 0x1000>;
clk_boston: clock {
--
2.34.1
prev parent reply other threads:[~2024-05-13 18:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 18:58 [PATCH 0/2] MIPS: Boston: Fix syscon devicetree binding and node Jiaxun Yang
2024-05-13 18:58 ` [PATCH 1/2] dt-bindings: mfd: syscon: Add img,boston-platform-regs Jiaxun Yang
2024-05-14 9:08 ` Krzysztof Kozlowski
2024-05-14 9:11 ` Krzysztof Kozlowski
2024-05-15 21:44 ` Jiaxun Yang
2024-05-17 8:58 ` Krzysztof Kozlowski
2024-05-17 10:15 ` Jiaxun Yang
2024-05-18 19:26 ` Krzysztof Kozlowski
2024-05-13 18:58 ` Jiaxun Yang [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=20240513-boston-syscon-v1-2-93ff557d3548@flygoat.com \
--to=jiaxun.yang@flygoat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paulburton@kernel.org \
--cc=robh@kernel.org \
--cc=tsbogend@alpha.franken.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).