From: Lars Poeschel <poeschel@lemonage.de>
To: devicetree@vger.kernel.org, Samuel Ortiz <sameo@linux.intel.com>,
"GitAuthor: Lars Poeschel" <poeschel@lemonage.de>,
linux-wireless@vger.kernel.org (open list:NFC SUBSYSTEM),
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH v3 5/5] nfc: pn532_uart: Make use of pn532 autopoll
Date: Thu, 25 Oct 2018 15:29:36 +0200 [thread overview]
Message-ID: <20181025132937.24405-5-poeschel@lemonage.de> (raw)
In-Reply-To: <20181025132937.24405-1-poeschel@lemonage.de>
This switches the pn532 UART phy driver from manually polling to the new
autopoll mechanism.
Signed-off-by: Lars Poeschel <poeschel@lemonage.de>
---
drivers/nfc/pn533/uart.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/nfc/pn533/uart.c b/drivers/nfc/pn533/uart.c
index 8fd71c8953ca..a95ca01745ca 100644
--- a/drivers/nfc/pn533/uart.c
+++ b/drivers/nfc/pn533/uart.c
@@ -207,7 +207,7 @@ static int pn532_uart_probe(struct serdev_device *serdev)
goto err_free;
pn532->serdev = serdev;
- priv = pn533_register_device(PN533_DEVICE_PN532,
+ priv = pn533_register_device(PN533_DEVICE_PN532_AUTOPOLL,
PN533_NO_TYPE_B_PROTOCOLS,
PN533_PROTO_REQ_ACK_RESP,
pn532, &uart_phy_ops, NULL,
--
2.19.1
prev parent reply other threads:[~2018-10-25 13:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-25 13:29 [PATCH v3 1/5] nfc: pn533: i2c: "pn532" as dt compatible string Lars Poeschel
2018-10-25 13:29 ` [PATCH v3 2/5] nfc: pn532_uart: Add NXP PN532 to devicetree docs Lars Poeschel
2018-10-25 21:54 ` Rob Herring
2018-10-26 7:59 ` Lars Poeschel
2018-10-25 13:29 ` [PATCH v3 3/5] nfc: pn533: add UART phy driver Lars Poeschel
2018-10-28 10:27 ` Johan Hovold
2018-10-28 13:46 ` Marcel Holtmann
2018-10-28 14:35 ` Johan Hovold
2018-10-29 10:02 ` Lars Poeschel
2018-10-29 11:07 ` Johan Hovold
2018-10-29 15:51 ` Lars Poeschel
2018-10-29 16:13 ` Johan Hovold
2018-10-25 13:29 ` [PATCH v3 4/5] nfc: pn533: Add autopoll capability Lars Poeschel
2018-10-25 13:29 ` Lars Poeschel [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=20181025132937.24405-5-poeschel@lemonage.de \
--to=poeschel@lemonage.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).