devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: "jon@ringle.org" <jon@ringle.org>
Cc: "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Jon Ringle <jringle@gridpoint.com>
Subject: Re: [PATCH v2 2/2] serial: sc16is7xx: Add bindings documentation for the SC16IS7XX UARTs
Date: Wed, 26 Mar 2014 09:08:56 +0000	[thread overview]
Message-ID: <20140326090855.GP10341@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <1395771564-30534-2-git-send-email-jon@ringle.org>

On Tue, Mar 25, 2014 at 06:19:24PM +0000, jon@ringle.org wrote:
> From: Jon Ringle <jringle@gridpoint.com>
> 
> This patch adds the devicetree documentation for the NXP SC16IS7XX UARTs.
> 
> Signed-off-by: Jon Ringle <jringle@gridpoint.com>
> ---
>  .../devicetree/bindings/serial/nxp,sc16is7xx.txt   | 35 ++++++++++++++++++++++
>  1 file changed, 35 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/serial/nxp,sc16is7xx.txt
> 
> diff --git a/Documentation/devicetree/bindings/serial/nxp,sc16is7xx.txt b/Documentation/devicetree/bindings/serial/nxp,sc16is7xx.txt
> new file mode 100644
> index 0000000..cd9ae33
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/serial/nxp,sc16is7xx.txt
> @@ -0,0 +1,35 @@
> +* NXP SC16IS7xx advanced Universal Asynchronous Receiver-Transmitter (UART)
> +
> +Required properties:
> +- compatible: Should be one of the following:
> +  - "nxp,sc16is740" for NXP SC16IS740,
> +  - "nxp,sc16is741" for NXP SC16IS741,
> +  - "nxp,sc16is750" for NXP SC16IS750,
> +  - "nxp,sc16is752" for NXP SC16IS752,
> +  - "nxp,sc16is760" for NXP SC16IS760,
> +  - "nxp,sc16is762" for NXP SC16IS762.

These all look fine.

> +- reg: I2C address of the SC16IS7xx device.
> +- interrupt-parent: The phandle for the interrupt controller that
> +  services interrupts for this IC.
> +- interrupts: Specifies the interrupt source of the parent interrupt
> +  controller. The format of the interrupt specifier depends on the
> +  parent interrupt controller.

Just describe what the device-specific interrupt logically is, not what
the interrupts property means in general.

> +- clocks: phandle to the IC source clock.

Nit: clocks aren't just referred to with phandles; there's a clock
specifier too.

Either correct the type here or don't mention the type at all, given
this is a common property.

> +
> +Optional properties:
> +- gpio-controller: Marks the device node as a GPIO controller.
> +- #gpio-cells: Should be two. The first cell is the GPIO number and
> +  the second cell is used to specify the GPIO polarity:
> +    0 = active high,
> +    1 = active low.
> +
> +Example:
> +        sc16is750: sc16is750@51 {
> +                compatible = "nxp,sc16is750";
> +                reg = <0x51>;
> +                clocks = <&clk20m>;
> +                interrupt-parent = <&gpio3>;
> +                interrupts = <7 IRQ_TYPE_EDGE_FALLING>;
> +                gpio-controller;
> +                #gpio-cells = <2>;
> +        };
> -- 
> 1.8.5.4
> 
> --
> To unsubscribe from this list: send the line "unsubscribe devicetree" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

  reply	other threads:[~2014-03-26  9:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-25 18:19 [PATCH v2 1/2] serial: sc16is7xx jon
2014-03-25 18:19 ` [PATCH v2 2/2] serial: sc16is7xx: Add bindings documentation for the SC16IS7XX UARTs jon
2014-03-26  9:08   ` Mark Rutland [this message]
2014-03-26 12:49     ` Jon Ringle
2014-03-26 13:35       ` 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=20140326090855.GP10341@e106331-lin.cambridge.arm.com \
    --to=mark.rutland@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jon@ringle.org \
    --cc=jringle@gridpoint.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.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).