From: "Mårten Lindahl" <martenli@axis.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<kernel@axis.com>
Subject: Re: [PATCH v2 1/2] regulator: Add bindings for TPS6287x
Date: Fri, 5 May 2023 13:03:30 +0200 [thread overview]
Message-ID: <56979ac8-f27a-801a-dca3-3e1ff63bb005@axis.com> (raw)
In-Reply-To: <1f62d6dd-1ab8-a8e8-c881-da03ad9bfbd9@linaro.org>
On 5/4/23 17:11, Krzysztof Kozlowski wrote:
> On 04/05/2023 17:08, Mårten Lindahl wrote:
>> Hi Krzysztof!
>>
>> On 5/4/23 11:34, Krzysztof Kozlowski wrote:
>>> On 04/05/2023 10:30, Mårten Lindahl wrote:
>>>> Add bindings for the TPS62870/TPS62871/TPS62872/TPS62873 voltage
>>>> regulators.
>>>>
>>> Use subject prefixes matching the subsystem (which you can get for
>>> example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory
>>> your patch is touching).
>>>
>>> Just a hint - I in general ignore all the emails without dt-bindings prefix.
>> Ok, I'll prefix it "dt-bindings: regulator:"
> You got command to run, so run it. This semi-automated response is made
> longer for the purpose to help you, not to be quickly scrolled and
> ignored. When you run it you will see the order is opposite, regulator
> followed by dt-bindings.
>
> You can apply such habit for other subsystems where maintainers also
> expect certain prefixes.
Hi! Sorry, I did run the command and followed the latest commit I could
see (1ba7dfb905b3) as the result is mixed with prefixes.
But I will of course do as you request: "regulator: dt-bindings: ".
>
>
>>>> Signed-off-by: Mårten Lindahl <marten.lindahl@axis.com>
>>>> ---
>>>> .../devicetree/bindings/regulator/ti,tps62870.yaml | 62 ++++++++++++++++++++++
>>>> 1 file changed, 62 insertions(+)
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/regulator/ti,tps62870.yaml b/Documentation/devicetree/bindings/regulator/ti,tps62870.yaml
>>>> new file mode 100644
>>>> index 000000000000..32f259f16314
>>>> --- /dev/null
>>>> +++ b/Documentation/devicetree/bindings/regulator/ti,tps62870.yaml
>>>> @@ -0,0 +1,62 @@
>>>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>>>> +%YAML 1.2
>>>> +---
>>>> +$id: http://devicetree.org/schemas/regulator/ti,tps62870.yaml#
>>>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>>>> +
>>>> +title: TI TPS62870/TPS62871/TPS62872/TPS62873 voltage regulator
>>>> +
>>>> +maintainers:
>>>> + - Mårten Lindahl <marten.lindahl@axis.com>
>>>> +
>>>> +properties:
>>>> + compatible:
>>>> + enum:
>>>> + - ti,tps62870
>>>> + - ti,tps62871
>>>> + - ti,tps62872
>>>> + - ti,tps62873
>>>> +
>>>> + reg:
>>>> + maxItems: 1
>>>> +
>>>> + regulators:
>>>> + type: object
>>>> +
>>>> + properties:
>>>> + "vout":
>>> Drop quotes.
>>>
>>> Why do you need entire "regulators" node for one regulator? Why do you
>>> need child at first place. Drop it entirely.
>> I will remove the regulators node. I think the vout node is needed to
>> get the of_get_regulator_init_data.
> Hmmm, how other simple regulators deal with it? Like all the fixed ones
> and few other one-regulator-devices?
Ok, I added of_get_regulator_init_data to the driver probe and then it
works fine. I'll drop the child node.
Thanks!
Kind regards
Mårten
>
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2023-05-05 11:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 8:30 [PATCH v2 0/2] regulator: Add support " Mårten Lindahl
2023-05-04 8:30 ` [PATCH v2 1/2] regulator: Add bindings " Mårten Lindahl
2023-05-04 9:34 ` Krzysztof Kozlowski
2023-05-04 15:08 ` Mårten Lindahl
2023-05-04 15:11 ` Krzysztof Kozlowski
2023-05-05 11:03 ` Mårten Lindahl [this message]
2023-05-04 8:30 ` [PATCH v2 2/2] regulator: Add support for TI TPS6287x regulators Mårten Lindahl
2023-05-04 12:04 ` Mark Brown
2023-05-05 8:29 ` Mårten Lindahl
[not found] ` <e02589b8-118d-0feb-d32a-bdf39d1b88f6@axis.com>
2023-05-05 11:52 ` Mark Brown
2023-05-08 6:51 ` Mårten Lindahl
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=56979ac8-f27a-801a-dca3-3e1ff63bb005@axis.com \
--to=martenli@axis.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@axis.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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
all inboxes | Powered by JetHome®