From: "Erim, Salih" <Salih.Erim@amd.com>
To: "Simek, Michal" <michal.simek@amd.com>,
Jonathan Cameron <jic23@kernel.org>
Cc: "Sean Anderson" <sean.anderson@linux.dev>,
"O'Griofa, Conall" <conall.ogriofa@amd.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Andy Shevchenko" <andy@kernel.org>,
"Manish Narani" <manish.narani@xilinx.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] iio: xilinx-ams: Unmask interrupts after updating alarms
Date: Wed, 30 Jul 2025 10:55:30 +0000 [thread overview]
Message-ID: <IA1PR12MB7736A3924239D1EF35DAED089F24A@IA1PR12MB7736.namprd12.prod.outlook.com> (raw)
In-Reply-To: <69a99252-4f1e-4197-8914-a6fc1c6c7027@amd.com>
[AMD Official Use Only - AMD Internal Distribution Only]
Hi,
I am really busy right now. I will look into this within next week.
Regards,
Salih.
> -----Original Message-----
> From: Simek, Michal <michal.simek@amd.com>
> Sent: Monday, July 28, 2025 6:55 AM
> To: Jonathan Cameron <jic23@kernel.org>
> Cc: Sean Anderson <sean.anderson@linux.dev>; Erim, Salih
> <Salih.Erim@amd.com>; O'Griofa, Conall <conall.ogriofa@amd.com>; 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; 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
>
>
>
> On 7/27/25 17:43, Jonathan Cameron wrote:
> > On Fri, 25 Jul 2025 06:47:16 +0200
> > Michal Simek <michal.simek@amd.com> wrote:
> >
> >> On 7/24/25 17:32, Jonathan Cameron wrote:
> >>> 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.
> >>
> >> Anand left some time ago. Salih or Conall should be able to provide some input.
> >>
> >> Thanks,
> >> Michal
> >>
> >
> > Hi Michal,
> >
> > Thanks for letting me know. Would be good to have a MAINTAINERS
> > update patch to remove Anand + ideally add someone else. If not to
> > mark it orphaned (will still be covered by the top level IIO entry).
>
> Salih: Can you please send a patch for it?
>
> It is also covered my fragment that's why you don't need to explicitly add me there.
>
> Thanks,
> Michal
>
>
next prev parent reply other threads:[~2025-07-30 10:55 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
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 [this message]
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=IA1PR12MB7736A3924239D1EF35DAED089F24A@IA1PR12MB7736.namprd12.prod.outlook.com \
--to=salih.erim@amd.com \
--cc=andy@kernel.org \
--cc=conall.ogriofa@amd.com \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).