[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190111161812.26325-2-poeschel@lemonage.de>
Date: Fri, 11 Jan 2019 17:18:05 +0100
From: Lars Poeschel <poeschel@...onage.de>
To: devicetree@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
"GitAuthor: Lars Poeschel" <poeschel@...onage.de>,
linux-kernel@...r.kernel.org (open list)
Cc: Johan Hovold <johan@...nel.org>
Subject: [PATCH v5 2/7] nfc: pn532_uart: Add NXP PN532 to devicetree docs
Add a simple binding doc for the pn532.
Cc: Johan Hovold <johan@...nel.org>
Signed-off-by: Lars Poeschel <poeschel@...onage.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@...42000 {
+ 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
Powered by blists - more mailing lists