[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9f5a7213-8a31-afed-f4aa-b45b6e277be4@linaro.org>
Date: Wed, 22 Mar 2023 09:24:51 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Zeynep Arslanbenzer <Zeynep.Arslanbenzer@...log.com>,
lee@...nel.org, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, sre@...nel.org,
lgirdwood@...il.com, broonie@...nel.org
Cc: Nurettin.Bolucu@...log.com, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, linux-pm@...r.kernel.org
Subject: Re: [PATCH v2 1/8] dt-bindings: regulator: max77658: Add ADI
MAX77643/54/58/59 Regulator
On 22/03/2023 06:56, Zeynep Arslanbenzer wrote:
> Add ADI MAX77643/MAX77654/MAX77658/MAX77659 Regulator devicetree document.
>
> Signed-off-by: Nurettin Bolucu <Nurettin.Bolucu@...log.com>
> Signed-off-by: Zeynep Arslanbenzer <Zeynep.Arslanbenzer@...log.com>
> ---
> .../regulator/adi,max77658-regulator.yaml | 32 +++++++++++++++++++
> 1 file changed, 32 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/regulator/adi,max77658-regulator.yaml
>
> diff --git a/Documentation/devicetree/bindings/regulator/adi,max77658-regulator.yaml b/Documentation/devicetree/bindings/regulator/adi,max77658-regulator.yaml
> new file mode 100644
> index 000000000000..1d097eddcd98
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/regulator/adi,max77658-regulator.yaml
> @@ -0,0 +1,32 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/regulator/adi,max77658-regulator.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Regulator for MAX77658 PMICs family from ADI
> +
> +maintainers:
> + - Nurettin Bolucu <Nurettin.Bolucu@...log.com>
> + - Zeynep Arslanbenzer <Zeynep.Arslanbenzer@...log.com>
> +
> +description: |
> + This is part of the MAX77658 MFD device. For more details
> + see Documentation/devicetree/bindings/mfd/adi,max77658.yaml.
> +
> + The regulators is represented as a sub-node of the PMIC node on the device tree.
There is no select/compatible here, so this makes little sense as
separate binding. Make it part of parent schema instead.
Best regards,
Krzysztof
Powered by blists - more mailing lists