devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kuldeep Singh <singh.kuldeep87k@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Mark Brown <broonie@kernel.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org
Subject: Re: [PATCH v2 2/2] dt-bindings: qcom: qcom,geni-se: refer to dtschema for SPI
Date: Fri, 1 Apr 2022 19:27:25 +0530	[thread overview]
Message-ID: <20220401135725.GA40356@9a2d8922b8f1> (raw)
In-Reply-To: <20220331160248.716234-2-krzysztof.kozlowski@linaro.org>

On Thu, Mar 31, 2022 at 06:02:48PM +0200, Krzysztof Kozlowski wrote:
> After adding DT schema for the SPI controller, the Qualcomm GENI Serial
> Engine QUP Wrapper Controller bindings can reference it directly for
> full schema validation.
> 
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>

Reviewed-by: Kuldeep Singh <singh.kuldeep87k@gmail.com>

> 
> ---
> 
> Changes since v1:
> 1. None
> 
> Patch depends on previous patch (DT schema conversion).
> ---
>  .../bindings/soc/qcom/qcom,geni-se.yaml       | 22 +------------------
>  1 file changed, 1 insertion(+), 21 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/soc/qcom/qcom,geni-se.yaml b/Documentation/devicetree/bindings/soc/qcom/qcom,geni-se.yaml
> index 690ce6a355de..1bc12b6a7e01 100644
> --- a/Documentation/devicetree/bindings/soc/qcom/qcom,geni-se.yaml
> +++ b/Documentation/devicetree/bindings/soc/qcom/qcom,geni-se.yaml
> @@ -103,27 +103,7 @@ patternProperties:
>                   supports up to 50MHz, up to four chip selects, programmable
>                   data path from 4 bits to 32 bits and numerous protocol
>                   variants.
> -    $ref: /spi/spi-controller.yaml#
> -
> -    properties:
> -      compatible:
> -        enum:
> -          - qcom,geni-spi
> -
> -      interrupts:
> -        maxItems: 1
> -
> -      "#address-cells":
> -        const: 1
> -
> -      "#size-cells":
> -        const: 0
> -
> -    required:
> -      - compatible
> -      - interrupts
> -      - "#address-cells"
> -      - "#size-cells"
> +    $ref: /schemas/spi/qcom,spi-geni-qcom.yaml#
>  
>    "i2c@[0-9a-f]+$":
>      type: object
> -- 
> 2.32.0
> 

  reply	other threads:[~2022-04-01 13:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-31 16:02 [PATCH v2 1/2] spi: dt-bindings: qcom,spi-geni-qcom: convert to dtschema Krzysztof Kozlowski
2022-03-31 16:02 ` [PATCH v2 2/2] dt-bindings: qcom: qcom,geni-se: refer to dtschema for SPI Krzysztof Kozlowski
2022-04-01 13:57   ` Kuldeep Singh [this message]
2022-03-31 17:58 ` [PATCH v2 1/2] spi: dt-bindings: qcom,spi-geni-qcom: convert to dtschema Kuldeep Singh
2022-03-31 19:40   ` Krzysztof Kozlowski
2022-04-01 13:52     ` Kuldeep Singh
2022-04-01 14: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=20220401135725.GA40356@9a2d8922b8f1 \
    --to=singh.kuldeep87k@gmail.com \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@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).