From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>, Lee Jones <lee@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"paulburton@kernel.org" <paulburton@kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>
Subject: Re: [PATCH v3 7/8] dt-bindings: mfd: Add img,boston-platform-regs
Date: Thu, 20 Jun 2024 18:16:50 +0200 [thread overview]
Message-ID: <45d66377-20d8-4b16-9b5c-490d9afc41ed@kernel.org> (raw)
In-Reply-To: <be608e3e-2ecd-4d7d-bf45-99c553e72c08@app.fastmail.com>
On 20/06/2024 18:13, Jiaxun Yang wrote:
>
>
> 在2024年6月20日六月 上午7:40，Krzysztof Kozlowski写道：
>> On 19/06/2024 13:20, Jiaxun Yang wrote:
>>>
>>>
>>> 在2024年6月19日六月 上午10:28，Krzysztof Kozlowski写道：
> [...]
>> Your children depend on parent to provide IO address, so this is not
>> simple-mfd. Rule for simple-mfd is that children do not rely on parent
>> at all.
>
> I don't really get this.
>
> As per syscon-rebbot.yaml:
>
> The SYSCON registers map is normally retrieved from the
> parental dt-node. So the SYSCON reboot node should be represented as a
> sub-node of a "syscon", "simple-mfd" node.
>
> syscon-reboot is certainly using parent node to provide I/O address,
> even regmap property is deprecated. Without "simple-mfd", reboot node
> won't be populated at all.
That's why I asked you to populate children.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-06-20 16:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 15:11 [PATCH v3 0/8] MIPS: Boston: Fix syscon devicetree binding and node Jiaxun Yang
2024-06-18 15:11 ` [PATCH v3 1/8] MIPS: dts: Boston: Add simple-mfd compatible for syscon Jiaxun Yang
2024-06-18 15:11 ` [PATCH v3 2/8] MIPS: dts: Boston: Move syscon-reboot node under syscon Jiaxun Yang
2024-06-18 15:11 ` [PATCH v3 3/8] MIPS: dts: Boston: Rename clock node as clock-controller Jiaxun Yang
2024-06-18 15:11 ` [PATCH v3 4/8] MIPS: dts: Boston: Remove unused #interrupt-cells Jiaxun Yang
2024-06-18 15:11 ` [PATCH v3 5/8] MIPS: dts: Boston: Add model property Jiaxun Yang
2024-06-18 15:11 ` [PATCH v3 6/8] MIPS: dts: Boston: Rename uart node Jiaxun Yang
2024-06-18 15:11 ` [PATCH v3 7/8] dt-bindings: mfd: Add img,boston-platform-regs Jiaxun Yang
2024-06-19 9:28 ` Krzysztof Kozlowski
2024-06-19 11:20 ` Jiaxun Yang
2024-06-20 6:40 ` Krzysztof Kozlowski
2024-06-20 16:13 ` Jiaxun Yang
2024-06-20 16:16 ` Krzysztof Kozlowski [this message]
2024-06-20 16:32 ` Jiaxun Yang
2024-06-21 15:51 ` Jiaxun Yang
2024-06-22 18:12 ` Krzysztof Kozlowski
2024-06-22 19:06 ` Jiaxun Yang
2024-06-27 20:44 ` Rob Herring
2024-06-18 15:11 ` [PATCH v3 8/8] dt-bindings: mips: img: Add devices binding Jiaxun Yang
2024-06-20 6:43 ` Krzysztof Kozlowski
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=45d66377-20d8-4b16-9b5c-490d9afc41ed@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jiaxun.yang@flygoat.com \
--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 NNTP newsgroup(s).