From: Lars Poeschel <poeschel@lemonage.de>
To: devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"GitAuthor: Lars Poeschel" <poeschel@lemonage.de>,
linux-kernel@vger.kernel.org (open list)
Cc: Johan Hovold <johan@kernel.org>
Subject: [PATCH v5 2/7] nfc: pn532_uart: Add NXP PN532 to devicetree docs
Date: Fri, 11 Jan 2019 17:18:05 +0100 [thread overview]
Message-ID: <20190111161812.26325-2-poeschel@lemonage.de> (raw)
In-Reply-To: <20190111161812.26325-1-poeschel@lemonage.de>
Add a simple binding doc for the pn532.
Cc: Johan Hovold <johan@kernel.org>
Signed-off-by: Lars Poeschel <poeschel@lemonage.de>
---
Changes in v4:
- Add documentation about reg property in case of i2c
Changes in v3:
- seperate binding doc instead of entry in trivial-devices.txt
.../devicetree/bindings/nfc/pn532.txt | 33 +++++++++++++++++++
1 file changed, 33 insertions(+)
create mode 100644 Documentation/devicetree/bindings/nfc/pn532.txt
diff --git a/Documentation/devicetree/bindings/nfc/pn532.txt b/Documentation/devicetree/bindings/nfc/pn532.txt
new file mode 100644
index 000000000000..d5aaa588073d
--- /dev/null
+++ b/Documentation/devicetree/bindings/nfc/pn532.txt
@@ -0,0 +1,33 @@
+NXP PN532 NFC Chip
+
+Required properties:
+- compatible: Should be
+ - "nxp,pn532" Place a node with this inside the devicetree node of the bus
+ where the NFC chip is connected to.
+ Currently the kernel has phy bindings for uart and i2c.
+ - "nxp,pn532-i2c" (DEPRECATED) only works for the i2c binding.
+ - "nxp,pn533-i2c" (DEPRECATED) only works for the i2c binding.
+
+Required properties if connected on i2c:
+- reg: for the i2c bus address. This is fixed at 0x48 for the PN532.
+
+Example uart:
+
+uart4: serial@49042000 {
+ compatible = "ti,omap3-uart";
+
+ pn532: nfc {
+ compatible = "nxp,pn532";
+ };
+};
+
+Example i2c:
+
+i2c1: i2c@0 {
+ compatible = "ti,omap3-i2c";
+
+ pn532: nfc {
+ compatible = "nxp,pn532";
+ reg = <0x48>;
+ };
+};
--
2.20.1
next prev parent reply other threads:[~2019-01-11 15:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 16:18 [PATCH v5 1/7] nfc: pn533: i2c: "pn532" as dt compatible string Lars Poeschel
2019-01-11 16:18 ` Lars Poeschel [this message]
2019-01-15 19:59 ` [PATCH v5 2/7] nfc: pn532_uart: Add NXP PN532 to devicetree docs Rob Herring
2019-01-24 10:02 ` Lars Poeschel
2019-01-11 16:18 ` [PATCH v5 3/7] nfc: pn533: Add dev_up/dev_down hooks to phy_ops Lars Poeschel
2019-01-11 16:18 ` [PATCH v5 4/7] nfc: pn533: Split pn533 init & nfc_register Lars Poeschel
2019-01-11 16:18 ` [PATCH v5 5/7] nfc: pn533: add UART phy driver Lars Poeschel
2019-01-11 16:18 ` [PATCH v5 6/7] nfc: pn533: Add autopoll capability Lars Poeschel
2019-01-11 16:18 ` [PATCH v5 7/7] nfc: pn532_uart: Make use of pn532 autopoll Lars Poeschel
2019-02-28 10:48 ` [PING] [PATCH v5 1/7] nfc: pn533: i2c: "pn532" as dt compatible string Lars Poeschel
2019-04-03 9:47 ` [PING 2] " Lars Poeschel
2019-08-05 12:42 ` Johan Hovold
2019-08-12 7:40 ` Lars Poeschel
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=20190111161812.26325-2-poeschel@lemonage.de \
--to=poeschel@lemonage.de \
--cc=devicetree@vger.kernel.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
/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).