From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Ondrej Jirman <megous@megous.com>
Cc: linux-sunxi@googlegroups.com,
Amit Kucheria <amit.kucheria@verdurent.com>,
"open list:ALLWINNER THERMAL DRIVER" <linux-pm@vger.kernel.org>,
Yangtao Li <tiny.windzz@gmail.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
open list <linux-kernel@vger.kernel.org>,
Maxime Ripard <mripard@kernel.org>,
Vasily Khoruzhick <anarsoul@gmail.com>,
Chen-Yu Tsai <wens@csie.org>, Zhang Rui <rui.zhang@intel.com>,
"moderated list:ARM/Allwinner sunXi SoC support"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] thermal: sun8i: Be loud when probe fails
Date: Wed, 8 Jul 2020 12:03:01 +0100 [thread overview]
Message-ID: <20200708110301.GB1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <20200708105527.868987-1-megous@megous.com>
On Wed, Jul 08, 2020 at 12:55:27PM +0200, Ondrej Jirman wrote:
> I noticed several mobile Linux distributions failing to enable the
> thermal regulation correctly, because the kernel is silent
> when thermal driver fails to probe. Add enough error reporting
> to debug issues and warn users in case thermal sensor is failing
> to probe.
>
> Failing to notify users means, that SoC can easily overheat under
> load.
>
> Signed-off-by: Ondrej Jirman <megous@megous.com>
> ---
> drivers/thermal/sun8i_thermal.c | 55 ++++++++++++++++++++++++++-------
> 1 file changed, 43 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/thermal/sun8i_thermal.c b/drivers/thermal/sun8i_thermal.c
> index 74d73be16496..9065e79ae743 100644
> --- a/drivers/thermal/sun8i_thermal.c
> +++ b/drivers/thermal/sun8i_thermal.c
> @@ -287,8 +287,12 @@ static int sun8i_ths_calibrate(struct ths_device *tmdev)
>
> calcell = devm_nvmem_cell_get(dev, "calibration");
> if (IS_ERR(calcell)) {
> + dev_err(dev, "Failed to get calibration nvmem cell (%ld)\n",
> + PTR_ERR(calcell));
Consider using:
dev_err(dev, "Failed to get calibration nvmem cell (%pe)\n",
calcell);
which means the kernel can print the symbolic errno value.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2020-07-08 11:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 10:55 [PATCH] thermal: sun8i: Be loud when probe fails Ondrej Jirman
2020-07-08 11:03 ` Russell King - ARM Linux admin [this message]
2020-07-08 11:10 ` Ondřej Jirman
2020-07-20 7:55 ` Icenowy Zheng
2020-07-20 8:28 ` Russell King - ARM Linux admin
2020-07-08 11:55 ` Frank Lee
2020-07-08 13:21 ` Ondřej Jirman
2020-07-08 13:42 ` Robin Murphy
2020-07-08 13:33 ` Ondřej Jirman
2020-07-08 12:25 ` Maxime Ripard
2020-07-08 13:29 ` Ondřej Jirman
2020-07-08 13:36 ` Maxime Ripard
2020-07-08 13:44 ` Ondřej Jirman
2020-07-08 13:57 ` Maxime Ripard
2020-07-12 23:29 ` Ondřej Jirman
2020-07-23 15:20 ` Maxime Ripard
2020-07-08 13:29 ` Maxime Ripard
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=20200708110301.GB1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=amit.kucheria@verdurent.com \
--cc=anarsoul@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=megous@megous.com \
--cc=mripard@kernel.org \
--cc=rui.zhang@intel.com \
--cc=tiny.windzz@gmail.com \
--cc=wens@csie.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).