From: Krzysztof Kozlowski <krzk@kernel.org>
To: Antoni Pokusinski <apokusinski01@gmail.com>
Cc: alexandre.belloni@bootlin.com, krzk+dt@kernel.org,
conor+dt@kernel.org, robh@kernel.org,
alexander.stein@ew.tq-group.com, linux-rtc@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 3/3] dt-bindings: rtc: pcf85063: add binding for RV8063
Date: Thu, 10 Apr 2025 09:23:18 +0200 [thread overview]
Message-ID: <20250410-enchanted-uber-finch-c60afb@shite> (raw)
In-Reply-To: <20250409170916.47224-4-apokusinski01@gmail.com>
On Wed, Apr 09, 2025 at 07:09:16PM GMT, Antoni Pokusinski wrote:
> Microcrystal RV8063 is a real-time clock module with SPI interface.
>
> Signed-off-by: Antoni Pokusinski <apokusinski01@gmail.com>
> ---
> .../devicetree/bindings/rtc/nxp,pcf85063.yaml | 33 ++++++++++++++++++-
> 1 file changed, 32 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/rtc/nxp,pcf85063.yaml b/Documentation/devicetree/bindings/rtc/nxp,pcf85063.yaml
> index 2f892f8640d1..cb31c7619d66 100644
> --- a/Documentation/devicetree/bindings/rtc/nxp,pcf85063.yaml
> +++ b/Documentation/devicetree/bindings/rtc/nxp,pcf85063.yaml
> @@ -12,6 +12,7 @@ maintainers:
> properties:
> compatible:
> enum:
> + - microcrystal,rv8063
Bindings are before the users, so this cannot be patch 3/3.
> - microcrystal,rv8263
> - nxp,pcf85063
> - nxp,pcf85063a
> @@ -44,7 +45,12 @@ properties:
>
> wakeup-source: true
>
> + spi-cs-high: true
> +
> + spi-3wire: true
> +
> allOf:
> + - $ref: /schemas/spi/spi-peripheral-props.yaml#
> - $ref: rtc.yaml#
> - if:
> properties:
> @@ -52,6 +58,7 @@ allOf:
> contains:
> enum:
> - microcrystal,rv8263
> + - microcrystal,rv8063
Keep the order.
> then:
> properties:
> quartz-load-femtofarads: false
> @@ -65,12 +72,23 @@ allOf:
> properties:
> quartz-load-femtofarads:
> const: 7000
> + - if:
> + properties:
> + compatible:
> + not:
> + contains:
> + enum:
> + - microcrystal,rv8063
> + then:
> + properties:
> + spi-cs-high: false
> + spi-3wire: false
>
> required:
> - compatible
> - reg
>
> -additionalProperties: false
> +unevaluatedProperties: false
>
> examples:
> - |
> @@ -90,3 +108,16 @@ examples:
> };
> };
> };
> +
> + - |
> + spi {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + rtc@0 {
> + compatible = "microcrystal,rv8063";
Messed indentation. Look at rest of the examples here and use the same
indentation.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-04-10 7:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 17:09 [PATCH v2 0/3] add support for RV8063 SPI rtc Antoni Pokusinski
2025-04-09 17:09 ` [PATCH v2 1/3] rtc: pcf85063: create pcf85063_i2c_probe Antoni Pokusinski
2025-04-09 17:09 ` [PATCH v2 2/3] rtc: pcf85063: add support for RV8063 Antoni Pokusinski
2025-04-09 17:09 ` [PATCH v2 3/3] dt-bindings: rtc: pcf85063: add binding " Antoni Pokusinski
2025-04-10 7:23 ` Krzysztof Kozlowski [this message]
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=20250410-enchanted-uber-finch-c60afb@shite \
--to=krzk@kernel.org \
--cc=alexander.stein@ew.tq-group.com \
--cc=alexandre.belloni@bootlin.com \
--cc=apokusinski01@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=robh@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