[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0h7bvAqyKzV_SsKaTc3JV0R01y0k6aaieAk7iRcbN-eCg@mail.gmail.com>
Date: Mon, 10 Jul 2023 19:28:09 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Yangtao Li <frank.li@...o.com>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Amit Kucheria <amitk@...nel.org>,
Zhang Rui <rui.zhang@...el.com>,
Thomas Gleixner <tglx@...utronix.de>,
Krzysztof Kozlowski <krzk@...nel.org>,
Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>,
Jonathan Cameron <Jonathan.Cameron@...wei.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 09/21] thermal: intel: int340x: processor_thermal:
convert to use devm_request*_irq_probe()
On Mon, Jul 10, 2023 at 12:00 PM Yangtao Li <frank.li@...o.com> wrote:
>
> 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@...utronix.de>
> Cc: Krzysztof Kozlowski <krzk@...nel.org>
> Cc: "Uwe Kleine-König" <u.kleine-koenig@...gutronix.de>
> Cc: Jonathan Cameron <Jonathan.Cameron@...wei.com>
> Cc: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
> Signed-off-by: Yangtao Li <frank.li@...o.com>
Acked-by: Rafael J. Wysocki <rafael@...nel.org>
> ---
> .../intel/int340x_thermal/processor_thermal_device_pci.c | 9 +++------
> 1 file changed, 3 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/thermal/intel/int340x_thermal/processor_thermal_device_pci.c b/drivers/thermal/intel/int340x_thermal/processor_thermal_device_pci.c
> index 0d1e98007270..ee766904b314 100644
> --- a/drivers/thermal/intel/int340x_thermal/processor_thermal_device_pci.c
> +++ b/drivers/thermal/intel/int340x_thermal/processor_thermal_device_pci.c
> @@ -258,13 +258,10 @@ static int proc_thermal_pci_probe(struct pci_dev *pdev, const struct pci_device_
> irq_flag = IRQF_SHARED;
>
> irq = pci_irq_vector(pdev, 0);
> - ret = devm_request_threaded_irq(&pdev->dev, irq,
> - proc_thermal_irq_handler, NULL,
> - irq_flag, KBUILD_MODNAME, pci_info);
> - if (ret) {
> - dev_err(&pdev->dev, "Request IRQ %d failed\n", pdev->irq);
> + ret = devm_request_threaded_irq_probe(&pdev->dev, irq, proc_thermal_irq_handler,
> + NULL, irq_flag, KBUILD_MODNAME, pci_info, NULL);
> + if (ret)
> goto err_free_vectors;
> - }
>
> ret = thermal_zone_device_enable(pci_info->tzone);
> if (ret)
> --
> 2.39.0
>
Powered by blists - more mailing lists