devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@somainline.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: soc: qcom: YAML-ify SSBI bindings
Date: Sat, 1 Oct 2022 11:43:33 +0200	[thread overview]
Message-ID: <d1a26c97-75db-5d09-4c4f-77ed4fed1683@linaro.org> (raw)
In-Reply-To: <20220930212052.894834-1-dmitry.baryshkov@linaro.org>

On 30/09/2022 23:20, Dmitry Baryshkov wrote:
> Convert arm/msm/ssbi.txt yo YAML, moving it to the directory with SoC
> bindings (soc/qcom/).

I think this should go to "bus" instead. Actually we could put there as
well GSBI and few others...

> 
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
>  .../devicetree/bindings/arm/msm/ssbi.txt      | 18 ------
>  .../bindings/soc/qcom/qcom,ssbi.yaml          | 63 +++++++++++++++++++
>  2 files changed, 63 insertions(+), 18 deletions(-)
>  delete mode 100644 Documentation/devicetree/bindings/arm/msm/ssbi.txt
>  create mode 100644 Documentation/devicetree/bindings/soc/qcom/qcom,ssbi.yaml
> 
> diff --git a/Documentation/devicetree/bindings/arm/msm/ssbi.txt b/Documentation/devicetree/bindings/arm/msm/ssbi.txt
> deleted file mode 100644
> index 54fd5ced3401..000000000000
> --- a/Documentation/devicetree/bindings/arm/msm/ssbi.txt
> +++ /dev/null
> @@ -1,18 +0,0 @@
> -* Qualcomm SSBI
> -
> -Some Qualcomm MSM devices contain a point-to-point serial bus used to
> -communicate with a limited range of devices (mostly power management
> -chips).
> -
> -These require the following properties:
> -
> -- compatible: "qcom,ssbi"
> -
> -- qcom,controller-type
> -  indicates the SSBI bus variant the controller should use to talk
> -  with the slave device.  This should be one of "ssbi", "ssbi2", or
> -  "pmic-arbiter".  The type chosen is determined by the attached
> -  slave.
> -
> -The slave device should be the single child node of the ssbi device
> -with a compatible field.
> diff --git a/Documentation/devicetree/bindings/soc/qcom/qcom,ssbi.yaml b/Documentation/devicetree/bindings/soc/qcom/qcom,ssbi.yaml
> new file mode 100644
> index 000000000000..6154f7222899
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/soc/qcom/qcom,ssbi.yaml
> @@ -0,0 +1,63 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: "http://devicetree.org/schemas/soc/qcom/qcom,ssbi.yaml#"
> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"

Drop quotes from both above.

> +
> +title: Qualcomm Single-wire Serial Bus Interface (SSBI)
> +
> +description:
> +  Some Qualcomm MSM devices contain a point-to-point serial bus used to
> +  communicate with a limited range of devices (mostly power management
> +  chips).
> +
> +maintainers:
> +  - Andy Gross <agross@kernel.org>
> +  - Bjorn Andersson <andersson@kernel.org>
> +
> +properties:
> +  compatible:
> +    const: qcom,ssbi
> +
> +  reg:
> +    maxItems: 1
> +
> +  qcom,controller-type:
> +    description:
> +      Indicates the SSBI bus variant the controller should use to talk
> +      with the slave device. The type chosen is determined by the attached
> +      slave.
> +    enum:
> +      - ssbi
> +      - ssbi2
> +      - pmic-arbiter
> +
> +  pmic:
> +    type: object

This is quite unspecific... Can we make it a ref to some PMICs schemas?

> +
> +required:
> +  - compatible
> +  - reg
> +  - qcom,controller-type
> +
> +additionalProperties: false
> +
> +examples:
> +  - |
> +    #include <dt-bindings/interrupt-controller/irq.h>
> +    ssbi@c00000 {
> +        compatible = "qcom,ssbi";
> +        reg = <0x00c00000 0x1000>;
> +        qcom,controller-type = "pmic-arbiter";
> +
> +        pmic {
> +            compatible = "qcom,pm8821";
> +            interrupt-parent = <&msmgpio>;
> +            interrupts = <76 IRQ_TYPE_LEVEL_LOW>;
> +            #interrupt-cells = <2>;
> +            interrupt-controller;
> +            #address-cells = <1>;
> +            #size-cells = <0>;
> +        };
> +    };
> +...

Best regards,
Krzysztof


  parent reply	other threads:[~2022-10-01  9:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-30 21:20 [PATCH 1/2] dt-bindings: soc: qcom: YAML-ify SSBI bindings Dmitry Baryshkov
2022-09-30 21:20 ` [PATCH 2/2] ARM: dts: qcom: mdm9615: drop unit ids from PMIC nodes Dmitry Baryshkov
2022-10-01  9:40   ` Krzysztof Kozlowski
2022-10-02 13:20     ` Dmitry Baryshkov
2022-10-03  6:46       ` Krzysztof Kozlowski
2022-10-01  9:43 ` Krzysztof Kozlowski [this message]
2022-10-02 13:46   ` [PATCH 1/2] dt-bindings: soc: qcom: YAML-ify SSBI bindings Dmitry Baryshkov
2022-10-03  6:46     ` Krzysztof Kozlowski
2022-10-03 17:17       ` Rob Herring
2022-10-03 17:32         ` Krzysztof Kozlowski
2022-10-03 21:28           ` Dmitry Baryshkov
2022-10-03 13:24 ` Rob Herring
2022-10-03 17:18 ` Rob Herring
2022-11-08  1:27 ` (subset) " Bjorn Andersson

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=d1a26c97-75db-5d09-4c4f-77ed4fed1683@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=konrad.dybcio@somainline.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@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;
as well as URLs for NNTP newsgroup(s).