From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Marco Giorgi <giorgi.marco.96@disroot.org>
Cc: netdev@vger.kernel.org, u.kleine-koenig@pengutronix.de,
davem@davemloft.net, michael@walle.cc, kuba@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC net 1/2] nfc: nxp-nci: Fix i2c read on ThinkPad hardware
Date: Mon, 12 Jun 2023 09:15:45 +0200 [thread overview]
Message-ID: <416a90ee-7501-1014-051d-e6a3eb03a0ff@linaro.org> (raw)
In-Reply-To: <20230611181707.1227de20@T590-Marco>
On 11/06/2023 18:25, Marco Giorgi wrote:
> Hi Krzysztof,
>
> On Wed, 7 Jun 2023 19:45:25 +0200
> Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote:
>
>> On 07/06/2023 19:00, Marco Giorgi wrote:
>>> Add the IRQ GPIO configuration.
>>
>> Why? Please include reasons in commit msg. What you are doing is quite
>> easy to see.
>
> This is my fault, I only put the patch reason in patch [0/2].
>
> Basically, I found out that the mainline driver is not working on my
> machine (Lenovo ThinkPad T590).
>
> I suspect that the I2C read IRQ is somehow misconfigured, and it
> triggers even when the NFC chip is not ready to be read, resulting in
> an error.
Isn't this then a problem of your I2C controller?
>
> In this patch [1/2], I'm adding the "IRQ" GPIO to the driver so its
> value can be directly read from the IRQ thread.
What is IRQ GPIO? If this is interrupt line, you are not handling it
correctly. This is quite surprising code.
>
> In patch [2/2], I'm safely returning from the IRQ thread when the IRQ
> GPIO is not active.
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-06-12 7:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230607170009.9458-1-giorgi.marco.96@disroot.org>
[not found] ` <20230607170009.9458-2-giorgi.marco.96@disroot.org>
2023-06-07 17:45 ` Krzysztof Kozlowski
[not found] ` <20230611181707.1227de20@T590-Marco>
2023-06-12 7:15 ` Krzysztof Kozlowski [this message]
[not found] ` <20230607170009.9458-3-giorgi.marco.96@disroot.org>
2023-06-07 17:46 ` [PATCH RFC net 2/2] " Krzysztof Kozlowski
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=416a90ee-7501-1014-051d-e6a3eb03a0ff@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=davem@davemloft.net \
--cc=giorgi.marco.96@disroot.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®