devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
To: Clement Perrochaud <clement.perrochaud-3arQi8VN3Tc@public.gmane.org>
Cc: "linux-nfc-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org"
	<linux-nfc-y27Ovi1pjclAfugRpC6u6w@public.gmane.org>,
	"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v3 2/2] NFC: pn544_i2c: Add DTS Documentation
Date: Mon, 31 Mar 2014 16:25:50 +0100	[thread overview]
Message-ID: <20140331152550.GA15064@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <6ec915ed416745248c5ed4aa22dfe0e6-fjMGVQzTDdguRZvghep3ngfhPeD8jYilXA4E9RH9d+qIuWR1G4zioA@public.gmane.org>

On Mon, Mar 31, 2014 at 01:22:24PM +0100, Clement Perrochaud wrote:
> Describe the properties used by the PN544 NFC controller driver.
> 
> Signed-off-by: Clément Perrochaud <clement.perrochaud-3arQi8VN3Tc@public.gmane.org>
> ---
>  .../devicetree/bindings/net/nfc/pn544.txt          | 32 ++++++++++++++++++++++
>  1 file changed, 32 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/net/nfc/pn544.txt
> 
> diff --git a/Documentation/devicetree/bindings/net/nfc/pn544.txt b/Documentation/devicetree/bindings/net/nfc/pn544.txt
> new file mode 100644
> index 0000000..2017ad5
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/nfc/pn544.txt
> @@ -0,0 +1,32 @@
> +* NXP Semiconductors PN544 NFC Controller
> +
> +Required properties:
> +- compatible: Should be "nxp,pn544_i2c".

s/_/-/ in compatible strings and property names, please.

> +- clock-frequency: I²C work frequency.
> +- reg: address on the bus
> +- irq: Input GPIO pin used for interrupt requests from the controller

As this is an interrupt from the point of view of the device, I would
prefer this described as an interrupt (using the standard interrupts
property), with the GPIO controller described as an interrupt
controller.

> +- en: Output GPIO pin used for enabling/disabling the PN544

enable-gpios?

> +- fw:Output GPIO pin used to enter firmware download mode

firmware-gpios?

Cheers,
Mark.

> +
> +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 PN544 on I2C2):
> +
> +&i2c2 {
> +
> +	status = "okay";
> +
> +    pn544: pn544@28 {
> +
> +        compatible = "nxp,pn544_i2c";
> +
> +        reg = <0x28>;
> +        clock-frequency = <400000>;
> +
> +        irq  = <&gpio1 17 GPIO_ACTIVE_HIGH>;
> +        en = <&gpio3 21 GPIO_ACTIVE_HIGH>;
> +        fw = <&gpio3 19 GPIO_ACTIVE_HIGH>;
> +    };
> +};
> -- 
> 1.9.0
> 
> --
> To unsubscribe from this list: send the line "unsubscribe devicetree" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2014-03-31 15:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-31 12:22 [PATCH v3 2/2] NFC: pn544_i2c: Add DTS Documentation Clement Perrochaud
     [not found] ` <6ec915ed416745248c5ed4aa22dfe0e6-fjMGVQzTDdguRZvghep3ngfhPeD8jYilXA4E9RH9d+qIuWR1G4zioA@public.gmane.org>
2014-03-31 15:25   ` Mark Rutland [this message]
     [not found]     ` <20140331152550.GA15064-NuALmloUBlrZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2014-04-01 13:45       ` Clement Perrochaud
     [not found]         ` <ab2e5666063c4ea1937636a911dfca02-fjMGVQzTDdguRZvghep3ngfhPeD8jYilXA4E9RH9d+qIuWR1G4zioA@public.gmane.org>
2014-04-01 16:05           ` Mark Rutland

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=20140331152550.GA15064@e106331-lin.cambridge.arm.com \
    --to=mark.rutland-5wv7dgnigg8@public.gmane.org \
    --cc=clement.perrochaud-3arQi8VN3Tc@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-nfc-y27Ovi1pjclAfugRpC6u6w@public.gmane.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).