[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <45d66377-20d8-4b16-9b5c-490d9afc41ed@kernel.org>
Date: Thu, 20 Jun 2024 18:16:50 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Jiaxun Yang <jiaxun.yang@...goat.com>, Lee Jones <lee@...nel.org>,
Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
"paulburton@...nel.org" <paulburton@...nel.org>,
Thomas Bogendoerfer <tsbogend@...ha.franken.de>
Cc: devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
"linux-mips@...r.kernel.org" <linux-mips@...r.kernel.org>
Subject: Re: [PATCH v3 7/8] dt-bindings: mfd: Add img,boston-platform-regs
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
Powered by blists - more mailing lists