From: Marco Giorgi <giorgi.marco.96@disroot.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: netdev@vger.kernel.org, u.kleine-koenig@pengutronix.de,
davem@davemloft.net, michael@walle.cc, kuba@kernel.org
Subject: Re: [PATCH RFC net 2/2] nfc: nxp-nci: Fix i2c read on ThinkPad hardware
Date: Sun, 11 Jun 2023 18:43:42 +0200 [thread overview]
Message-ID: <20230611184342.551cc040@T590-Marco> (raw)
In-Reply-To: <84508d22-2dcd-c49f-2424-37a717a49e1b@linaro.org>
Hi Krzysztof,
On Wed, 7 Jun 2023 19:46:35 +0200
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote:
> On 07/06/2023 19:00, Marco Giorgi wrote:
> > Read IRQ GPIO value and exit from IRQ if the device is not ready.
>
> Why? What problem are you solving?
>
> Why IRQ GPIO - whatever it is - means device is not ready for I2C
> transfer?
It seems that the I2C IRQ gets triggered also when the IRQ GPIO is not
active (low value).
This patch queries the IRQ GPIO before issuing the I2C read.
If the GPIO is low, the IRQ returns with IRQ_HANDLED.
I don't know why the IRQ is triggered even when the GPIO is low, I'm
still looking into it.
I've submitted this patch in the hope to get feedback from other people
to understand what's going on.
>
> >
> > Signed-off-by: Marco Giorgi <giorgi.marco.96@disroot.org>
> > ---
> > drivers/nfc/nxp-nci/i2c.c | 13 +++++++++++++
> > 1 file changed, 13 insertions(+)
>
> Best regards,
> Krzysztof
>
Thanks,
Marco.
prev parent reply other threads:[~2023-06-11 16:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 17:00 [PATCH RFC net 0/2] nfc: nxp-nci: Fix i2c read on ThinkPad hardware Marco Giorgi
2023-06-07 17:00 ` [PATCH RFC net 1/2] " Marco Giorgi
2023-06-07 17:45 ` Krzysztof Kozlowski
2023-06-11 16:25 ` Marco Giorgi
2023-06-12 7:15 ` Krzysztof Kozlowski
2023-06-07 17:00 ` [PATCH RFC net 2/2] " Marco Giorgi
2023-06-07 17:46 ` Krzysztof Kozlowski
2023-06-11 16:43 ` Marco Giorgi [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=20230611184342.551cc040@T590-Marco \
--to=giorgi.marco.96@disroot.org \
--cc=davem@davemloft.net \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=michael@walle.cc \
--cc=netdev@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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).