From: Krzysztof Kozlowski <krzk@kernel.org>
To: Akhilesh Patil <akhilesh@ee.iitb.ac.in>
Cc: alexandre.belloni@bootlin.com, krzk+dt@kernel.org,
robh@kernel.org, conor+dt@kernel.org, skhan@linuxfoundation.org,
linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, akhileshpatilvnit@gmail.com
Subject: Re: [PATCH v2 1/6] dt-bindings: rtc: Add ST m41t93
Date: Thu, 11 Sep 2025 09:43:09 +0200 [thread overview]
Message-ID: <20250911-resolute-translucent-koala-1707dd@kuoka> (raw)
In-Reply-To: <3aed714163abc86a18a62f039b285643d9504e64.1757510157.git.akhilesh@ee.iitb.ac.in>
On Wed, Sep 10, 2025 at 07:22:33PM +0530, Akhilesh Patil wrote:
> Document DT bindings for m41t93 rtc which supports time, date,
> alarm, watchdog, square wave clock output provider, user sram
> and 8 bit timer.
>
> Signed-off-by: Akhilesh Patil <akhilesh@ee.iitb.ac.in>
> ---
> .../devicetree/bindings/rtc/st,m41t93.yaml | 50 +++++++++++++++++++
> 1 file changed, 50 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..bd593669cfa2
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/rtc/st,m41t93.yaml
> @@ -0,0 +1,50 @@
> +# 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:
> + - linux-rtc@vger.kernel.org
Not much improved. This should be a person responsible/caring about this
hardware support in the kernel. Why would we want to take the binding if
no one cares about it?
> +
> +description: |
Do not need '|' unless you need to preserve formatting.
> + ST M41T93 is spi based Real Time Clock (RTC) with time, date,
> + alarm, watchdog, square wave clock output, 8 bit timer and
> + 7 bytes of user SRAM.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-09-11 7:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 13:52 [PATCH v2 0/6] rtc: m41t93: add new features alarm, clock out, watchdog Akhilesh Patil
2025-09-10 13:52 ` [PATCH v2 1/6] dt-bindings: rtc: Add ST m41t93 Akhilesh Patil
2025-09-11 7:43 ` Krzysztof Kozlowski [this message]
2025-09-15 14:19 ` Akhilesh Patil
2025-09-17 0:52 ` Krzysztof Kozlowski
2025-09-20 14:47 ` Akhilesh Patil
2025-09-10 13:53 ` [PATCH v2 2/6] rtc: m41t93: add device tree support Akhilesh Patil
2025-09-10 13:53 ` [PATCH v2 3/6] rtc: m41t93: migrate to regmap api for register access Akhilesh Patil
2025-09-10 13:53 ` [PATCH v2 4/6] rtc: m41t93: Add alarm support Akhilesh Patil
2025-09-10 13:54 ` [PATCH v2 5/6] rtc: m41t93: Add square wave clock provider support Akhilesh Patil
2025-09-10 13:54 ` [PATCH v2 6/6] rtc: m41t93: Add watchdog support Akhilesh Patil
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=20250911-resolute-translucent-koala-1707dd@kuoka \
--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