From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: claudiu beznea <claudiu.beznea@tuxon.dev>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
mturquette@baylibre.com, sboyd@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, magnus.damm@gmail.com,
p.zabel@pengutronix.de, linux-renesas-soc@vger.kernel.org,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-rtc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
Subject: Re: [PATCH v3 08/12] arm64: dts: renesas: r9a08g045: Add RTC node
Date: Thu, 17 Oct 2024 00:03:46 +0200 [thread overview]
Message-ID: <2024101622034648032b39@mail.local> (raw)
In-Reply-To: <4ff318b0-cd7c-4857-888c-a07c8985fce9@tuxon.dev>
On 11/10/2024 13:28:55+0300, claudiu beznea wrote:
> >> + compatible = "renesas,r9a08g045-rtca3", "renesas,rz-rtca3";
> >> + reg = <0 0x1004ec00 0 0x400>;
> >> + interrupts = <GIC_SPI 315 IRQ_TYPE_LEVEL_HIGH>,
> >> + <GIC_SPI 316 IRQ_TYPE_LEVEL_HIGH>,
> >> + <GIC_SPI 317 IRQ_TYPE_LEVEL_HIGH>;
> >> + interrupt-names = "alarm", "period", "carry";
> >> + clocks = <&cpg CPG_MOD R9A08G045_VBAT_BCLK>, <&vbattb VBATTB_VBATTCLK>;
> >> + clock-names = "bus", "counter";
> >> + assigned-clocks = <&vbattb VBATTB_MUX>;
> >> + assigned-clock-parents = <&vbattb VBATTB_XC>;
> >
> > Don't the assigned-clock* properties belong in the board DTS?
>
> It makes sense to be in the board DTS, indeed.
>
> > In addition, I think they should be documented in the DT bindings,
> > and be made required, so board developers don't forget about them.
>
> It would be better, indeed.
There were multiple recent emails from Rob saying that assigned-clocks
should not be part of the bindings.
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2024-10-16 22:03 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 13:02 [PATCH v3 00/12] Add RTC support for the Renesas RZ/G3S SoC Claudiu
2024-08-30 13:02 ` [PATCH v3 01/12] dt-bindings: clock: renesas,r9a08g045-vbattb: Document VBATTB Claudiu
2024-08-30 17:46 ` Rob Herring
2024-08-30 22:06 ` Alexandre Belloni
2024-09-02 14:55 ` claudiu beznea
2024-09-03 6:58 ` Biju Das
2024-09-03 7:23 ` Geert Uytterhoeven
2024-09-03 7:25 ` Biju Das
2024-09-03 7:29 ` Biju Das
2024-09-03 7:28 ` claudiu beznea
2024-09-03 7:36 ` Biju Das
2024-09-03 7:40 ` Geert Uytterhoeven
2024-09-03 7:44 ` claudiu beznea
2024-09-03 7:51 ` Biju Das
2024-10-10 9:58 ` Geert Uytterhoeven
2024-10-10 10:08 ` Geert Uytterhoeven
2024-08-30 13:02 ` [PATCH v3 02/12] dt-bindings: clock: r9a08g045-vbattb: Add clock IDs for the VBATTB controller Claudiu
2024-08-30 17:47 ` Rob Herring
2024-10-10 9:55 ` Geert Uytterhoeven
2024-08-30 13:02 ` [PATCH v3 03/12] clk: linux/clk-provider.h: Add devm_clk_hw_register_gate_parent_hw() Claudiu
2024-10-10 10:00 ` Geert Uytterhoeven
2024-08-30 13:02 ` [PATCH v3 04/12] clk: renesas: clk-vbattb: Add VBATTB clock driver Claudiu
2024-10-10 10:06 ` Geert Uytterhoeven
2024-08-30 13:02 ` [PATCH v3 05/12] dt-bindings: rtc: renesas,rzg3s-rtc: Document the Renesas RTCA-3 IP Claudiu
2024-08-30 15:44 ` Rob Herring (Arm)
2024-10-10 9:29 ` Geert Uytterhoeven
2024-10-10 9:52 ` claudiu beznea
2024-10-10 15:31 ` Geert Uytterhoeven
2024-08-30 13:02 ` [PATCH v3 06/12] rtc: renesas-rtca3: Add driver for RTCA-3 available on Renesas RZ/G3S SoC Claudiu
2024-08-30 22:25 ` Alexandre Belloni
2024-09-02 14:49 ` claudiu beznea
2024-09-02 20:28 ` Alexandre Belloni
2024-09-03 7:29 ` claudiu beznea
2024-09-03 16:09 ` claudiu beznea
2024-09-03 17:36 ` Alexandre Belloni
2024-10-17 10:45 ` Wolfram Sang
2024-10-17 10:51 ` Geert Uytterhoeven
2024-10-17 11:04 ` Wolfram Sang
2024-08-30 13:02 ` [PATCH v3 07/12] arm64: dts: renesas: r9a08g045: Add VBATTB node Claudiu
2024-09-03 19:48 ` Stephen Boyd
2024-09-04 12:17 ` claudiu beznea
2024-09-05 18:09 ` Stephen Boyd
2024-09-06 7:28 ` Geert Uytterhoeven
2024-09-06 23:01 ` Stephen Boyd
2024-09-09 12:11 ` Geert Uytterhoeven
2024-09-09 21:18 ` Stephen Boyd
2024-09-10 8:02 ` Geert Uytterhoeven
2024-10-10 15:17 ` Geert Uytterhoeven
2024-08-30 13:02 ` [PATCH v3 08/12] arm64: dts: renesas: r9a08g045: Add RTC node Claudiu
2024-10-10 15:22 ` Geert Uytterhoeven
2024-10-11 10:28 ` claudiu beznea
2024-10-16 22:03 ` Alexandre Belloni [this message]
2024-10-17 7:57 ` Geert Uytterhoeven
2024-08-30 13:02 ` [PATCH v3 09/12] arm64: dts: renesas: rzg3s-smarc-som: Enable VBATTB Claudiu
2024-10-10 15:28 ` Geert Uytterhoeven
2024-08-30 13:02 ` [PATCH v3 10/12] arm64: dts: renesas: rzg3s-smarc-som: Enable RTC Claudiu
2024-10-10 15:28 ` Geert Uytterhoeven
2024-08-30 13:02 ` [PATCH v3 11/12] arm64: defconfig: Enable VBATTB clock Claudiu
2024-10-10 15:29 ` Geert Uytterhoeven
2024-08-30 13:02 ` [PATCH v3 12/12] arm64: defconfig: Enable Renesas RTCA-3 flag Claudiu
2024-10-10 15:30 ` Geert Uytterhoeven
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=2024101622034648032b39@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=sboyd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.