From: Patrice CHOTARD <patrice.chotard@foss.st.com>
To: Tian Tao <tiantao6@hisilicon.com>, <a.zummo@towertech.it>,
<alexandre.belloni@bootlin.com>
Cc: <linux-arm-kernel@lists.infradead.org>, <linux-rtc@vger.kernel.org>
Subject: Re: [PATCH] rtc: st-lpc: move to use request_irq by IRQF_NO_AUTOEN flag
Date: Thu, 8 Apr 2021 10:04:05 +0200 [thread overview]
Message-ID: <1df61277-23b0-0351-7373-2e1e5c9f6651@foss.st.com> (raw)
In-Reply-To: <1617761937-58318-1-git-send-email-tiantao6@hisilicon.com>
Hi Tian
On 4/7/21 4:18 AM, Tian Tao wrote:
> disable_irq() after request_irq() still has a time gap in which
> interrupts can come. request_irq() with IRQF_NO_AUTOEN flag will
> disable IRQ auto-enable because of requesting.
>
> this patch is made base on "add IRQF_NO_AUTOEN for request_irq" which
> is being merged: https://lore.kernel.org/patchwork/patch/1388765/
>
> Signed-off-by: Tian Tao <tiantao6@hisilicon.com>
> ---
> drivers/rtc/rtc-st-lpc.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/rtc/rtc-st-lpc.c b/drivers/rtc/rtc-st-lpc.c
> index bdb20f6..2df2179 100644
> --- a/drivers/rtc/rtc-st-lpc.c
> +++ b/drivers/rtc/rtc-st-lpc.c
> @@ -218,15 +218,14 @@ static int st_rtc_probe(struct platform_device *pdev)
> return -EINVAL;
> }
>
> - ret = devm_request_irq(&pdev->dev, rtc->irq, st_rtc_handler, 0,
> - pdev->name, rtc);
> + ret = devm_request_irq(&pdev->dev, rtc->irq, st_rtc_handler,
> + IRQF_NO_AUTOEN, pdev->name, rtc);
> if (ret) {
> dev_err(&pdev->dev, "Failed to request irq %i\n", rtc->irq);
> return ret;
> }
>
> enable_irq_wake(rtc->irq);
> - disable_irq(rtc->irq);
>
> rtc->clk = clk_get(&pdev->dev, NULL);
> if (IS_ERR(rtc->clk)) {
>
Reviewed-by: Patrice Chotard <patrice.chotard@foss.st.com>
Thanks
Patrice
next prev parent reply other threads:[~2021-04-08 8:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 2:18 [PATCH] rtc: st-lpc: move to use request_irq by IRQF_NO_AUTOEN flag Tian Tao
2021-04-08 8:04 ` Patrice CHOTARD [this message]
2021-04-16 23:04 ` Alexandre Belloni
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=1df61277-23b0-0351-7373-2e1e5c9f6651@foss.st.com \
--to=patrice.chotard@foss.st.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rtc@vger.kernel.org \
--cc=tiantao6@hisilicon.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;
as well as URLs for NNTP newsgroup(s).