From: Jonathan Cameron <jic23@kernel.org>
To: Sean Anderson <sean.anderson@linux.dev>
Cc: "Anand Ashok Dumbre" <anand.ashok.dumbre@xilinx.com>,
linux-iio@vger.kernel.org,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
linux-arm-kernel@lists.infradead.org,
"Michal Simek" <michal.simek@amd.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Manish Narani" <manish.narani@xilinx.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: xilinx-ams: Unmask interrupts after updating alarms
Date: Thu, 24 Jul 2025 16:32:19 +0100 [thread overview]
Message-ID: <20250724163219.0098ced6@jic23-huawei> (raw)
In-Reply-To: <20250715002847.2035228-1-sean.anderson@linux.dev>
On Mon, 14 Jul 2025 20:28:47 -0400
Sean Anderson <sean.anderson@linux.dev> wrote:
> To convert level-triggered alarms into edge-triggered IIO events, alarms
> are masked when they are triggered. To ensure we catch subsequent
> alarms, we then periodically poll to see if the alarm is still active.
> If it isn't, we unmask it. Active but masked alarms are stored in
> current_masked_alarm.
>
> If an active alarm is disabled, it will remain set in
> current_masked_alarm until ams_unmask_worker clears it. If the alarm is
> re-enabled before ams_unmask_worker runs, then it will never be cleared
> from current_masked_alarm. This will prevent the alarm event from being
> pushed even if the alarm is still active.
>
> Fix this by recalculating current_masked_alarm immediately when enabling
> or disabling alarms.
>
> Fixes: d5c70627a794 ("iio: adc: Add Xilinx AMS driver")
> Signed-off-by: Sean Anderson <sean.anderson@linux.dev>
> ---
Anand?
This seems fine to me, but I'm not that familiar with the hardware or driver.
>
> drivers/iio/adc/xilinx-ams.c | 45 ++++++++++++++++++++----------------
> 1 file changed, 25 insertions(+), 20 deletions(-)
>
> diff --git a/drivers/iio/adc/xilinx-ams.c b/drivers/iio/adc/xilinx-ams.c
> index 76dd0343f5f7..180d4140993d 100644
> --- a/drivers/iio/adc/xilinx-ams.c
> +++ b/drivers/iio/adc/xilinx-ams.c
> @@ -389,6 +389,29 @@ static void ams_update_pl_alarm(struct ams *ams, unsigned long alarm_mask)
> ams_pl_update_reg(ams, AMS_REG_CONFIG3, AMS_REGCFG3_ALARM_MASK, cfg);
> }
>
> +static void ams_unmask(struct ams *ams)
> +{
> + unsigned int status, unmask;
> +
> + status = readl(ams->base + AMS_ISR_0);
> +
> + /* Clear those bits which are not active anymore */
> + unmask = (ams->current_masked_alarm ^ status) & ams->current_masked_alarm;
> +
> + /* Clear status of disabled alarm */
> + unmask |= ams->intr_mask;
> +
> + ams->current_masked_alarm &= status;
> +
> + /* Also clear those which are masked out anyway */
> + ams->current_masked_alarm &= ~ams->intr_mask;
> +
> + /* Clear the interrupts before we unmask them */
> + writel(unmask, ams->base + AMS_ISR_0);
> +
> + ams_update_intrmask(ams, ~AMS_ALARM_MASK, ~AMS_ALARM_MASK);
> +}
> +
> static void ams_update_alarm(struct ams *ams, unsigned long alarm_mask)
> {
> unsigned long flags;
> @@ -401,6 +424,7 @@ static void ams_update_alarm(struct ams *ams, unsigned long alarm_mask)
>
> spin_lock_irqsave(&ams->intr_lock, flags);
> ams_update_intrmask(ams, AMS_ISR0_ALARM_MASK, ~alarm_mask);
> + ams_unmask(ams);
> spin_unlock_irqrestore(&ams->intr_lock, flags);
> }
>
> @@ -1035,28 +1059,9 @@ static void ams_handle_events(struct iio_dev *indio_dev, unsigned long events)
> static void ams_unmask_worker(struct work_struct *work)
> {
> struct ams *ams = container_of(work, struct ams, ams_unmask_work.work);
> - unsigned int status, unmask;
>
> spin_lock_irq(&ams->intr_lock);
> -
> - status = readl(ams->base + AMS_ISR_0);
> -
> - /* Clear those bits which are not active anymore */
> - unmask = (ams->current_masked_alarm ^ status) & ams->current_masked_alarm;
> -
> - /* Clear status of disabled alarm */
> - unmask |= ams->intr_mask;
> -
> - ams->current_masked_alarm &= status;
> -
> - /* Also clear those which are masked out anyway */
> - ams->current_masked_alarm &= ~ams->intr_mask;
> -
> - /* Clear the interrupts before we unmask them */
> - writel(unmask, ams->base + AMS_ISR_0);
> -
> - ams_update_intrmask(ams, ~AMS_ALARM_MASK, ~AMS_ALARM_MASK);
> -
> + ams_unmask(ams);
> spin_unlock_irq(&ams->intr_lock);
>
> /* If still pending some alarm re-trigger the timer */
next prev parent reply other threads:[~2025-07-24 18:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 0:28 [PATCH] iio: xilinx-ams: Unmask interrupts after updating alarms Sean Anderson
2025-07-24 15:32 ` Jonathan Cameron [this message]
2025-07-25 4:47 ` Michal Simek
2025-07-27 15:43 ` Jonathan Cameron
2025-07-28 5:54 ` Michal Simek
2025-07-30 10:55 ` Erim, Salih
2025-08-20 11:23 ` Erim, Salih
2025-08-20 11:28 ` O'Griofa, Conall
2025-08-25 11:23 ` 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=20250724163219.0098ced6@jic23-huawei \
--to=jic23@kernel.org \
--cc=anand.ashok.dumbre@xilinx.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manish.narani@xilinx.com \
--cc=michal.simek@amd.com \
--cc=nuno.sa@analog.com \
--cc=sean.anderson@linux.dev \
/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