[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <99f0fcb4-7c45-426a-8176-8191a032c0f0@kernel.org>
Date: Mon, 13 May 2024 11:02:53 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Laurentiu Mihalcea <laurentiumihalcea111@...il.com>,
Rob Herring <robh@...nel.org>
Cc: Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
Fabio Estevam <festevam@...il.com>, Daniel Baluta <daniel.baluta@....com>,
Shengjiu Wang <shengjiu.wang@....com>, Liu Ying <victor.liu@....com>,
Laurentiu Mihalcea <laurentiu.mihalcea@....com>, devicetree@...r.kernel.org,
imx@...ts.linux.dev, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 2/3] dt-bindings: mfd: add schema for 8ulp AVD-SIM
On 09/05/2024 20:48, Laurentiu Mihalcea wrote:
>>> +
>>> + reg:
>>> + maxItems: 1
>>> +
>>> + clocks:
>>> + maxItems: 1
>> If you do add child nodes, 'simple-mfd' also means there is not any
>> dependency on the parent node such as needing this clock to be enabled
>> for the child nodes.
>>
>> Rob
>
> The plan was to add the children later on as required.
> Given the children would in fact depend on the parent's clock being
> enabled, I wonder if just removing 'simple-mfd' from the compatible
> list would do the trick?
Dropping simple-mfd would be a requirement in such case, but not
sufficient. Please send complete bindings, so with the children.
Best regards,
Krzysztof
Powered by blists - more mailing lists