All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Zhang Rui <rui.zhang@intel.com>,
	Lukasz Luba <lukasz.luba@arm.com>,
	Nicolas Frattaroli <nicolas.frattaroli@collabora.com>,
	Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	kernel@collabora.com,
	Sebastian Reichel <sebastian.reichel@collabora.com>
Subject: Re: [PATCH] thermal/drivers/rockchip: Shut up eFuse prober defer warning
Date: Tue, 17 Mar 2026 16:14:45 +0100	[thread overview]
Message-ID: <3330199.5fSG56mABF@phil> (raw)
In-Reply-To: <20260317-rockchip-thermal-trim-warning-v1-1-01bc4bda75e9@collabora.com>

Am Dienstag, 17. März 2026, 15:31:30 Mitteleuropäische Normalzeit schrieb Sebastian Reichel:
> Shut up the following message printed at error level on ArmSom Sige5:
> 
> rockchip-thermal 2ae70000.tsadc: failed reading trim of sensor 0: -EPROBE_DEFER
> 
> Fixes: ae332ec0009d ("thermal/drivers/rockchip: Support reading trim values from OTP")
> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>

Reviewed-by: Heiko Stuebner <heiko@sntech.de>

> ---
>  drivers/thermal/rockchip_thermal.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/drivers/thermal/rockchip_thermal.c b/drivers/thermal/rockchip_thermal.c
> index c49ddf70f86e..2a40339de0d0 100644
> --- a/drivers/thermal/rockchip_thermal.c
> +++ b/drivers/thermal/rockchip_thermal.c
> @@ -1638,8 +1638,7 @@ rockchip_thermal_register_sensor(struct platform_device *pdev,
>  	if (tsadc->get_trim_code && sensor->of_node) {
>  		error = rockchip_get_efuse_value(sensor->of_node, "trim", &trim);
>  		if (error < 0 && error != -ENOENT) {
> -			dev_err(dev, "failed reading trim of sensor %d: %pe\n",
> -				id, ERR_PTR(error));
> +			dev_err_probe(dev, error, "failed reading trim of sensor %d\n", id);
>  			return error;
>  		}
>  		if (trim) {
> 
> ---
> base-commit: 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f
> change-id: 20260317-rockchip-thermal-trim-warning-cd0072aa2f46
> 
> Best regards,
> 






WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Zhang Rui <rui.zhang@intel.com>,
	Lukasz Luba <lukasz.luba@arm.com>,
	Nicolas Frattaroli <nicolas.frattaroli@collabora.com>,
	Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	kernel@collabora.com,
	Sebastian Reichel <sebastian.reichel@collabora.com>
Subject: Re: [PATCH] thermal/drivers/rockchip: Shut up eFuse prober defer warning
Date: Tue, 17 Mar 2026 16:14:45 +0100	[thread overview]
Message-ID: <3330199.5fSG56mABF@phil> (raw)
In-Reply-To: <20260317-rockchip-thermal-trim-warning-v1-1-01bc4bda75e9@collabora.com>

Am Dienstag, 17. März 2026, 15:31:30 Mitteleuropäische Normalzeit schrieb Sebastian Reichel:
> Shut up the following message printed at error level on ArmSom Sige5:
> 
> rockchip-thermal 2ae70000.tsadc: failed reading trim of sensor 0: -EPROBE_DEFER
> 
> Fixes: ae332ec0009d ("thermal/drivers/rockchip: Support reading trim values from OTP")
> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>

Reviewed-by: Heiko Stuebner <heiko@sntech.de>

> ---
>  drivers/thermal/rockchip_thermal.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/drivers/thermal/rockchip_thermal.c b/drivers/thermal/rockchip_thermal.c
> index c49ddf70f86e..2a40339de0d0 100644
> --- a/drivers/thermal/rockchip_thermal.c
> +++ b/drivers/thermal/rockchip_thermal.c
> @@ -1638,8 +1638,7 @@ rockchip_thermal_register_sensor(struct platform_device *pdev,
>  	if (tsadc->get_trim_code && sensor->of_node) {
>  		error = rockchip_get_efuse_value(sensor->of_node, "trim", &trim);
>  		if (error < 0 && error != -ENOENT) {
> -			dev_err(dev, "failed reading trim of sensor %d: %pe\n",
> -				id, ERR_PTR(error));
> +			dev_err_probe(dev, error, "failed reading trim of sensor %d\n", id);
>  			return error;
>  		}
>  		if (trim) {
> 
> ---
> base-commit: 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f
> change-id: 20260317-rockchip-thermal-trim-warning-cd0072aa2f46
> 
> Best regards,
> 





_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

  reply	other threads:[~2026-03-17 15:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17 14:31 [PATCH] thermal/drivers/rockchip: Shut up eFuse prober defer warning Sebastian Reichel
2026-03-17 14:31 ` Sebastian Reichel
2026-03-17 15:14 ` Heiko Stuebner [this message]
2026-03-17 15:14   ` 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=3330199.5fSG56mABF@phil \
    --to=heiko@sntech.de \
    --cc=daniel.lezcano@linaro.org \
    --cc=kernel@collabora.com \
    --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=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.