From: Rob Herring <robh@kernel.org>
To: Lars Poeschel <poeschel@lemonage.de>
Cc: "David S. Miller" <davem@davemloft.net>,
Mark Rutland <mark.rutland@arm.com>,
"open list:NFC SUBSYSTEM" <netdev@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Johan Hovold <johan@kernel.org>,
Simon Horman <horms@verge.net.au>
Subject: Re: [PATCH v8 2/7] nfc: pn532: Add uart phy docs and rename it
Date: Fri, 27 Sep 2019 10:52:09 -0500 [thread overview]
Message-ID: <20190927155209.GA6261@bogus> (raw)
In-Reply-To: <20190919091645.16439-2-poeschel@lemonage.de>
On Thu, Sep 19, 2019 at 11:16:39AM +0200, Lars Poeschel wrote:
> This adds documentation about the uart phy to the pn532 binding doc. As
> the filename "pn533-i2c.txt" is not appropriate any more, rename it to
> the more general "pn532.txt".
> This also documents the deprecation of the compatible strings ending
> with "...-i2c".
>
> Cc: Johan Hovold <johan@kernel.org>
> Cc: Simon Horman <horms@verge.net.au>
> Signed-off-by: Lars Poeschel <poeschel@lemonage.de>
> ---
> Changes in v8:
> - Update existing binding doc instead of adding a new one:
> - Add uart phy example
> - Add general "pn532" compatible string
> - Deprecate "...-i2c" compatible strings
> - Rename file to a more general filename
> - Intentionally drop Rob's Reviewed-By as I guess this rather big change
> requires a new review
>
> Changes in v7:
> - Accidentally lost Rob's Reviewed-By
>
> Changes in v6:
> - Rebased the patch series on v5.3-rc5
> - Picked up Rob's Reviewed-By
>
> 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/net/nfc/pn532.txt | 46 +++++++++++++++++++
> .../devicetree/bindings/net/nfc/pn533-i2c.txt | 29 ------------
> 2 files changed, 46 insertions(+), 29 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/net/nfc/pn532.txt
> delete mode 100644 Documentation/devicetree/bindings/net/nfc/pn533-i2c.txt
In the future, use '-M' option (I recommend making this the default).
>
> diff --git a/Documentation/devicetree/bindings/net/nfc/pn532.txt b/Documentation/devicetree/bindings/net/nfc/pn532.txt
> new file mode 100644
> index 000000000000..f0591f160bee
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/nfc/pn532.txt
> @@ -0,0 +1,46 @@
> +* NXP Semiconductors PN532 NFC Controller
> +
> +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.
No more pm533 support?
> +
> +Required properties if connected on i2c:
> +- clock-frequency: I²C work frequency.
> +- reg: for the I²C bus address. This is fixed at 0x24 for the PN532.
> +- interrupts: GPIO interrupt to which the chip is connected
UART attached case has no irq? I guess it could just start sending
data...
> +
> +Optional SoC Specific Properties:
> +- pinctrl-names: Contains only one value - "default".
> +- pintctrl-0: Specifies the pin control groups used for this controller.
> +
> +Example (for ARM-based BeagleBone with PN532 on I2C2):
> +
> +&i2c2 {
> +
> +
> + pn532: pn532@24 {
nfc@24
> +
> + compatible = "nxp,pn532";
> +
> + reg = <0x24>;
> + clock-frequency = <400000>;
> +
> + interrupt-parent = <&gpio1>;
> + interrupts = <17 IRQ_TYPE_EDGE_FALLING>;
> +
> + };
> +};
> +
> +Example (for PN532 connected via uart):
> +
> +uart4: serial@49042000 {
> + compatible = "ti,omap3-uart";
> +
> + pn532: nfc {
> + compatible = "nxp,pn532";
> + };
> +};
next prev parent reply other threads:[~2019-09-27 15:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 9:16 [PATCH v8 1/7] nfc: pn533: i2c: "pn532" as dt compatible string Lars Poeschel
2019-09-19 9:16 ` [PATCH v8 2/7] nfc: pn532: Add uart phy docs and rename it Lars Poeschel
2019-09-19 9:16 ` Lars Poeschel
2019-09-27 15:52 ` Rob Herring [this message]
2019-09-30 7:47 ` Lars Poeschel
2019-09-19 9:16 ` [PATCH v8 3/7] nfc: pn533: Add dev_up/dev_down hooks to phy_ops Lars Poeschel
2019-09-19 9:16 ` [PATCH v8 4/7] nfc: pn533: Split pn533 init & nfc_register Lars Poeschel
2019-09-19 9:16 ` [PATCH v8 5/7] nfc: pn533: add UART phy driver Lars Poeschel
2019-09-19 9:16 ` [PATCH v8 6/7] nfc: pn533: Add autopoll capability Lars Poeschel
2019-09-19 9:16 ` [PATCH v8 7/7] nfc: pn532_uart: Make use of pn532 autopoll Lars Poeschel
2019-09-19 11:32 ` [PATCH v8 1/7] nfc: pn533: i2c: "pn532" as dt compatible string David Miller
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=20190927155209.GA6261@bogus \
--to=robh@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=horms@verge.net.au \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=poeschel@lemonage.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.