From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Mårten Lindahl" <marten.lindahl@axis.com>,
"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: Thu, 4 May 2023 11:34:28 +0200 [thread overview]
Message-ID: <dfd3498c-62ab-92d3-22d6-21729dc619fa@linaro.org> (raw)
In-Reply-To: <20230502-tps6287x-driver-v2-1-fb5419d46c49@axis.com>
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.
> 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.
> + type: object
> + $ref: regulator.yaml#
> + unevaluatedProperties: false
You missed that piece of explanation:
"The set of possible operating modes depends on the capabilities of
every hardware so each device binding documentation explains which
values the regulator supports."
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-05-04 9:34 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 [this message]
2023-05-04 15:08 ` Mårten Lindahl
2023-05-04 15:11 ` Krzysztof Kozlowski
2023-05-05 11:03 ` Mårten Lindahl
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=dfd3498c-62ab-92d3-22d6-21729dc619fa@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@axis.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marten.lindahl@axis.com \
--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®