From: Rob Herring <robh@kernel.org>
To: Karthikeyan Krishnasamy <karthikeyan@linumiz.com>
Cc: krzk+dt@kernel.org, conor+dt@kernel.org, heiko@sntech.de,
alexandre.belloni@bootlin.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-rtc@vger.kernel.org
Subject: Re: [PATCH v2 5/8] dt-bindings: rtc: microcrystal,rv3028: add clock-cells property
Date: Tue, 3 Sep 2024 09:45:42 -0500 [thread overview]
Message-ID: <20240903144542.GA985263-robh@kernel.org> (raw)
In-Reply-To: <20240903105245.715899-6-karthikeyan@linumiz.com>
On Tue, Sep 03, 2024 at 04:22:42PM +0530, Karthikeyan Krishnasamy wrote:
> consume clkout from rv3028 rtc which is able to provide
> different clock frequency upon configuration
Please write complete sentences.
The subject is wrong. There is no such property 'clock-cells'.
>
> Signed-off-by: Karthikeyan Krishnasamy <karthikeyan@linumiz.com>
> ---
>
> Notes:
> v2:
> - fix commit message subject
>
> Documentation/devicetree/bindings/rtc/microcrystal,rv3028.yaml | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/rtc/microcrystal,rv3028.yaml b/Documentation/devicetree/bindings/rtc/microcrystal,rv3028.yaml
> index 5ade5dfad048..cda8ad7c1203 100644
> --- a/Documentation/devicetree/bindings/rtc/microcrystal,rv3028.yaml
> +++ b/Documentation/devicetree/bindings/rtc/microcrystal,rv3028.yaml
> @@ -22,6 +22,9 @@ properties:
> interrupts:
> maxItems: 1
>
> + "#clock-cells":
> + const: 0
> +
> trickle-resistor-ohms:
> enum:
> - 3000
> --
> 2.39.2
>
next prev parent reply other threads:[~2024-09-03 14:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 10:52 [PATCH v2 0/8] Add support Relfor Saib board which is based on Rockchip RV1109 SoC Karthikeyan Krishnasamy
2024-09-03 10:52 ` [PATCH v2 1/8] ARM: dts: rockchip: Add i2c3 node for RV1126 Karthikeyan Krishnasamy
2024-09-03 10:52 ` [PATCH v2 2/8] ARM: dts: rockchip: Add i2s0 " Karthikeyan Krishnasamy
2024-09-03 10:52 ` [PATCH v2 3/8] ARM: dts: rockchip: Add pwm " Karthikeyan Krishnasamy
2024-09-03 10:52 ` [PATCH v2 4/8] ARM: dts: rockchip: Add watchdog " Karthikeyan Krishnasamy
2024-09-04 9:11 ` Heiko Stübner
2024-09-04 14:21 ` karthikeyan
2024-09-03 10:52 ` [PATCH v2 5/8] dt-bindings: rtc: microcrystal,rv3028: add clock-cells property Karthikeyan Krishnasamy
2024-09-03 12:51 ` Krzysztof Kozlowski
2024-09-03 13:29 ` karthikeyan
2024-09-03 14:45 ` Rob Herring [this message]
2024-09-04 14:17 ` karthikeyan
2024-09-03 10:52 ` [PATCH v2 6/8] dt-bindings: vendor-prefixes: Add Relfor labs Karthikeyan Krishnasamy
2024-09-03 12:51 ` Krzysztof Kozlowski
2024-09-03 10:52 ` [PATCH v2 7/8] dt-bindings: arm: rockchip: Add Relfor Saib Karthikeyan Krishnasamy
2024-09-03 15:28 ` Rob Herring (Arm)
2024-09-03 10:52 ` [PATCH v2 8/8] ARM: dts: rockchip: Add Relfor Saib board Karthikeyan Krishnasamy
2024-09-04 9:24 ` (subset) [PATCH v2 0/8] Add support Relfor Saib board which is based on Rockchip RV1109 SoC Heiko Stuebner
2024-09-04 14:23 ` karthikeyan
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=20240903144542.GA985263-robh@kernel.org \
--to=robh@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=karthikeyan@linumiz.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-rtc@vger.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;
as well as URLs for NNTP newsgroup(s).