From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: Chanwoo Choi <cw00.choi@samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Pavel Machek <pavel@ucw.cz>, Lee Jones <lee.jones@linaro.org>,
Sebastian Reichel <sre@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH 3/4] regulator: dt-bindings: maxim,max77693: convert to dtschema
Date: Tue, 4 Jan 2022 09:29:41 -0600 [thread overview]
Message-ID: <YdRn5cvksYXK4icV@robh.at.kernel.org> (raw)
In-Reply-To: <20211228163930.35524-4-krzysztof.kozlowski@canonical.com>
On Tue, Dec 28, 2021 at 05:39:29PM +0100, Krzysztof Kozlowski wrote:
> Convert the regulator bindings of Maxim MAX77693 MUIC to DT schema format.
> The existing bindings were defined in ../bindings/mfd/max77693.txt.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
> ---
> .../bindings/regulator/maxim,max77693.yaml | 49 +++++++++++++++++++
> 1 file changed, 49 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/regulator/maxim,max77693.yaml
>
> diff --git a/Documentation/devicetree/bindings/regulator/maxim,max77693.yaml b/Documentation/devicetree/bindings/regulator/maxim,max77693.yaml
> new file mode 100644
> index 000000000000..81242c8cd77c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/regulator/maxim,max77693.yaml
> @@ -0,0 +1,49 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/regulator/maxim,max77693.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Maxim MAX77693 MicroUSB and Companion Power Management IC regulators
> +
> +maintainers:
> + - Chanwoo Choi <cw00.choi@samsung.com>
> + - Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
> +
> +description: |
> + This is a part of device tree bindings for Maxim MAX77693 MicroUSB Integrated
> + Circuit (MUIC).
> +
> + See also Documentation/devicetree/bindings/mfd/maxim,max77693.yaml for
> + additional information and example.
> +
> +patternProperties:
> + "^ESAFEOUT[12]$":
> + type: object
> + $ref: regulator.yaml#
> + unevaluatedProperties: false
> + description: |
> + Safeout LDO regulator.
> +
> + properties:
> + regulator-min-microvolt: true
> + regulator-max-microvolt: true
If you want to define which properties are valid from regulator.yaml,
then you need to define all of them (regulator-name is missing), and use
'additionalProperties: false'. Or you can just drop these.
> +
> + required:
> + - regulator-name
> +
> + "^CHARGER$":
Fixed string, not a pattern. Place under 'properties'.
> + type: object
> + $ref: regulator.yaml#
> + unevaluatedProperties: false
> + description: |
> + Current regulator.
> +
> + properties:
> + regulator-min-microamp: true
> + regulator-max-microamp: true
> +
> + required:
> + - regulator-name
> +
> +additionalProperties: false
> --
> 2.32.0
>
>
next prev parent reply other threads:[~2022-01-04 15:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 16:39 [PATCH 0/4] leds/power/regulator/mfd: " Krzysztof Kozlowski
2021-12-28 16:39 ` [PATCH 1/4] dt-bindings: leds: " Krzysztof Kozlowski
2021-12-29 17:34 ` Rob Herring
2021-12-30 10:53 ` Krzysztof Kozlowski
2022-01-04 15:09 ` Rob Herring
2022-01-11 15:03 ` Krzysztof Kozlowski
2021-12-28 16:39 ` [PATCH 2/4] dt-bindings: power: supply: " Krzysztof Kozlowski
2022-01-10 19:08 ` Rob Herring
2021-12-28 16:39 ` [PATCH 3/4] regulator: dt-bindings: " Krzysztof Kozlowski
2022-01-04 15:29 ` Rob Herring [this message]
2022-01-11 16:26 ` Krzysztof Kozlowski
2021-12-28 16:39 ` [PATCH 4/4] dt-bindings: mfd: " Krzysztof Kozlowski
2022-01-10 19:10 ` Rob Herring
2022-01-11 16:28 ` Krzysztof Kozlowski
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=YdRn5cvksYXK4icV@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=b.zolnierkie@samsung.com \
--cc=broonie@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=sre@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
Powered by JetHome