From: Krzysztof Kozlowski <krzk@kernel.org>
To: John Madieu <john.madieu.xa@bp.renesas.com>
Cc: "geert+renesas@glider.be" <geert+renesas@glider.be>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"rafael@kernel.org" <rafael@kernel.org>,
"daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>,
"magnus.damm@gmail.com" <magnus.damm@gmail.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"john.madieu@gmail.com" <john.madieu@gmail.com>,
"rui.zhang@intel.com" <rui.zhang@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"sboyd@kernel.org" <sboyd@kernel.org>,
Biju Das <biju.das.jz@bp.renesas.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"lukasz.luba@arm.com" <lukasz.luba@arm.com>
Subject: Re: [PATCH v3 6/6] arm64: defconfig: Enable RZ/G3E thermal
Date: Mon, 17 Mar 2025 15:55:50 +0100 [thread overview]
Message-ID: <21de806b-1d25-4feb-bc30-1b5c3adf1bb0@kernel.org> (raw)
In-Reply-To: <OSBPR01MB2775B7252468BCE234BFF7D5FFDF2@OSBPR01MB2775.jpnprd01.prod.outlook.com>
On 17/03/2025 12:14, John Madieu wrote:
> Hi Krzysztof,
>
> Thanks for the review!
>
>> -----Original Message-----
>> From: Krzysztof Kozlowski <krzk@kernel.org>
>> Sent: Monday, March 17, 2025 10:29 AM
>> To: John Madieu <john.madieu.xa@bp.renesas.com>
>> Subject: Re: [PATCH v3 6/6] arm64: defconfig: Enable RZ/G3E thermal
>>
>> On Sat, Mar 15, 2025 at 09:12:16AM +0100, John Madieu wrote:
>>> Enable the CONFIG_RZG3E_THERMAL flag for the RZ/G3E SoC.
>>
>> s/RZ/Renesas RZ/ and which *upstream* board uses it? This is not your
>> platform defconfig, but all platforms and all users defconfig.
>>
>
> Noted for the fix.
>
> However, most thermal drivers use SOC-specific config options,
> as we can see in arm64 defconfig:
>
> [...]
> CONFIG_IMX8MM_THERMAL=m
> CONFIG_K3_THERMAL=m
> CONFIG_QORIQ_THERMAL=m
> CONFIG_SUN8I_THERMAL=y
> CONFIG_ROCKCHIP_THERMAL=m
> CONFIG_RCAR_THERMAL=y
> CONFIG_RCAR_GEN3_THERMAL=y
> CONFIG_RZG2L_THERMAL=y
> CONFIG_ARMADA_THERMAL=y
> CONFIG_MTK_THERMAL=m
> CONFIG_MTK_LVTS_THERMAL=m
> CONFIG_BCM2711_THERMAL=m
> CONFIG_BCM2835_THERMAL=m
> CONFIG_BRCMSTB_THERMAL=m
> [...]
>
> Hence my choice for RZG3E_THERMAL, or did I miss something in your comment?
Your commit msg must explain why do we want it. I gave you idea, if you
don't want to use it, sure, come with other.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-03-17 14:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-15 8:12 [PATCH v3 0/6] thermal: renesas: Add support fot RZ/G3E John Madieu
2025-03-15 8:12 ` [PATCH v3 1/6] soc: renesas: rz-sysc: add syscon/regmap support John Madieu
2025-03-17 15:12 ` Geert Uytterhoeven
2025-03-17 15:49 ` John Madieu
2025-03-27 12:02 ` John Madieu
2025-03-15 8:12 ` [PATCH v3 2/6] dt-bindings: thermal: r9a09g047-tsu: Document the TSU unit John Madieu
2025-03-17 9:28 ` Krzysztof Kozlowski
2025-03-17 10:56 ` John Madieu
2025-03-15 8:12 ` [PATCH v3 3/6] thermal: renesas: rzg3e: Add thermal driver for the Renesas RZ/G3E SoC John Madieu
2025-03-15 8:12 ` [PATCH v3 4/6] thermal: renesas: rzg3e: Add safety check when reading temperature John Madieu
2025-03-15 8:12 ` [PATCH v3 5/6] arm64: dts: renesas: r9a09g047: Add TSU node John Madieu
2025-03-15 8:12 ` [PATCH v3 6/6] arm64: defconfig: Enable RZ/G3E thermal John Madieu
2025-03-17 9:29 ` Krzysztof Kozlowski
2025-03-17 11:14 ` John Madieu
2025-03-17 13:06 ` Geert Uytterhoeven
2025-03-17 13:10 ` John Madieu
2025-03-17 14:56 ` Krzysztof Kozlowski
2025-03-17 14:55 ` Krzysztof Kozlowski [this message]
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=21de806b-1d25-4feb-bc30-1b5c3adf1bb0@kernel.org \
--to=krzk@kernel.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=john.madieu.xa@bp.renesas.com \
--cc=john.madieu@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=magnus.damm@gmail.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=rui.zhang@intel.com \
--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).