All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Yangtao Li <frank.li@vivo.com>
Cc: "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-kernel@vger.kernel.org
Subject: Re: [PATCH v4 01/21] genirq/devres: Add devm_request_threaded_irq_probe() and devm_request_irq_probe()
Date: Mon, 10 Jul 2023 14:25:24 +0200	[thread overview]
Message-ID: <CAMuHMdXx7h47cOg8AJysbS_ohT=SfRsXW+vRUh+KiOPEsXNfnA@mail.gmail.com> (raw)
In-Reply-To: <20230710095926.15614-1-frank.li@vivo.com>

Hi Yangtao,

On Mon, Jul 10, 2023 at 12:05 PM Yangtao Li <frank.li@vivo.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 add devm_request_threaded_irq_probe() and devm_request_irq_probe(),
> 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>

Thanks for your patch!

> --- a/include/linux/interrupt.h
> +++ b/include/linux/interrupt.h
> @@ -201,6 +201,21 @@ extern void free_percpu_nmi(unsigned int irq, void __percpu *percpu_dev_id);
>
>  struct device;
>
> +extern int __must_check
> +devm_request_threaded_irq_probe(struct device *dev, unsigned int irq,
> +                             irq_handler_t handler, irq_handler_t thread_fn,
> +                             unsigned long irqflags, const char *devname,
> +                             void *dev_id, const char *info);
> +
> +static inline int __must_check
> +devm_request_irq_probe(struct device *dev, unsigned int irq,
> +                      irq_handler_t handler, unsigned long irqflags,
> +                      const char *devname, void *dev_id, const char *info)
> +{
> +       return devm_request_threaded_irq_probe(dev, irq, handler, NULL, irqflags,
> +                                        devname, dev_id, info);
> +}
> +
>  extern int __must_check
>  devm_request_threaded_irq(struct device *dev, unsigned int irq,
>                           irq_handler_t handler, irq_handler_t thread_fn,
> diff --git a/kernel/irq/devres.c b/kernel/irq/devres.c
> index f6e5515ee077..43a40d6e2e0b 100644
> --- a/kernel/irq/devres.c
> +++ b/kernel/irq/devres.c
> @@ -79,6 +79,46 @@ int devm_request_threaded_irq(struct device *dev, unsigned int irq,
>  }
>  EXPORT_SYMBOL(devm_request_threaded_irq);
>
> +/**
> + *     devm_request_threaded_irq_probe - allocate an interrupt line for a managed device
> + *     @dev: device to request interrupt for
> + *     @irq: Interrupt line to allocate
> + *     @handler: Function to be called when the IRQ occurs
> + *     @thread_fn: function to be called in a threaded interrupt context. NULL
> + *                 for devices which handle everything in @handler
> + *     @irqflags: Interrupt type flags
> + *     @devname: An ascii name for the claiming device, dev_name(dev) if NULL
> + *     @dev_id: A cookie passed back to the handler function
> + *     @info: Optional additional error log
> + *
> + *     This is a variant of the devm_request_threaded_irq function.
> + *     It will print an error message by default when the request fails,
> + *     and the consumer can add a special error msg.
> + *
> + *     Except for the extra @dev argument, this function takes the

... extra @dev and @info arguments, ...

> + *     same arguments and performs the same function as
> + *     request_threaded_irq().  IRQs requested with this function will be

But probably you want to compare with devm_request_threaded_irq()
instead of with request_threaded_irq()?
I.e. "... extra @info argument..." above.

> + *     automatically freed on driver detach.
> + *
> + *     If an IRQ allocated with this function needs to be freed
> + *     separately, devm_free_irq() must be used.
> + */
> +int devm_request_threaded_irq_probe(struct device *dev, unsigned int irq,
> +                                   irq_handler_t handler, irq_handler_t thread_fn,
> +                                   unsigned long irqflags, const char *devname,
> +                                   void *dev_id, const char *info)
> +{
> +       int rc;
> +
> +       rc = devm_request_threaded_irq(dev, irq, handler, NULL, irqflags, devname, dev_id);
> +       if (rc)
> +               return dev_err_probe(dev, rc, "Failed to request %sinterrupt %u %s %s\n",
> +                                    thread_fn ? "threaded " : "", irq, devname ? : dev_name(dev),
> +                                    info ? : "");
> +       return 0;
> +}
> +EXPORT_SYMBOL(devm_request_threaded_irq_probe);
> +
>  /**
>   *     devm_request_any_context_irq - allocate an interrupt line for a managed device
>   *     @dev: device to request interrupt for

With the above fixed:
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  parent reply	other threads:[~2023-07-10 12:25 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10  9:59 [PATCH v4 01/21] genirq/devres: Add devm_request_threaded_irq_probe() and devm_request_irq_probe() Yangtao Li
2023-07-10  9:59 ` [PATCH v4 02/21] thermal/drivers/sun8i: convert to use devm_request*_irq_probe() Yangtao Li
2023-07-10  9:59   ` Yangtao Li
2023-07-11 17:57   ` Jernej Škrabec
2023-07-11 17:57     ` Jernej Škrabec
2023-07-10  9:59 ` [PATCH v4 03/21] thermal/drivers/armada: " Yangtao Li
2023-07-10  9:59 ` [PATCH v4 04/21] thermal/drivers/broadcom: " Yangtao Li
2023-07-10  9:59   ` Yangtao Li
2023-07-10  9:59 ` [PATCH v4 05/21] thermal/drivers/tegra: " Yangtao Li
2023-07-10 13:16   ` Thierry Reding
2023-07-10 13:55     ` Krzysztof Kozlowski
2023-07-10  9:59 ` [PATCH v4 06/21] thermal/drivers/db8500: " Yangtao Li
2023-07-10 11:25   ` Dmitry Baryshkov
2023-07-10 11:30     ` Yangtao Li
2023-07-10 11:40       ` Dmitry Baryshkov
2023-07-10  9:59 ` [PATCH v4 07/21] thermal/drivers/rcar: " Yangtao Li
2023-07-10 12:27   ` Geert Uytterhoeven
2023-07-10  9:59 ` [PATCH v4 08/21] thermal/drivers/qcom/temp-alarm: " Yangtao Li
2023-07-10 11:26   ` Dmitry Baryshkov
2023-07-10  9:59 ` [PATCH v4 09/21] thermal: intel: int340x: processor_thermal: " Yangtao Li
2023-07-10 17:28   ` Rafael J. Wysocki
2023-07-10  9:59 ` [PATCH v4 10/21] thermal/drivers/exynos: " Yangtao Li
2023-07-10  9:59   ` Yangtao Li
2023-07-10 10:14   ` Krzysztof Kozlowski
2023-07-10 10:14     ` Krzysztof Kozlowski
2023-07-10  9:59 ` [PATCH v4 11/21] thermal/drivers/hisi: " Yangtao Li
2023-07-10  9:59 ` [PATCH v4 12/21] thermal/drivers/rockchip: " Yangtao Li
2023-07-10  9:59   ` Yangtao Li
2023-07-10  9:59   ` Yangtao Li
2023-07-10 11:05   ` Heiko Stuebner
2023-07-10 11:05     ` Heiko Stuebner
2023-07-10 11:05     ` Heiko Stuebner
2023-07-10  9:59 ` [PATCH v4 13/21] drivers/thermal/rcar_gen3_thermal: " Yangtao Li
2023-07-10 12:27   ` Geert Uytterhoeven
2023-07-10  9:59 ` [PATCH v4 14/21] thermal/drivers/mediatek/lvts_thermal: " Yangtao Li
2023-07-10  9:59   ` Yangtao Li
2023-07-11  8:04   ` AngeloGioacchino Del Regno
2023-07-11  8:04     ` AngeloGioacchino Del Regno
2023-07-10  9:59 ` [PATCH v4 15/21] thermal: max77620: " Yangtao Li
2023-07-10  9:59 ` [PATCH v4 16/21] thermal/drivers/intel/bxt_pmic: " Yangtao Li
2023-07-10  9:59 ` [PATCH v4 17/21] thermal/drivers/stm: " Yangtao Li
2023-07-10  9:59   ` Yangtao Li
2023-07-10  9:59 ` [PATCH v4 18/21] thermal/drivers/qcom/tsens-v0_1: " Yangtao Li
2023-07-10 11:26   ` Dmitry Baryshkov
2023-07-10  9:59 ` [PATCH v4 19/21] thermal: qcom-spmi-adc-tm5: " Yangtao Li
2023-07-10 11:27   ` Dmitry Baryshkov
2023-07-10  9:59 ` [PATCH v4 20/21] thermal/drivers/uniphier: " Yangtao Li
2023-07-10  9:59   ` Yangtao Li
2023-07-10  9:59 ` [PATCH v4 21/21] thermal/drivers/imx: " Yangtao Li
2023-07-10  9:59   ` Yangtao Li
2023-07-10 12:25 ` Geert Uytterhoeven [this message]
2023-07-10 12:41   ` [PATCH v4 01/21] genirq/devres: Add devm_request_threaded_irq_probe() and devm_request_irq_probe() Jonathan Cameron

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='CAMuHMdXx7h47cOg8AJysbS_ohT=SfRsXW+vRUh+KiOPEsXNfnA@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=frank.li@vivo.com \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=u.kleine-koenig@pengutronix.de \
    /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.