mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Binbin Zhou <zhoubinbin@loongson.cn>
To: Liu Dalin <liudalin@kylinsec.com.cn>,
	alexandre.belloni@bootlin.com, wangming01@loongson.cn
Cc: chenhuacai@kernel.org, gaojuxin@loongson.cn, git@xen0n.name,
	jiaxun.yang@flygoat.com, keguang.zhang@gmail.com,
	lixuefeng@loongson.cn, linux-rtc@vger.kernel.org,
	linux-kernel@vger.kernel.org, zhoubb.aaron@gmail.com
Subject: Re: [PATCH] rtc: loongson: Add missing alarm notifications for ACPI RTC events
Date: Thu, 8 May 2025 11:12:32 +0800	[thread overview]
Message-ID: <2fa3740a-9181-40bf-9b1a-eeb6ffc6f23f@loongson.cn> (raw)
In-Reply-To: <20250429062736.982039-1-liudalin@kylinsec.com.cn>

Hi Dalin:

Thanks for your patch.

On 2025/4/29 14:27, Liu Dalin wrote:
> When an application sets and enables an alarm on Loongson RTC devices,
> the alarm notification fails to propagate to userspace because the
> ACPI event handler omits calling rtc_update_irq().
>
> As a result, processes waiting via select() or poll() on RTC device
> files fail to receive alarm notifications.
>
> Fixes: 1b733a9ebc3d ("rtc: Add rtc driver for the Loongson family chips")
> Signed-off-by: Liu Dalin <liudalin@kylinsec.com.cn>
> ---
>   drivers/rtc/rtc-loongson.c | 2 ++
>   1 file changed, 2 insertions(+)
>
> diff --git a/drivers/rtc/rtc-loongson.c b/drivers/rtc/rtc-loongson.c
> index 97e5625c064c..0c573f198f63 100644
> --- a/drivers/rtc/rtc-loongson.c
> +++ b/drivers/rtc/rtc-loongson.c
> @@ -129,6 +129,8 @@ static u32 loongson_rtc_handler(void *id)
>   {
>   	struct loongson_rtc_priv *priv = (struct loongson_rtc_priv *)id;
>   
> +	rtc_update_irq(priv->rtcdev, 1, RTC_AF | RTC_IRQF);
> +
While testing the patch, I noticed that interrupts are triggered 
multiple times (/proc/interrupt), not sure if you have the same issue.

I think we need a similar operation to loongson_rtc_isr() to clear the 
interrupt:
regmap_write(priv->regmap, TOY_MATCH0_REG, 0);
>   	spin_lock(&priv->lock);
>   	/* Disable RTC alarm wakeup and interrupt */
>   	writel(readl(priv->pm_base + PM1_EN_REG) & ~RTC_EN,
Thanks.
Binbin


  reply	other threads:[~2025-05-08  3:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-29  6:27 Liu Dalin
2025-05-08  3:12 ` Binbin Zhou [this message]
2025-05-08  6:43   ` liudalin
     [not found]   ` <58BBF92742F0D0E1+2025050814202393211321@kylinos.com.cn>
2025-05-08  6:48     ` Binbin Zhou
2025-05-09  1:40 ` [PATCH V1] " Liu Dalin
2025-05-09  7:12   ` Binbin Zhou
2025-05-09  8:06     ` Liu Dalin
2025-05-09  8:27       ` Binbin Zhou
2025-05-09  8:44 ` [PATCH V2] " Liu Dalin
2025-05-13  7:32   ` Binbin Zhou
2025-05-24 22:28   ` Alexandre Belloni
  -- strict thread matches above, loose matches on Subject: below --
2025-04-28  2:59 [PATCH] " Liu Dalin

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=2fa3740a-9181-40bf-9b1a-eeb6ffc6f23f@loongson.cn \
    --to=zhoubinbin@loongson.cn \
    --cc=alexandre.belloni@bootlin.com \
    --cc=chenhuacai@kernel.org \
    --cc=gaojuxin@loongson.cn \
    --cc=git@xen0n.name \
    --cc=jiaxun.yang@flygoat.com \
    --cc=keguang.zhang@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=liudalin@kylinsec.com.cn \
    --cc=lixuefeng@loongson.cn \
    --cc=wangming01@loongson.cn \
    --cc=zhoubb.aaron@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®