From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: Vasily Khoruzhick <anarsoul@gmail.com>,
Yangtao Li <tiny.windzz@gmail.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Amit Kucheria <amitk@kernel.org>, Zhang Rui <rui.zhang@intel.com>,
Chen-Yu Tsai <wens@csie.org>,
Samuel Holland <samuel@sholland.org>,
Yangtao Li <frank.li@vivo.com>
Cc: "Yangtao Li" <frank.li@vivo.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 02/21] thermal/drivers/sun8i: convert to use devm_request*_irq_probe()
Date: Tue, 11 Jul 2023 19:57:26 +0200 [thread overview]
Message-ID: <2687714.mvXUDI8C0e@jernej-laptop> (raw)
In-Reply-To: <20230710095926.15614-2-frank.li@vivo.com>
Dne ponedeljek, 10. julij 2023 ob 11:59:06 CEST je Yangtao Li napisal(a):
> There are more than 700 calls to devm_request_threaded_irq method and
> more than 1000 calls to devm_request_irq method. Most drivers only
> request one interrupt resource, and these error messages are basically
> the same. If error messages are printed everywhere, more than 2000 lines
> of code can be saved by removing the msg in the driver.
>
> And tglx point out that:
>
> If we actually look at the call sites of
> devm_request_threaded_irq() then the vast majority of them print more or
> less lousy error messages. A quick grep/sed/awk/sort/uniq revealed
>
> 519 messages total (there are probably more)
>
> 352 unique messages
>
> 323 unique messages after lower casing
>
> Those 323 are mostly just variants of the same patterns with
> slight modifications in formatting and information provided.
>
> 186 of these messages do not deliver any useful information,
> e.g. "no irq", "
>
> The most useful one of all is: "could request wakeup irq: %d"
>
> So there is certainly an argument to be made that this particular
> function should print a well formatted and informative error message.
>
> It's not a general allocator like kmalloc(). It's specialized and in the
> vast majority of cases failing to request the interrupt causes the
> device probe to fail. So having proper and consistent information why
> the device cannot be used _is_ useful.
>
> So convert to use devm_request*_irq_probe() API, which ensure that all
> error handling branches print error information.
>
> In this way, when this function fails, the upper-layer functions can
> directly return an error code without missing debugging information.
> Otherwise, the error message will be printed redundantly or missing.
>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Krzysztof Kozlowski <krzk@kernel.org>
> Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
> Cc: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
> Cc: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> Signed-off-by: Yangtao Li <frank.li@vivo.com>
> ---
Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com>
Best regards,
Jernej
> drivers/thermal/sun8i_thermal.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/thermal/sun8i_thermal.c b/drivers/thermal/sun8i_thermal.c
> index 195f3c5d0b38..a952804ff993 100644
> --- a/drivers/thermal/sun8i_thermal.c
> +++ b/drivers/thermal/sun8i_thermal.c
> @@ -512,9 +512,9 @@ static int sun8i_ths_probe(struct platform_device *pdev)
> * registered yet, we deffer the registration of the interrupt to
> * the end.
> */
> - ret = devm_request_threaded_irq(dev, irq, NULL,
> - sun8i_irq_thread,
> - IRQF_ONESHOT, "ths", tmdev);
> + ret = devm_request_threaded_irq_probe(dev, irq, NULL,
> + sun8i_irq_thread,
> + IRQF_ONESHOT, "ths", tmdev, NULL);
> if (ret)
> return ret;
>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-07-11 17:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230710095926.15614-1-frank.li@vivo.com>
2023-07-10 9:59 ` [PATCH v4 02/21] thermal/drivers/sun8i: convert to use devm_request*_irq_probe() Yangtao Li
2023-07-11 17:57 ` Jernej Škrabec [this message]
2023-07-10 9:59 ` [PATCH v4 04/21] thermal/drivers/broadcom: " Yangtao Li
2023-07-10 9:59 ` [PATCH v4 10/21] thermal/drivers/exynos: " Yangtao Li
2023-07-10 10:14 ` Krzysztof Kozlowski
2023-07-10 9:59 ` [PATCH v4 12/21] thermal/drivers/rockchip: " Yangtao Li
2023-07-10 11:05 ` Heiko Stuebner
2023-07-10 9:59 ` [PATCH v4 14/21] thermal/drivers/mediatek/lvts_thermal: " Yangtao Li
2023-07-11 8:04 ` AngeloGioacchino Del Regno
2023-07-10 9:59 ` [PATCH v4 17/21] thermal/drivers/stm: " Yangtao Li
2023-07-10 9:59 ` [PATCH v4 20/21] thermal/drivers/uniphier: " Yangtao Li
2023-07-10 9:59 ` [PATCH v4 21/21] thermal/drivers/imx: " Yangtao Li
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=2687714.mvXUDI8C0e@jernej-laptop \
--to=jernej.skrabec@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=amitk@kernel.org \
--cc=anarsoul@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=daniel.lezcano@linaro.org \
--cc=frank.li@vivo.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=samuel@sholland.org \
--cc=tglx@linutronix.de \
--cc=tiny.windzz@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
--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