public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Carl Lee <qq1145099@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: linux-kernel@vger.kernel.org, krzk@kernel.org,
	netdev@vger.kernel.org, carl.lee@amd.com, peter.shen@amd.com,
	colin.huang2@amd.com
Subject: Re: [PATCH v2] nfc: nxp-nci: i2c: restore IRQ trigger fallback
Date: Mon, 30 Mar 2026 18:04:24 +0800	[thread overview]
Message-ID: <acpKqD76FUWSH1UE@carl-amd> (raw)
In-Reply-To: <20260316192609.3e001253@kernel.org>

On Mon, Mar 16, 2026 at 07:26:09PM -0700, Jakub Kicinski wrote:
> On Thu, 12 Mar 2026 10:51:35 +0800 Carl Lee via B4 Relay wrote:
> > From: Carl Lee <carl.lee@amd.com>
> > 
> > The driver previously relied on IRQF_TRIGGER_RISING when requesting
> > the interrupt. This was removed to rely on the trigger type provided
> > by firmware.
> > 
> > However, some platforms do not propagate the interrupt trigger type
> > to the IRQ descriptor, resulting in interrupts not being triggered.
> > 
> > Use the trigger type provided by firmware when available and fall
> > back to the historically used rising-edge trigger otherwise.
> 
> Sounds like a regression, if you can please mention which platform you
> hit the issue on, and please repost with a Fixes tag, presumably:
> 
> Fixes: 57be33f85e36 ("nfc: nxp-nci: remove interrupt trigger type")
> 
> 
> > diff --git a/drivers/nfc/nxp-nci/i2c.c b/drivers/nfc/nxp-nci/i2c.c
> > index 6a5ce8ff91f0..7aaab92c616c 100644
> > --- a/drivers/nfc/nxp-nci/i2c.c
> > +++ b/drivers/nfc/nxp-nci/i2c.c
> > @@ -16,6 +16,7 @@
> >  #include <linux/delay.h>
> >  #include <linux/i2c.h>
> >  #include <linux/interrupt.h>
> > +#include <linux/irq.h>
> >  #include <linux/module.h>
> >  #include <linux/nfc.h>
> >  #include <linux/gpio/consumer.h>
> > @@ -268,6 +269,7 @@ static int nxp_nci_i2c_probe(struct i2c_client *client)
> >  	struct device *dev = &client->dev;
> >  	struct nxp_nci_i2c_phy *phy;
> >  	int r;
> > +	unsigned long irqflags;
> 
> nit: when you repost please order the variable lines longest to shortest
> 
>  	struct device *dev = &client->dev;
>  	struct nxp_nci_i2c_phy *phy;
> +	unsigned long irqflags;
>  	int r;
> -- 
> pw-bot: cr
> 

Hi Jakub,

Thanks for the feedback and for the detailed investigation.

After further analysis, this issue is not related to the proposed change and does not appear to be reproducible on our side.

I will drop this patch for now.

Thanks!

      reply	other threads:[~2026-03-30 10:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-12  2:51 [PATCH v2] nfc: nxp-nci: i2c: restore IRQ trigger fallback Carl Lee via B4 Relay
2026-03-17  2:26 ` Jakub Kicinski
2026-03-30 10:04   ` Carl Lee [this message]

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=acpKqD76FUWSH1UE@carl-amd \
    --to=qq1145099@gmail.com \
    --cc=carl.lee@amd.com \
    --cc=colin.huang2@amd.com \
    --cc=krzk@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=peter.shen@amd.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