From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: "Yangtao Li" <frank.li@vivo.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Jonathan Cameron" <Jonathan.Cameron@Huawei.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
miquel.raynal@bootlin.com, rafael@kernel.org,
daniel.lezcano@linaro.org, amitk@kernel.org, rui.zhang@intel.com,
mmayer@broadcom.com, bcm-kernel-feedback-list@broadcom.com,
florian.fainelli@broadcom.com, tglx@linutronix.de,
matthias.bgg@gmail.com, bchihi@baylibre.com, wenst@chromium.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v3 1/5] genirq/devres: Add devm_request_threaded_irq_emsg()
Date: Wed, 5 Jul 2023 12:14:21 +0200 [thread overview]
Message-ID: <548f2a41-1f37-fe3a-6665-ae786e4c8f77@collabora.com> (raw)
In-Reply-To: <c092b860-33d5-77c0-456c-367d545e8b7f@vivo.com>
Il 05/07/23 09:43, Yangtao Li ha scritto:
> On 2023/7/5 15:30, Uwe Kleine-König wrote:
>
>> Hello,
>>
>> On Wed, Jul 05, 2023 at 10:15:37AM +0800, Jonathan Cameron wrote:
>>> On Tue, 4 Jul 2023 16:19:54 +0200
>>> Uwe Kleine-König <u.kleine-koenig@pengutronix.de> wrote:
>>>
>>>> Hello,
>>>>
>>>> On Tue, Jul 04, 2023 at 05:06:12PM +0800, Yangtao Li wrote:
>>>>> On 2023/7/4 16:48, Krzysztof Kozlowski wrote:
>>>>>> [你通常不会收到来自 krzk@kernel.org 的电子邮件。请访问 https://aka.ms
>>>>>> /LearnAboutSenderIdentification,以了解这一点为什么很重要]
>>>>>>
>>>>>> On 03/07/2023 19:43, Uwe Kleine-König wrote:
>>>>>>> Hello Krzysztof,
>>>>>>>
>>>>>>> On Mon, Jul 03, 2023 at 02:31:59PM +0200, Krzysztof Kozlowski wrote:
>>>>>>>> On 03/07/2023 11:04, Yangtao Li wrote:
>>>>>>>>> There are more than 700 calls to the devm_request_threaded_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 1000 lines of code can be saved by removing the
>>>>>>>>> msg in the driver.
>>>>>>>> ...
>>>>>>>>> +int devm_request_threaded_irq_emsg(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 *emsg)
>>>>>>>>> +{
>>>>>>>>> + int rc;
>>>>>>>>> +
>>>>>>>>> + rc = devm_request_threaded_irq(dev, irq, handler, NULL, irqflags,
>>>>>>>>> + devname, dev_id);
>>>>>>>>> + if (rc && rc != -EPROBE_DEFER) {
>>>>>>>>> + dev_err(dev, "Failed to request %sinterrupt %u %s %s: %pe\n",
>>>>>>>>> + thread_fn ? "threaded " : "", irq, devname ? :
>>>>>>>>> dev_name(dev),
>>>>>>>>> + emsg ? : "", ERR_PTR(rc));
>>>>>>>> It is open-coding dev_err_probe(). Just use dev_err_probe instead.
>>>>>>> dev_err_probe is supposed to be only called in probe functions, while
>>>>>>> devm_request_threaded_irq might be called in other contexts (e.g. when a
>>>>>>> device is opened). That's why I asked to not use dev_err_probe() in v2
>>>>>> True, but then all the callers of this function will forget to set
>>>>>> deferred probe reason.
>>>> That's another reason for letting the driver issue the error message and
>>>> not the request_irq function.
>>>>> So let's use dev_err_probe?
>>>>>
>>>>> BTW, any suggestions for names here, keep using
>>>>> devm_request_threaded_irq_emsg or change to a new name?
>>>> I would have called it devm_request_threaded_irq_verbose() which I
>>>> consider easier to understand. But maybe is just my (green)
>>>> bikeshed.
>>> If going to use dev_err_probe() internally maybe can just use
>>> devm_request_threaded_irq_probe() thus reflecting that and making
>>> it different to the devm_request_threaded_irq()?
>> I like devm_request_threaded_irq_probe(), thanks for that suggestion
>> (even though it's red :-)
>
>
> devm_request_threaded_irq_probe() also sounds good to me, :-) If there is no
> objection, I think it's time to start working on switching the api.
>
+1 on devm_request_threaded_irq_probe() name, makes sense to me, as it'd be
using the same error logic as dev_err_probe() (no prints if -EPROBE_DEFER),
and also.. this is a function that's anyway used in .probe() callbacks at
least in the *vast* majority of the cases.
Cheers,
Angelo
> 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); MBR, Yangtao
>
>
>>
>> Best regards
>> Uwe
>>
next prev parent reply other threads:[~2023-07-05 10:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 9:04 [PATCH v3 0/5] introduce devm_request_threaded_irq_emsg() Yangtao Li
2023-07-03 9:04 ` [PATCH v3 1/5] genirq/devres: Add devm_request_threaded_irq_emsg() Yangtao Li
2023-07-03 12:31 ` Krzysztof Kozlowski
2023-07-03 13:24 ` Yangtao Li
2023-07-03 13:37 ` Krzysztof Kozlowski
2023-07-03 17:43 ` Uwe Kleine-König
2023-07-04 8:48 ` Krzysztof Kozlowski
2023-07-04 9:06 ` Yangtao Li
2023-07-04 14:19 ` Uwe Kleine-König
2023-07-05 2:15 ` Jonathan Cameron
2023-07-05 7:30 ` Uwe Kleine-König
2023-07-05 7:43 ` Yangtao Li
2023-07-05 7:49 ` Yangtao Li
2023-07-05 10:14 ` AngeloGioacchino Del Regno [this message]
2023-07-03 9:04 ` [PATCH v3 2/5] thermal/drivers/armada: convert to use devm_request_threaded_irq_emsg() Yangtao Li
2023-07-04 8:46 ` Miquel Raynal
2023-07-04 14:22 ` Uwe Kleine-König
2023-07-04 14:29 ` Miquel Raynal
2023-07-03 9:04 ` [PATCH v3 3/5] thermal/drivers/brcmstb_thermal: " Yangtao Li
2023-07-03 9:04 ` [PATCH v3 4/5] thermal/drivers/db8500: " Yangtao Li
2023-07-03 9:04 ` [PATCH v3 5/5] thermal/drivers/mediatek/lvts_thermal: " Yangtao Li
2023-07-03 11:47 ` [PATCH v3 0/5] introduce devm_request_threaded_irq_emsg() 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=548f2a41-1f37-fe3a-6665-ae786e4c8f77@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=amitk@kernel.org \
--cc=bchihi@baylibre.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=daniel.lezcano@linaro.org \
--cc=florian.fainelli@broadcom.com \
--cc=frank.li@vivo.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=mmayer@broadcom.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=tglx@linutronix.de \
--cc=u.kleine-koenig@pengutronix.de \
--cc=wenst@chromium.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