From: "Kazuhiro Abe (Fujitsu)" <fj1078ii@fujitsu.com>
To: 'Will Deacon' <will@kernel.org>, Hanjun Guo <guohanjun@huawei.com>
Cc: Lorenzo Pieralisi <lpieralisi@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ilkka Koskinen <ilkka@os.amperecomputing.com>,
Catalin Marinas <catalin.marinas@arm.com>,
"Koichi Okuno (Fujitsu)" <fj2767dz@fujitsu.com>
Subject: RE: [PATCH v4] ACPI: AGDI: Add interrupt signaling mode support
Date: Thu, 6 Nov 2025 01:19:07 +0000 [thread overview]
Message-ID: <OSAPR01MB766951191ACB95ABCD7DD319D5C2A@OSAPR01MB7669.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <aQokdBkjFqw9ZGRt@willie-the-truck>
Hi Will,
> [You don't often get email from will@kernel.org. Learn why this is important at
> https://aka.ms/LearnAboutSenderIdentification ]
>
> On Mon, Oct 20, 2025 at 09:23:05PM +0800, Hanjun Guo wrote:
> > On 2025/10/17 15:39, Kazuhiro Abe wrote:
> > > AGDI has two types of signaling modes: SDEI and interrupt.
> > > Currently, the AGDI driver only supports SDEI.
> > > Therefore, add support for interrupt signaling mode The interrupt
> > > vector is retrieved from the AGDI table, and call panic function
> > > when an interrupt occurs.
> > >
> > > Reviewed-by: Ilkka Koskinen <ilkka@os.amperecomputing.com>
> > > Signed-off-by: Kazuhiro Abe <fj1078ii@aa.jp.fujitsu.com>
> > > ---
> > > Hanjun, I have addressed all your comments.
> > > Please review them.
> > >
> > > v3->v4
> > > - Add a comment to the flags member.
> > > - Fix agdi_interrupt_probe.
> > > - Fix agdi_interrupt_remove.
> > > - Add space in struct initializsation.
> > > - Delete curly braces.
> >
> > Looks good to me,
> >
> > Acked-by: Hanjun Guo <guohanjun@huawei.com>
>
> I wasn't cc'd on the original patch but I couldn't figure out why it uses
> IRQF_NO_AUTOEN when requesting the irq given that the first thing it does is
> enable it.
I misunderstood the usage of request_irq and enable_irq.
Since there's no need to separate them, I will remove IRQF_NO_AUTOEN and the enable_irq call, and send v5.
Best Regards,
Kazuhiro Abe
>
> Will
next prev parent reply other threads:[~2025-11-06 1:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 7:39 Kazuhiro Abe
2025-10-20 13:23 ` Hanjun Guo
2025-11-04 16:06 ` Will Deacon
2025-11-06 1:19 ` Kazuhiro Abe (Fujitsu) [this message]
2025-11-10 7:38 ` Kazuhiro Abe (Fujitsu)
2025-11-12 4:42 ` Charles Mirabile
2025-11-12 9:18 ` Kazuhiro Abe (Fujitsu)
2025-11-12 9:50 ` Lorenzo Pieralisi
2025-11-14 8:21 ` Kazuhiro Abe (Fujitsu)
2025-11-14 15:20 ` Charles Mirabile
2025-11-14 15:23 ` Will Deacon
2025-11-18 7:29 ` Hanjun Guo
2025-11-18 10:09 ` Kazuhiro Abe (Fujitsu)
2025-11-20 13:27 ` Hanjun Guo
2025-11-21 2:31 ` Kazuhiro Abe (Fujitsu)
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=OSAPR01MB766951191ACB95ABCD7DD319D5C2A@OSAPR01MB7669.jpnprd01.prod.outlook.com \
--to=fj1078ii@fujitsu.com \
--cc=catalin.marinas@arm.com \
--cc=fj2767dz@fujitsu.com \
--cc=guohanjun@huawei.com \
--cc=ilkka@os.amperecomputing.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=will@kernel.org \
/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®