From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Biju Das <biju.das.jz@bp.renesas.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Fabrizio Castro <fabrizio.castro.jz@renesas.com>
Subject: Re: [PATCH v2 3/3] arm64: dts: renesas: r9a09g011: Add system configuration node
Date: Fri, 11 Nov 2022 11:50:36 +0100 [thread overview]
Message-ID: <b4e54a00-cc37-8c3a-8f72-289fdff5f1d2@linaro.org> (raw)
In-Reply-To: <OS0PR01MB5922ADB9F181E6745FE46EE986009@OS0PR01MB5922.jpnprd01.prod.outlook.com>
On 11/11/2022 10:10, Biju Das wrote:
> Hi Krzysztof Kozlowski,
>
> Thanks for the feedback.
>
>> -----Original Message-----
>> From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>> Sent: 11 November 2022 08:35
>> To: Biju Das <biju.das.jz@bp.renesas.com>; Rob Herring <robh+dt@kernel.org>;
>> Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
>> Cc: Geert Uytterhoeven <geert+renesas@glider.be>; Magnus Damm
>> <magnus.damm@gmail.com>; linux-renesas-soc@vger.kernel.org;
>> devicetree@vger.kernel.org; Chris Paterson <Chris.Paterson2@renesas.com>;
>> Fabrizio Castro <fabrizio.castro.jz@renesas.com>
>> Subject: Re: [PATCH v2 3/3] arm64: dts: renesas: r9a09g011: Add system
>> configuration node
>>
>> On 10/11/2022 17:21, Biju Das wrote:
>>> Add system configuration node to RZ/V2M SoC dtsi.
>>>
>>> Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
>>> ---
>>> v2:
>>> * New patch
>>> ---
>>> arch/arm64/boot/dts/renesas/r9a09g011.dtsi | 6 ++++++
>>> 1 file changed, 6 insertions(+)
>>>
>>> diff --git a/arch/arm64/boot/dts/renesas/r9a09g011.dtsi
>> b/arch/arm64/boot/dts/renesas/r9a09g011.dtsi
>>> index 7b949e40745a..07164d9e4a0f 100644
>>> --- a/arch/arm64/boot/dts/renesas/r9a09g011.dtsi
>>> +++ b/arch/arm64/boot/dts/renesas/r9a09g011.dtsi
>>> @@ -130,6 +130,12 @@ cpg: clock-controller@a3500000 {
>>> #power-domain-cells = <0>;
>>> };
>>>
>>> + sysc: system-configuration@a3f03000 {
>>> + compatible = "renesas,r9a09g011-sys";
>>> + reg = <0 0xa3f03000 0 0x400>;
>>> + status = "disabled";
>>
>> Why disabled? You do not have any other resources needed. This is odd.
>
> OK, will enable by default. Currently the driver compatible is used for getting SoC
> Major and Minor versions. But later will enhance to support more features.
Whatever your driver is doing, should be rather independent of
enabling/disabling nodes in DTS. Generic rule is that all SoC
components, which do not need external resources from board, should be
enabled by default. Of course there are exceptions to this rule. DTS is
anyway description of hardware, so "driver compatible" is not
appropriate argument for this (or I miss the meaning behind this).
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-11-11 10:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 16:21 [PATCH v2 0/3] Add SoC identification support for RZ/V2M Biju Das
2022-11-10 16:21 ` [PATCH v2 1/3] dt-bindings: arm: renesas: Document Renesas RZ/V2M System Configuration Biju Das
2022-11-11 8:34 ` Krzysztof Kozlowski
2022-11-11 9:06 ` Biju Das
2022-11-11 10:51 ` Krzysztof Kozlowski
2022-11-11 11:16 ` Biju Das
2022-11-14 16:18 ` Biju Das
2022-11-14 16:32 ` Krzysztof Kozlowski
2022-11-14 16:44 ` Biju Das
2022-11-14 16:51 ` Krzysztof Kozlowski
2022-11-14 17:05 ` Biju Das
2022-11-14 19:12 ` Geert Uytterhoeven
2022-11-14 19:21 ` Biju Das
2022-11-15 8:08 ` Geert Uytterhoeven
2022-11-15 11:19 ` Biju Das
2022-11-15 11:24 ` Geert Uytterhoeven
2022-11-15 11:27 ` Biju Das
2022-11-16 8:14 ` Biju Das
2022-11-16 8:20 ` Geert Uytterhoeven
2022-11-10 16:21 ` [PATCH v2 3/3] arm64: dts: renesas: r9a09g011: Add system configuration node Biju Das
2022-11-11 8:34 ` Krzysztof Kozlowski
2022-11-11 9:10 ` Biju Das
2022-11-11 10:50 ` Krzysztof Kozlowski [this message]
2022-11-11 11:25 ` Biju Das
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=b4e54a00-cc37-8c3a-8f72-289fdff5f1d2@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh+dt@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