From: claudiu beznea <claudiu.beznea@tuxon.dev>
To: Krzysztof Kozlowski <krzk@kernel.org>,
geert+renesas@glider.be, mturquette@baylibre.com,
sboyd@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, lee@kernel.org,
alexandre.belloni@bootlin.com, magnus.damm@gmail.com
Cc: 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 03/12] dt-bindings: mfd: renesas,rzg3s-vbattb: Document VBATTB
Date: Mon, 17 Jun 2024 10:25:52 +0300 [thread overview]
Message-ID: <f0f77eda-b7f4-4a3b-a0e6-a3d5a78419fb@tuxon.dev> (raw)
In-Reply-To: <c882bac6-9cb9-4ba2-9bc4-967c03fcb031@tuxon.dev>
On 17.06.2024 10:16, claudiu beznea wrote:
>
>
> On 16.06.2024 10:38, Krzysztof Kozlowski wrote:
>> On 14/06/2024 09:19, Claudiu wrote:
>>> From: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
>>
>>> +
>>> +maintainers:
>>> + - Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
>>> +
>>> +properties:
>>> + compatible:
>>> + items:
>>> + - const: renesas,rzg3s-vbattb
>>> + - const: syscon
>>> + - const: simple-mfd
>>
>> No, mfd does no look good. That's not a simple device anymore and you
>> claim here child does not need vbat bclk, power domains and resets? That
>> would be a big surprise, although technically possible.
>
> I wasn't sure how this MFD will be received by the Renesas maintainers so I
> kept it simple for this version.
>
> In theory the VBAT clk, power domain and resets are specific to VBAT module
> itself but, indeed, the child cannot work w/o these.
>
>>
>> Please clarify: which of parent resources are needed for children?
>
> VBAT clock, power domain are needed. Reset, too. In the current
> implementation the reset is deasserted though parent by calling the
> syscon_node_to_regmap(np->parent) in the clock driver.
>
>>
>> ...
>>
>>> +
>>> +additionalProperties: false
>>> +
>>> +examples:
>>> + - |
>>> + #include <dt-bindings/clock/r9a08g045-cpg.h>
>>> + #include <dt-bindings/interrupt-controller/arm-gic.h>
>>> +
>>> + vbattb: vbattb@1005c000 {
>>> + compatible = "renesas,rzg3s-vbattb", "syscon", "simple-mfd";
>>> + reg = <0x1005c000 0x1000>;
>>> + ranges = <0 0 0x1005c000 0 0x1000>;
>>> + interrupts = <GIC_SPI 43 IRQ_TYPE_LEVEL_HIGH>;
>>> + interrupt-names = "tampdi";
>>> + clocks = <&cpg CPG_MOD R9A08G045_VBAT_BCLK>;
>>> + clock-names = "bclk";
>>> + power-domains = <&cpg>;
>>> + resets = <&cpg R9A08G045_VBAT_BRESETN>;
>>> + #address-cells = <2>;
>>> + #size-cells = <2>;
>>> + status = "disabled";
>>
>> Drop
>
> Could you please clarify this? Would you want me to drop the full node
> (same for clock-controller node)?
Looking at your review on patch 05/12 from this series I noticed you're
taking about the status = "disabled" lines.
I'll drop it as suggested.
Thank you,
Claudiu Beznea
>
> Can you point me an example that you are thinking about?
>
> Thank you,
> Claudiu Beznea
>
>>
>>> +
>>> + vbattclk: clock-controller@1c {
>>> + compatible = "renesas,rzg3s-vbattb-clk";
>>> + reg = <0 0x1c 0 0x10>;
>>> + clocks = <&cpg CPG_MOD R9A08G045_VBAT_BCLK>, <&vbattb_xtal>;
>>> + clock-names = "bclk", "vbattb_xtal";
>>> + #clock-cells = <0>;
>>> + power-domains = <&cpg>;
>>> + status = "disabled";
>>
>> Drop
>>
>>> + };
>>> + };
>>> +
>>> +...
>>
>> Best regards,
>> Krzysztof
>>
next prev parent reply other threads:[~2024-06-17 7:25 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 7:19 [PATCH 00/12] Add RTC support for the Renesas RZ/G3S SoC Claudiu
2024-06-14 7:19 ` [PATCH 01/12] clk: renesas: r9a08g045: Add clock, reset and power domain support for the VBATTB IP Claudiu
2024-06-26 12:09 ` Geert Uytterhoeven
2024-06-14 7:19 ` [PATCH 02/12] dt-bindings: clock: renesas,rzg3s-vbattb-clk: Document the VBATTB clock driver Claudiu
2024-06-15 12:17 ` Conor Dooley
2024-06-17 7:02 ` claudiu beznea
2024-06-17 15:19 ` Conor Dooley
2024-06-18 7:34 ` claudiu beznea
2024-06-18 7:56 ` Geert Uytterhoeven
2024-06-18 8:11 ` claudiu beznea
2024-06-16 7:38 ` Krzysztof Kozlowski
2024-06-17 7:34 ` claudiu beznea
2024-06-14 7:19 ` [PATCH 03/12] dt-bindings: mfd: renesas,rzg3s-vbattb: Document VBATTB Claudiu
2024-06-15 12:19 ` Conor Dooley
2024-06-17 7:04 ` claudiu beznea
2024-06-16 7:38 ` Krzysztof Kozlowski
2024-06-17 7:16 ` claudiu beznea
2024-06-17 7:25 ` claudiu beznea [this message]
2024-06-17 8:10 ` Krzysztof Kozlowski
2024-06-14 7:19 ` [PATCH 04/12] clk: renesas: clk-vbattb: Add VBATTB clock driver Claudiu
2024-06-15 22:25 ` kernel test robot
2024-06-16 0:19 ` kernel test robot
2024-06-14 7:19 ` [PATCH 05/12] dt-bindings: rtc: renesas,rzg3s-rtc: Document the Renesas RZ/G3S RTC Claudiu
2024-06-14 7:53 ` Biju Das
2024-06-14 8:16 ` claudiu beznea
2024-06-14 8:22 ` Biju Das
2024-06-15 12:16 ` Conor Dooley
2024-06-15 12:20 ` Conor Dooley
2024-06-17 7:19 ` claudiu beznea
2024-06-17 15:17 ` Conor Dooley
2024-06-16 7:40 ` Krzysztof Kozlowski
2024-06-17 7:24 ` claudiu beznea
2024-06-14 7:19 ` [PATCH 06/12] rtc: renesas-rtca3: Add driver for RTCA-3 available on Renesas RZ/G3S SoC Claudiu
2024-06-14 7:51 ` Biju Das
2024-06-14 9:21 ` Alexandre Belloni
2024-06-14 11:06 ` claudiu beznea
2024-06-17 7:25 ` Alexandre Belloni
2024-06-17 7:31 ` claudiu beznea
2024-07-16 8:01 ` claudiu beznea
2024-06-14 7:19 ` [PATCH 07/12] arm64: dts: renesas: r9a08g045: Add VBATTB node Claudiu
2024-06-14 7:19 ` [PATCH 08/12] arm64: dts: renesas: r9a08g045: Add RTC node Claudiu
2024-06-14 7:19 ` [PATCH 09/12] arm64: dts: renesas: rzg3s-smarc-som: Enable VBATTB clock Claudiu
2024-06-14 7:19 ` [PATCH 10/12] arm64: dts: renesas: rzg3s-smarc-som: Enable RTC Claudiu
2024-06-14 7:19 ` [PATCH 11/12] arm64: defconfig: Enable VBATTB clock flag Claudiu
2024-06-14 7:19 ` [PATCH 12/12] arm64: defconfig: Enable Renesas RTCA-3 flag Claudiu
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=f0f77eda-b7f4-4a3b-a0e6-a3d5a78419fb@tuxon.dev \
--to=claudiu.beznea@tuxon.dev \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=lee@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=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 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).