devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Lee Jones <lee@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: mfd: Explain lack of child dependency in simple-mfd
Date: Sun, 23 Jun 2024 09:21:23 +0200	[thread overview]
Message-ID: <b078d8de-78f4-4125-8971-d76f354c7b30@linaro.org> (raw)
In-Reply-To: <20240621111000.GN1318296@google.com>

On 21/06/2024 13:10, Lee Jones wrote:
> On Thu, 20 Jun 2024, Krzysztof Kozlowski wrote:
> 
>> On 20/06/2024 19:17, Lee Jones wrote:
>>> On Sun, 16 Jun 2024, Krzysztof Kozlowski wrote:
>>>
>>>> Common mistake of usage of 'simple-mfd' compatible is a dependency of
>>>> children on resources acquired and managed by the parent, e.g. clocks.
>>>> Extend the simple-mfd documentation to cover this case.
>>>>
>>>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>>>> ---
>>>>  Documentation/devicetree/bindings/mfd/mfd.txt | 13 +++++++------
>>>>  1 file changed, 7 insertions(+), 6 deletions(-)
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/mfd/mfd.txt b/Documentation/devicetree/bindings/mfd/mfd.txt
>>>> index 336c0495c8a3..98b4340b65f3 100644
>>>> --- a/Documentation/devicetree/bindings/mfd/mfd.txt
>>>> +++ b/Documentation/devicetree/bindings/mfd/mfd.txt
>>>> @@ -18,12 +18,13 @@ A typical MFD can be:
>>>>  Optional properties:
>>>>  
>>>>  - compatible : "simple-mfd" - this signifies that the operating system should
>>>> -  consider all subnodes of the MFD device as separate devices akin to how
>>>> -  "simple-bus" indicates when to see subnodes as children for a simple
>>>> -  memory-mapped bus. For more complex devices, when the nexus driver has to
>>>> -  probe registers to figure out what child devices exist etc, this should not
>>>> -  be used. In the latter case the child devices will be determined by the
>>>> -  operating system.
>>>> +  consider all subnodes of the MFD device as separate and independent devices
>>>> +  akin to how "simple-bus" indicates when to see subnodes as children for a
>>>> +  simple memory-mapped bus. "Independent devices" means that children do not
>>>
>>> I'm not against the change, but I think it can be phased better.
>>>
>>> Quoting the new part and going on to explain what you mean by it doesn't
>>> flow very well.  Are you able to massage it so it reads a little more
>>> nicely please?
>>
>> Does this feels better?
>>
>> compatible : "simple-mfd" - this signifies that the operating system
>> should consider all subnodes of the MFD device as separate and
>> independent devices, so not needing any resources to be provided by the
>> parent device. Similarly to how "simple-bus" indicates when to see
>> subnodes as children for a simple memory-mapped bus.
>>
>> For more complex devices, when the nexus driver has to probe registers
>> to figure out what child devices exist etc, this should not be used. In
>> the latter case the child devices will be determined by the operating
>> system.
> 
> Flows a lot better, yes.

Sure.

> 
> Submit it and please include the original author this time.

Everything is scripted, so you ask me for additional, manual steps just
to find the author and then Cc-them. I'll do it but it would be much
easier if the interested party added themself as reviewer or maintainer
of the binding.

> 

Best regards,
Krzysztof


  reply	other threads:[~2024-06-23  7:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-16  8:06 [PATCH] dt-bindings: mfd: Explain lack of child dependency in simple-mfd Krzysztof Kozlowski
2024-06-17 15:34 ` Conor Dooley
2024-06-20 17:17 ` Lee Jones
2024-06-20 19:42   ` Krzysztof Kozlowski
2024-06-21 11:10     ` Lee Jones
2024-06-23  7:21       ` Krzysztof Kozlowski [this message]
2024-06-24 11:10         ` Lee Jones

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=b078d8de-78f4-4125-8971-d76f354c7b30@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --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=robh@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).