Linux RTC
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Javier Carrasco <javier.carrasco.cruz@gmail.com>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Chris Verges <chrisv@cyberswitching.com>,
	linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: rtc: pcf2123: convert to YAML
Date: Sun, 10 Sep 2023 14:17:44 +0200	[thread overview]
Message-ID: <202309101217447eae4bc4@mail.local> (raw)
In-Reply-To: <20230907-topic-pcf2123_yaml-v1-1-40e82bed2066@gmail.com>

On 10/09/2023 13:00:27+0200, Javier Carrasco wrote:
> Convert the existing txt binding to the preferred YAML format.
> 
> The pcf2123 node may contain SPI settings such as spi-cs-high and
> spi-max-frequency, which keeps it from being added to the trivial-rtc
> binding with its current definition. Add a reference to
> spi-peripheral-props.yaml to account for that.
> 
> The "interrupts" property was missing in the binding although it is
> already supported. Add the missing property in the new binding.
> 
> Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
> ---
>  .../devicetree/bindings/rtc/nxp,pcf2123.yaml       | 45 ++++++++++++++++++++++
>  .../devicetree/bindings/rtc/nxp,rtc-2123.txt       | 17 --------
>  2 files changed, 45 insertions(+), 17 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/rtc/nxp,pcf2123.yaml b/Documentation/devicetree/bindings/rtc/nxp,pcf2123.yaml
> new file mode 100644
> index 000000000000..013e5e5dc0ae
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/rtc/nxp,pcf2123.yaml
> @@ -0,0 +1,45 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/rtc/nxp,pcf2123.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: NXP PCF2123 SPI Real Time Clock
> +
> +maintainers:
> +  - Chris Verges <chrisv@cyberswitching.com>

Is Chris willing to maintain the binding?

> +
> +allOf:
> +  - $ref: /schemas/spi/spi-peripheral-props.yaml#
> +  - $ref: rtc.yaml#
> +
> +properties:
> +  compatible:
> +    enum:
> +      - nxp,pcf2123
> +
> +  reg:
> +    maxItems: 1
> +
> +  interrupts:
> +    maxItems: 1
> +
> +required:
> +  - compatible
> +  - reg
> +
> +unevaluatedProperties: false
> +
> +examples:
> +  - |
> +    spi {
> +        #address-cells = <1>;
> +        #size-cells = <0>;
> +
> +        rtc@3 {
> +            compatible = "nxp,pcf2123";
> +            reg = <3>;
> +            spi-cs-high;
> +        };
> +    };
> +...
> diff --git a/Documentation/devicetree/bindings/rtc/nxp,rtc-2123.txt b/Documentation/devicetree/bindings/rtc/nxp,rtc-2123.txt
> deleted file mode 100644
> index 7371f525a687..000000000000
> --- a/Documentation/devicetree/bindings/rtc/nxp,rtc-2123.txt
> +++ /dev/null
> @@ -1,17 +0,0 @@
> -NXP PCF2123 SPI Real Time Clock
> -
> -Required properties:
> -- compatible: should be: "nxp,pcf2123"
> -                      or "microcrystal,rv2123"
> -- reg: should be the SPI slave chipselect address
> -
> -Optional properties:
> -- spi-cs-high: PCF2123 needs chipselect high
> -
> -Example:
> -
> -pcf2123: rtc@3 {
> -	compatible = "nxp,pcf2123"
> -	reg = <3>
> -	spi-cs-high;
> -};
> 
> ---
> base-commit: 535a265d7f0dd50d8c3a4f8b4f3a452d56bd160f
> change-id: 20230907-topic-pcf2123_yaml-2ce57f4e77d7
> 
> Best regards,
> -- 
> Javier Carrasco <javier.carrasco.cruz@gmail.com>
> 

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2023-09-10 12:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-10 11:00 [PATCH] dt-bindings: rtc: pcf2123: convert to YAML Javier Carrasco
2023-09-10 12:17 ` Alexandre Belloni [this message]
2023-09-10 12:31   ` Javier Carrasco
2023-09-11  8:43   ` Javier Carrasco
2023-09-11  6:17 ` Krzysztof Kozlowski
2023-09-11  8:27   ` Javier Carrasco

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=202309101217447eae4bc4@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=a.zummo@towertech.it \
    --cc=chrisv@cyberswitching.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=javier.carrasco.cruz@gmail.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@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