From: Dmitry Osipenko <digetx@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: sameo@linux.intel.com, david@ixit.cz, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] nfc: pn544: Fix occasional HW initialization failure
Date: Thu, 20 Feb 2020 00:41:56 +0300 [thread overview]
Message-ID: <7723e3ad-e004-a691-6605-50ce05132162@gmail.com> (raw)
In-Reply-To: <20200219.111130.5189327548859835.davem@davemloft.net>
19.02.2020 22:11, David Miller пишет:
> From: Dmitry Osipenko <digetx@gmail.com>
> Date: Wed, 19 Feb 2020 18:01:22 +0300
>
>> The PN544 driver checks the "enable" polarity during of driver's probe and
>> it's doing that by turning ON and OFF NFC with different polarities until
>> enabling succeeds. It takes some time for the hardware to power-down, and
>> thus, to deassert the IRQ that is raised by turning ON the hardware.
>> Since the delay after last power-down of the polarity-checking process is
>> missed in the code, the interrupt may trigger immediately after installing
>> the IRQ handler (right after the checking is done), which results in IRQ
>> handler trying to touch the disabled HW and ends with marking NFC as
>> 'DEAD' during of the driver's probe:
>>
>> pn544_hci_i2c 1-002a: NFC: nfc_en polarity : active high
>> pn544_hci_i2c 1-002a: NFC: invalid len byte
>> shdlc: llc_shdlc_recv_frame: NULL Frame -> link is dead
>>
>> This patch fixes the occasional NFC initialization failure on Nexus 7
>> device.
>>
>> Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
>
> Applied and queued up for -stable, thanks.
>
Awesome, thanks!
prev parent reply other threads:[~2020-02-19 21:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 15:01 Dmitry Osipenko
2020-02-19 19:11 ` David Miller
2020-02-19 21:41 ` Dmitry Osipenko [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=7723e3ad-e004-a691-6605-50ce05132162@gmail.com \
--to=digetx@gmail.com \
--cc=davem@davemloft.net \
--cc=david@ixit.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sameo@linux.intel.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
all inboxes | Powered by JetHome®