linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Zhao Qiang <qiang.zhao@nxp.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org, Priyanka.Jain@freescale.com,
	oss@buserror.net
Subject: Re: [PATCH 3/6] QE: Add uqe_serial document to bindings
Date: Fri, 8 Jan 2016 14:12:25 -0600	[thread overview]
Message-ID: <20160108201225.GA9813@rob-hp-laptop> (raw)
In-Reply-To: <1452219494-31947-3-git-send-email-qiang.zhao@nxp.com>

On Fri, Jan 08, 2016 at 10:18:11AM +0800, Zhao Qiang wrote:
> Add uqe_serial document to
> Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/uqe_serial.txt
> 
> Signed-off-by: Zhao Qiang <qiang.zhao@nxp.com>
> ---
>  .../bindings/powerpc/fsl/cpm_qe/uqe_serial.txt       | 20 ++++++++++++++++++++
>  1 file changed, 20 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/uqe_serial.txt
> 
> diff --git a/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/uqe_serial.txt b/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/uqe_serial.txt
> new file mode 100644
> index 0000000..e677599
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/uqe_serial.txt
> @@ -0,0 +1,20 @@
> +* Serial
> +
> +Currently defined compatibles:
> +- ucc_uart
> +
> +Properties for ucc_uart:
> +device_type : which type the device is

Drop this please.

> +port-number : port number of UCC-UART

Use aliases instead.

> +rx-clock-name : which clock QE use for RX
> +tx-clock-name : which clock QE use for TX

These should use the clock binding.

> +
> +Example:
> +
> +	serial: ucc@2200 {
> +		device_type = "serial";
> +		compatible = "ucc_uart";
> +		port-number = <1>;
> +		rx-clock-name = "brg2";
> +		tx-clock-name = "brg2";
> +	};
> -- 
> 2.1.0.27.g96db324
> 
> --
> 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:[~2016-01-08 20:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-08  2:18 [PATCH 1/6] QE: Add IC, SI and SIRAM document to device tree bindings Zhao Qiang
2016-01-08  2:18 ` [PATCH 2/6] QE: Add ucc hdlc document to bindings Zhao Qiang
2016-01-08 20:10   ` Rob Herring
2016-01-08  2:18 ` [PATCH 3/6] QE: Add uqe_serial " Zhao Qiang
2016-01-08 20:12   ` Rob Herring [this message]
2016-01-11  8:19     ` Qiang Zhao
2016-01-18  3:28     ` Qiang Zhao
2016-01-18  9:10   ` Li Yang
2016-01-18  9:24     ` Qiang Zhao
2016-01-18 23:07       ` Scott Wood
2016-01-19  1:22         ` Qiang Zhao
2016-01-08  2:18 ` [PATCH 4/6] T104xD4RDB: Add qe node to t104xd4rdb Zhao Qiang
2016-01-08  2:18 ` [PATCH 5/6] T104xRDB: Add qe node to t104xrdb Zhao Qiang
2016-01-08  2:18 ` [PATCH 6/6] T104xQDS: Add qe node to t104xqds Zhao Qiang
2016-01-08 21:02 ` [PATCH 1/6] QE: Add IC, SI and SIRAM document to device tree bindings Rob Herring

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=20160108201225.GA9813@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=Priyanka.Jain@freescale.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=oss@buserror.net \
    --cc=qiang.zhao@nxp.com \
    /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).