linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Sumit Semwal <sumit.semwal@linaro.org>
Cc: agross@kernel.org, bjorn.andersson@linaro.org,
	lgirdwood@gmail.com, broonie@kernel.org,
	nishakumari@codeaurora.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	kgunda@codeaurora.org, rnayak@codeaurora.org
Subject: Re: [PATCH v4 2/5] dt-bindings: regulator: Add labibb regulator
Date: Tue, 9 Jun 2020 16:52:37 -0600	[thread overview]
Message-ID: <20200609225237.GA1647191@bogus> (raw)
In-Reply-To: <20200602100924.26256-3-sumit.semwal@linaro.org>

On Tue, Jun 02, 2020 at 03:39:21PM +0530, Sumit Semwal wrote:
> From: Nisha Kumari <nishakumari@codeaurora.org>
> 
> Adding the devicetree binding for labibb regulator.
> 
> Signed-off-by: Nisha Kumari <nishakumari@codeaurora.org>
> Signed-off-by: Sumit Semwal <sumit.semwal@linaro.org>
>  [sumits: cleanup as per review comments and update to yaml]
> --
> v2: updated for better compatible string and names.
> v3: moved to yaml
> v4: fixed dt_binding_check issues
> ---
>  .../regulator/qcom-labibb-regulator.yaml      | 79 +++++++++++++++++++
>  1 file changed, 79 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/regulator/qcom-labibb-regulator.yaml
> 
> diff --git a/Documentation/devicetree/bindings/regulator/qcom-labibb-regulator.yaml b/Documentation/devicetree/bindings/regulator/qcom-labibb-regulator.yaml
> new file mode 100644
> index 000000000000..178820ec04c7
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/regulator/qcom-labibb-regulator.yaml
> @@ -0,0 +1,79 @@
> +# SPDX-License-Identifier: GPL-2.0-only

Dual license new bindings:

(GPL-2.0-only OR BSD-2-Clause)

> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/regulator/qcom-labibb-regulator.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Qualcomm's LAB(LCD AMOLED Boost)/IBB(Inverting Buck Boost) Regulator
> +
> +maintainers:
> +  - Sumit Semwal <sumit.semwal@linaro.org>
> +
> +description:
> +  LAB can be used as a positive boost power supply and IBB can be used as a
> +  negative boost power supply for display panels. Currently implemented for
> +  pmi8998.
> +
> +allOf:
> +  - $ref: "regulator.yaml#"

I think you want this under each child as this schema applies to each 
regulator. But you aren't using any of the regulator properties, so not 
even needed? Or the example is not complete?

> +
> +properties:
> +  compatible:
> +    const: qcom,pmi8998-lab-ibb
> +
> +  lab:
> +    type: object
> +
> +    properties:
> +
> +      interrupts:
> +        maxItems: 1
> +        description:
> +          Short-circuit interrupt for lab.
> +
> +      interrupt-names:
> +        const: sc-err

You don't really need a name if there's only 1.

> +
> +    required:
> +    - interrupts
> +    - interrupt-names
> +
> +  ibb:
> +    type: object
> +
> +    properties:
> +
> +      interrupts:
> +        maxItems: 1
> +        description:
> +          Short-circuit interrupt for lab.
> +
> +      interrupt-names:
> +        const: sc-err
> +
> +    required:
> +    - interrupts
> +    - interrupt-names
> +
> +required:
> +  - compatible

unevaluatedProperties: false

> +
> +examples:
> +  - |
> +    #include <dt-bindings/interrupt-controller/irq.h>
> +
> +    labibb {
> +      compatible = "qcom,pmi8998-lab-ibb";
> +
> +      lab {
> +        interrupts = <0x3 0x0 IRQ_TYPE_EDGE_RISING>;
> +        interrupt-names = "sc-err";
> +      };
> +
> +      ibb {
> +        interrupts = <0x3 0x2 IRQ_TYPE_EDGE_RISING>;
> +        interrupt-names = "sc-err";
> +      };
> +    };
> +
> +...
> -- 
> 2.26.2
> 

  reply	other threads:[~2020-06-09 22:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-02 10:09 [PATCH v4 0/5] Qualcomm labibb regulator driver Sumit Semwal
2020-06-02 10:09 ` [PATCH v4 1/5] regulator: Allow regulators to verify enabled during enable() Sumit Semwal
2020-06-02 11:24   ` Mark Brown
2020-06-02 11:57     ` Sumit Semwal
2020-06-18 23:44   ` Bjorn Andersson
2020-06-02 10:09 ` [PATCH v4 2/5] dt-bindings: regulator: Add labibb regulator Sumit Semwal
2020-06-09 22:52   ` Rob Herring [this message]
2020-06-02 10:09 ` [PATCH v4 3/5] arm64: dts: qcom: pmi8998: Add nodes for LAB and IBB regulators Sumit Semwal
2020-06-02 10:09 ` [PATCH v4 4/5] regulator: qcom: Add labibb driver Sumit Semwal
2020-06-02 11:32   ` Mark Brown
2020-06-02 12:10     ` Sumit Semwal
2020-06-02 12:25       ` Mark Brown
2020-06-17 11:42         ` Sumit Semwal
2020-06-17 11:47           ` Mark Brown
2020-06-17 11:57             ` Sumit Semwal
2020-06-17 12:06               ` Mark Brown
2020-06-17 12:09                 ` Sumit Semwal
2020-06-17 12:40                   ` Mark Brown
2020-06-02 10:09 ` [PATCH v4 5/5] regulator: qcom: labibb: Add SC interrupt handling Sumit Semwal
2020-06-02 12:22   ` Mark Brown
2020-06-17 12:06     ` Sumit Semwal
2020-06-17 12:38       ` Mark Brown

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=20200609225237.GA1647191@bogus \
    --to=robh@kernel.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kgunda@codeaurora.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nishakumari@codeaurora.org \
    --cc=rnayak@codeaurora.org \
    --cc=sumit.semwal@linaro.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).