linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Kanak Shilledar <kanakshilledar@gmail.com>
Cc: Kanak Shilledar <kanakshilledar111@protonmail.com>,
	Mark Brown <broonie@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Florian Fainelli <florian.fainelli@broadcom.com>,
	Ray Jui <rjui@broadcom.com>,
	Scott Branden <sbranden@broadcom.com>,
	Broadcom internal kernel review list
	<bcm-kernel-feedback-list@broadcom.com>,
	Stefan Wahren <wahrenst@gmx.net>,
	linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
	linux-rpi-kernel@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RESEND v3] dt-bindings: spi: brcm,bcm2835-spi: convert to dtschema
Date: Mon, 3 Jun 2024 08:41:21 -0500	[thread overview]
Message-ID: <20240603134121.GA168897-robh@kernel.org> (raw)
In-Reply-To: <20240531122941.3524-1-kanakshilledar111@protonmail.com>

On Fri, May 31, 2024 at 05:59:37PM +0530, Kanak Shilledar wrote:
> From: Kanak Shilledar <kanakshilledar@gmail.com>
> 
> Convert the Broadcom BCM2835 SPI0 controller to newer DT
> schema. Created DT schema based on the .txt file which had
> `comaptible`, `reg`, `interrupts`, `clocks` as required
> properties.
> Added GPL-2.0 OR BSD-2-Clause License
> 
> Signed-off-by: Kanak Shilledar <kanakshilledar111@protonmail.com>

You forgot Conor's Reviewed-by tag.

> ---
> Changes in v3:
> - Updated DCO email address
> Changes in v2:
> - Updated the maintainers
> ---
>  .../bindings/spi/brcm,bcm2835-spi.txt         | 23 ---------
>  .../bindings/spi/brcm,bcm2835-spi.yaml        | 50 +++++++++++++++++++
>  2 files changed, 50 insertions(+), 23 deletions(-)
>  delete mode 100644 Documentation/devicetree/bindings/spi/brcm,bcm2835-spi.txt
>  create mode 100644 Documentation/devicetree/bindings/spi/brcm,bcm2835-spi.yaml
> 
> diff --git a/Documentation/devicetree/bindings/spi/brcm,bcm2835-spi.txt b/Documentation/devicetree/bindings/spi/brcm,bcm2835-spi.txt
> deleted file mode 100644
> index 3d55dd64b1be..000000000000
> --- a/Documentation/devicetree/bindings/spi/brcm,bcm2835-spi.txt
> +++ /dev/null
> @@ -1,23 +0,0 @@
> -Broadcom BCM2835 SPI0 controller
> -
> -The BCM2835 contains two forms of SPI master controller, one known simply as
> -SPI0, and the other known as the "Universal SPI Master"; part of the
> -auxiliary block. This binding applies to the SPI0 controller.
> -
> -Required properties:
> -- compatible: Should be one of "brcm,bcm2835-spi" for BCM2835/2836/2837 or
> -  "brcm,bcm2711-spi" for BCM2711 or "brcm,bcm7211-spi" for BCM7211.
> -- reg: Should contain register location and length.
> -- interrupts: Should contain interrupt.
> -- clocks: The clock feeding the SPI controller.
> -
> -Example:
> -
> -spi@20204000 {
> -	compatible = "brcm,bcm2835-spi";
> -	reg = <0x7e204000 0x1000>;
> -	interrupts = <2 22>;
> -	clocks = <&clk_spi>;
> -	#address-cells = <1>;
> -	#size-cells = <0>;
> -};
> diff --git a/Documentation/devicetree/bindings/spi/brcm,bcm2835-spi.yaml b/Documentation/devicetree/bindings/spi/brcm,bcm2835-spi.yaml
> new file mode 100644
> index 000000000000..94da68792194
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/spi/brcm,bcm2835-spi.yaml
> @@ -0,0 +1,50 @@
> +# SPDX-License-Identifier: GPL-2.0 OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/spi/brcm,bcm2835-spi.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Broadcom BCM2835 SPI0 controller
> +
> +maintainers:
> +  - Florian Fainelli <florian.fainelli@broadcom.com>
> +  - Kanak Shilledar <kanakshilledar111@protonmail.com>
> +  - Stefan Wahren <wahrenst@gmx.net>
> +
> +allOf:
> +  - $ref: spi-controller.yaml#
> +
> +properties:
> +  compatible:
> +    enum:
> +      - brcm,bcm2835-spi
> +      - brcm,bcm2711-spi
> +      - brcm,bcm7211-spi
> +
> +  reg:
> +    maxItems: 1
> +
> +  interrupts:
> +    maxItems: 1
> +
> +  clocks:
> +    maxItems: 1
> +
> +required:
> +  - compatible
> +  - reg
> +  - interrupts
> +  - clocks
> +
> +unevaluatedProperties: false
> +
> +examples:
> +  - |
> +    spi@20204000 {
> +        compatible = "brcm,bcm2835-spi";
> +        reg = <0x7e204000 0x1000>;
> +        interrupts = <2 22>;
> +        clocks = <&clk_spi>;
> +        #address-cells = <1>;
> +        #size-cells = <0>;
> +    };
> -- 
> 2.34.1
> 

  reply	other threads:[~2024-06-03 13:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-31 12:29 [RESEND v3] dt-bindings: spi: brcm,bcm2835-spi: convert to dtschema Kanak Shilledar
2024-06-03 13:41 ` Rob Herring [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-03 17:30 Kanak Shilledar
2024-06-03 17:34 ` Mark Brown
2024-06-04  7:29 ` Florian Fainelli

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=20240603134121.GA168897-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=florian.fainelli@broadcom.com \
    --cc=kanakshilledar111@protonmail.com \
    --cc=kanakshilledar@gmail.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=rjui@broadcom.com \
    --cc=sbranden@broadcom.com \
    --cc=wahrenst@gmx.net \
    /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).