From: Heiko Stuebner <heiko@sntech.de>
To: Alexey Charkov <alchark@gmail.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonas Karlman <jonas@kwiboo.se>,
Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
Cc: Sebastian Reichel <sebastian.reichel@collabora.com>,
kernel@collabora.com, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
Subject: Re: [PATCH v6 1/7] thermal: rockchip: rename rk_tsadcv3_tshut_mode
Date: Thu, 10 Jul 2025 13:16:27 +0200 [thread overview]
Message-ID: <7568508.DvuYhMxLoT@phil> (raw)
In-Reply-To: <20250610-rk3576-tsadc-upstream-v6-1-b6e9efbf1015@collabora.com>
Am Dienstag, 10. Juni 2025, 14:32:37 Mitteleuropäische Sommerzeit schrieb Nicolas Frattaroli:
> The "v" version specifier here refers to the hardware IP revision.
> Mainline deviated from downstream here by calling the v4 revision v3 as
> it didn't support the v3 hardware revision at all.
>
> This creates needless confusion, so rename it to rk_tsadcv4_tshut_mode
> to be consistent with what the hardware wants to be called.
>
> Signed-off-by: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
I checked the vendor-kernel, and your're right the
rv1126 gets identified as v3 it seems, while all of rk35xx except rk3568
(= rk3506, rk3528, rk3562, rk3576, rk3588) call themself v4
> ---
> drivers/thermal/rockchip_thermal.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/thermal/rockchip_thermal.c b/drivers/thermal/rockchip_thermal.c
> index a8ad85feb68fbb7ec8d79602b16c47838ecb3c00..40c7d234c3ef99f69dd8db4d8c47f9d493c0583d 100644
> --- a/drivers/thermal/rockchip_thermal.c
> +++ b/drivers/thermal/rockchip_thermal.c
> @@ -1045,7 +1045,7 @@ static void rk_tsadcv2_tshut_mode(int chn, void __iomem *regs,
> writel_relaxed(val, regs + TSADCV2_INT_EN);
> }
>
> -static void rk_tsadcv3_tshut_mode(int chn, void __iomem *regs,
> +static void rk_tsadcv4_tshut_mode(int chn, void __iomem *regs,
> enum tshut_mode mode)
> {
> u32 val_gpio, val_cru;
> @@ -1297,7 +1297,7 @@ static const struct rockchip_tsadc_chip rk3588_tsadc_data = {
> .get_temp = rk_tsadcv4_get_temp,
> .set_alarm_temp = rk_tsadcv3_alarm_temp,
> .set_tshut_temp = rk_tsadcv3_tshut_temp,
> - .set_tshut_mode = rk_tsadcv3_tshut_mode,
> + .set_tshut_mode = rk_tsadcv4_tshut_mode,
> .table = {
> .id = rk3588_code_table,
> .length = ARRAY_SIZE(rk3588_code_table),
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: Alexey Charkov <alchark@gmail.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonas Karlman <jonas@kwiboo.se>,
Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
Cc: devicetree@vger.kernel.org, linux-pm@vger.kernel.org,
Sebastian Reichel <sebastian.reichel@collabora.com>,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
kernel@collabora.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6 1/7] thermal: rockchip: rename rk_tsadcv3_tshut_mode
Date: Thu, 10 Jul 2025 13:16:27 +0200 [thread overview]
Message-ID: <7568508.DvuYhMxLoT@phil> (raw)
In-Reply-To: <20250610-rk3576-tsadc-upstream-v6-1-b6e9efbf1015@collabora.com>
Am Dienstag, 10. Juni 2025, 14:32:37 Mitteleuropäische Sommerzeit schrieb Nicolas Frattaroli:
> The "v" version specifier here refers to the hardware IP revision.
> Mainline deviated from downstream here by calling the v4 revision v3 as
> it didn't support the v3 hardware revision at all.
>
> This creates needless confusion, so rename it to rk_tsadcv4_tshut_mode
> to be consistent with what the hardware wants to be called.
>
> Signed-off-by: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
I checked the vendor-kernel, and your're right the
rv1126 gets identified as v3 it seems, while all of rk35xx except rk3568
(= rk3506, rk3528, rk3562, rk3576, rk3588) call themself v4
> ---
> drivers/thermal/rockchip_thermal.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/thermal/rockchip_thermal.c b/drivers/thermal/rockchip_thermal.c
> index a8ad85feb68fbb7ec8d79602b16c47838ecb3c00..40c7d234c3ef99f69dd8db4d8c47f9d493c0583d 100644
> --- a/drivers/thermal/rockchip_thermal.c
> +++ b/drivers/thermal/rockchip_thermal.c
> @@ -1045,7 +1045,7 @@ static void rk_tsadcv2_tshut_mode(int chn, void __iomem *regs,
> writel_relaxed(val, regs + TSADCV2_INT_EN);
> }
>
> -static void rk_tsadcv3_tshut_mode(int chn, void __iomem *regs,
> +static void rk_tsadcv4_tshut_mode(int chn, void __iomem *regs,
> enum tshut_mode mode)
> {
> u32 val_gpio, val_cru;
> @@ -1297,7 +1297,7 @@ static const struct rockchip_tsadc_chip rk3588_tsadc_data = {
> .get_temp = rk_tsadcv4_get_temp,
> .set_alarm_temp = rk_tsadcv3_alarm_temp,
> .set_tshut_temp = rk_tsadcv3_tshut_temp,
> - .set_tshut_mode = rk_tsadcv3_tshut_mode,
> + .set_tshut_mode = rk_tsadcv4_tshut_mode,
> .table = {
> .id = rk3588_code_table,
> .length = ARRAY_SIZE(rk3588_code_table),
>
>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-07-10 12:49 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 12:32 [PATCH v6 0/7] RK3576 thermal sensor support, including OTP trim adjustments Nicolas Frattaroli
2025-06-10 12:32 ` Nicolas Frattaroli
2025-06-10 12:32 ` [PATCH v6 1/7] thermal: rockchip: rename rk_tsadcv3_tshut_mode Nicolas Frattaroli
2025-06-10 12:32 ` Nicolas Frattaroli
2025-07-10 11:16 ` Heiko Stuebner [this message]
2025-07-10 11:16 ` Heiko Stuebner
2025-06-10 12:32 ` [PATCH v6 2/7] dt-bindings: rockchip-thermal: Add RK3576 compatible Nicolas Frattaroli
2025-06-10 12:32 ` Nicolas Frattaroli
2025-07-10 11:17 ` Heiko Stuebner
2025-07-10 11:17 ` Heiko Stuebner
2025-06-10 12:32 ` [PATCH v6 3/7] thermal: rockchip: Support RK3576 SoC in the thermal driver Nicolas Frattaroli
2025-06-10 12:32 ` Nicolas Frattaroli
2025-07-10 11:18 ` Heiko Stuebner
2025-07-10 11:18 ` Heiko Stuebner
2025-06-10 12:32 ` [PATCH v6 4/7] dt-bindings: thermal: rockchip: document otp thermal trim Nicolas Frattaroli
2025-06-10 12:32 ` Nicolas Frattaroli
2025-07-10 11:21 ` Heiko Stuebner
2025-07-10 11:21 ` Heiko Stuebner
2025-07-10 19:30 ` Nicolas Frattaroli
2025-07-10 19:30 ` Nicolas Frattaroli
2025-06-10 12:32 ` [PATCH v6 5/7] thermal: rockchip: support reading trim values from OTP Nicolas Frattaroli
2025-06-10 12:32 ` Nicolas Frattaroli
2025-06-10 12:32 ` [PATCH v6 6/7] arm64: dts: rockchip: Add thermal nodes to RK3576 Nicolas Frattaroli
2025-06-10 12:32 ` Nicolas Frattaroli
2025-06-10 12:32 ` [PATCH v6 7/7] arm64: dts: rockchip: Add thermal trim OTP and tsadc nodes Nicolas Frattaroli
2025-06-10 12:32 ` Nicolas Frattaroli
2025-07-16 20:12 ` [PATCH v6 0/7] RK3576 thermal sensor support, including OTP trim adjustments Daniel Lezcano
2025-07-16 20:12 ` Daniel Lezcano
2025-07-17 7:21 ` Heiko Stübner
2025-07-17 7:21 ` Heiko Stübner
2025-07-17 8:20 ` Daniel Lezcano
2025-07-17 8:20 ` Daniel Lezcano
2025-07-31 7:33 ` Alexey Charkov
2025-07-31 7:33 ` Alexey Charkov
2025-07-31 8:11 ` Heiko Stübner
2025-07-31 8:11 ` Heiko Stübner
2025-07-31 13:27 ` Sebastian Reichel
2025-07-31 13:27 ` Sebastian Reichel
2025-07-31 13:45 ` Heiko Stübner
2025-07-31 13:45 ` Heiko Stübner
2025-08-11 7:52 ` (subset) " Heiko Stuebner
2025-08-11 7:52 ` Heiko Stuebner
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=7568508.DvuYhMxLoT@phil \
--to=heiko@sntech.de \
--cc=alchark@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jonas@kwiboo.se \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=lukasz.luba@arm.com \
--cc=nicolas.frattaroli@collabora.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=rui.zhang@intel.com \
--cc=sebastian.reichel@collabora.com \
/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.