From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: Guangqing Zhu <zhuguangqing83@gmail.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] extcon: maxim: Fix missing IRQF_ONESHOT as only threaded handler
Date: Sun, 18 Apr 2021 17:39:51 +0200 [thread overview]
Message-ID: <005ae6c3-2cd0-4c1e-b820-2674cb758de9@canonical.com> (raw)
In-Reply-To: <4479c7f8-6a80-8d30-0602-b8cc10dd901e@gmail.com>
On 18/04/2021 16:41, Guangqing Zhu wrote:
>
>
> On 16/04/2021 16:43, Krzysztof Kozlowski wrote:
>> On 15/04/2021 13:36, zhuguangqing83@gmail.com wrote:
>>> From: Guangqing Zhu <zhuguangqing83@gmail.com>
>>>
>>> Coccinelle noticed:
>>> 1. drivers/extcon/extcon-max14577.c:699:8-33: ERROR: Threaded IRQ with
>>> no primary handler requested without IRQF_ONESHOT
>>> 2. drivers/extcon/extcon-max77693.c:1143:8-33: ERROR: Threaded IRQ with
>>> no primary handler requested without IRQF_ONESHOT
>>> 3. drivers/extcon/extcon-max77843.c:907:8-33: ERROR: Threaded IRQ with
>>> no primary handler requested without IRQF_ONESHOT
>>> 4. drivers/extcon/extcon-max8997.c:665:8-28: ERROR: Threaded IRQ with
>>> no primary handler requested without IRQF_ONESHOT
>>>
>>> Signed-off-by: Guangqing Zhu <zhuguangqing83@gmail.com>
>>> ---
>>> drivers/extcon/extcon-max14577.c | 2 +-
>>> drivers/extcon/extcon-max77693.c | 2 +-
>>> drivers/extcon/extcon-max77843.c | 3 ++-
>>> drivers/extcon/extcon-max8997.c | 2 +-
>>> 4 files changed, 5 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/drivers/extcon/extcon-max14577.c b/drivers/extcon/extcon-max14577.c
>>> index ace523924e58..af15a9e00ee9 100644
>>> --- a/drivers/extcon/extcon-max14577.c
>>> +++ b/drivers/extcon/extcon-max14577.c
>>> @@ -698,7 +698,7 @@ static int max14577_muic_probe(struct platform_device *pdev)
>>>
>>> ret = devm_request_threaded_irq(&pdev->dev, virq, NULL,
>>> max14577_muic_irq_handler,
>>> - IRQF_NO_SUSPEND,
>>> + IRQF_NO_SUSPEND | IRQF_ONESHOT,
>>
>> The same with all other patches for IRQF_ONESHOT which are send recently:
>> 1. On what board did you test it?
>
> I didn't test it.
>
>> 2. Is this just blind patch from Coccinelle without investigation
>> whether it is needed (hint: it's not needed here, it does not use
>> default primary handler).
>
> I found the error notice from Coccinelle and I saw the code. Maybe
> I'm mistaken, I think it's needed here. Because handler == NULL and
> thread_fn != NULL, it use irq_default_primary_handler() in
> request_threaded_irq().
No, the primary handler is nested, not default one. Otherwise it would
have absolutely never worked. Therefore you are not fixing anything,
except Coccinelle report.
Best regards,
Krzysztof
prev parent reply other threads:[~2021-04-18 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 11:36 zhuguangqing83
2021-04-16 8:43 ` Krzysztof Kozlowski
2021-04-18 14:41 ` Guangqing Zhu
2021-04-18 15:39 ` Krzysztof Kozlowski [this message]
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=005ae6c3-2cd0-4c1e-b820-2674cb758de9@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=b.zolnierkie@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=zhuguangqing83@gmail.com \
/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
all inboxes | Powered by JetHome®