From: Krzysztof Kozlowski <krzk@kernel.org>
To: Akhilesh Patil <akhilesh@ee.iitb.ac.in>,
alexandre.belloni@bootlin.com, krzk+dt@kernel.org,
robh@kernel.org, conor+dt@kernel.org
Cc: skhan@linuxfoundation.org, linux-rtc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
akhileshpatilvnit@gmail.com
Subject: Re: [PATCH 2/7] dt-bindings: rtc: add bindings for m41t93
Date: Wed, 3 Sep 2025 16:30:53 +0200 [thread overview]
Message-ID: <9094d792-c20a-48fa-b769-5824e1f451eb@kernel.org> (raw)
In-Reply-To: <40c91cbb07140ecdf4f91afc118c2518e85041c3.1756908788.git.akhilesh@ee.iitb.ac.in>
On 03/09/2025 16:25, Akhilesh Patil wrote:
> add DT bindings for m41t93 rtc in YAML format.
A nit, subject: drop second/last, redundant "bindings". The
"dt-bindings" prefix is already stating that these are bindings.
See also:
https://elixir.bootlin.com/linux/v6.17-rc3/source/Documentation/devicetree/bindings/submitting-patches.rst#L18
Please organize the patch documenting compatible (DT bindings) before
their user.
See also:
https://elixir.bootlin.com/linux/v6.14-rc6/source/Documentation/devicetree/bindings/submitting-patches.rst#L46
>
> Signed-off-by: Akhilesh Patil <akhilesh@ee.iitb.ac.in>
> ---
> .../devicetree/bindings/rtc/st,m41t93.yaml | 43 +++++++++++++++++++
> 1 file changed, 43 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/rtc/st,m41t93.yaml
>
> diff --git a/Documentation/devicetree/bindings/rtc/st,m41t93.yaml b/Documentation/devicetree/bindings/rtc/st,m41t93.yaml
> new file mode 100644
> index 000000000000..03673adc79db
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/rtc/st,m41t93.yaml
> @@ -0,0 +1,43 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/rtc/st,m41t93.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: ST M41T93 RTC and compatible
> +
> +maintainers:
> + - Alexandre Belloni <alexandre.belloni@bootlin.com>
This should not be subsystem maintainer.
> +
> +properties:
> + compatible:
> + enum:
> + - st,m41t93
> +
> + reg:
> + maxItems: 1
> +
> + "#clock-cells":
Hm? Are you sure? Nothing in the driver nor commit msg suggests that.
> + const: 1
> +
> +allOf:
> + - $ref: rtc.yaml
> +
> +unevaluatedProperties: false
This goes after required. See example schema.
> +
> +required:
> + - compatible
> + - reg
> +
> +examples:
> + - |
> + spi {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + rtc@0 {
> + spi-max-frequency = <2000000>;
Does not look tested.
> + compatible = "st,m41t93";
> + reg = <0>;
Please follow DTS coding style. Which property is the first in the
coding style?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-09-03 14:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 14:23 [PATCH 0/7] rtc: m41t93: add new features alarm, clock out, watchdog Akhilesh Patil
2025-09-03 14:25 ` [PATCH 1/7] rtc: m41t93: add device tree support Akhilesh Patil
2025-09-03 14:25 ` [PATCH 2/7] dt-bindings: rtc: add bindings for m41t93 Akhilesh Patil
2025-09-03 14:30 ` Krzysztof Kozlowski [this message]
2025-09-03 20:33 ` Rob Herring (Arm)
2025-09-03 14:26 ` [PATCH 3/7] rtc: m41t93: migrate to regmap api for register access Akhilesh Patil
2025-09-03 14:26 ` [PATCH 4/7] rtc: m41t93: Add alarm support Akhilesh Patil
2025-09-04 5:07 ` kernel test robot
2025-09-03 14:27 ` [PATCH 5/7] rtc: m41t93: fix device connection/detection logic during probe Akhilesh Patil
2025-09-03 14:47 ` Alexandre Belloni
2025-09-03 14:27 ` [PATCH 6/7] rtc: m41t93: Add square wave clock provider support Akhilesh Patil
2025-09-04 4:42 ` kernel test robot
2025-09-03 14:28 ` [PATCH 7/7] rtc: m41t93: Add watchdog support Akhilesh Patil
2025-09-04 23:23 ` kernel test robot
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=9094d792-c20a-48fa-b769-5824e1f451eb@kernel.org \
--to=krzk@kernel.org \
--cc=akhilesh@ee.iitb.ac.in \
--cc=akhileshpatilvnit@gmail.com \
--cc=alexandre.belloni@bootlin.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 \
--cc=skhan@linuxfoundation.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).