From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Boris BREZILLON <b.brezillon@overkiz.com>,
Rob Landley <rob@landley.net>, Mark Brown <broonie@linaro.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<devicetree@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] drivers/misc: atmel-ssc: document clock properties
Date: Thu, 19 Dec 2013 16:53:47 +0100 [thread overview]
Message-ID: <52B3168B.10004@atmel.com> (raw)
In-Reply-To: <1387292507-6606-1-git-send-email-b.brezillon@overkiz.com>
On 17/12/2013 16:01, Boris BREZILLON :
> Document the clock properties required by the atmel-ssc driver.
>
> Signed-off-by: Boris BREZILLON <b.brezillon@overkiz.com>
Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
> ---
> .../devicetree/bindings/misc/atmel-ssc.txt | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/misc/atmel-ssc.txt b/Documentation/devicetree/bindings/misc/atmel-ssc.txt
> index a45ae08..60960b2 100644
> --- a/Documentation/devicetree/bindings/misc/atmel-ssc.txt
> +++ b/Documentation/devicetree/bindings/misc/atmel-ssc.txt
> @@ -6,6 +6,9 @@ Required properties:
> - atmel,at91sam9g45-ssc: support dma transfer
> - reg: Should contain SSC registers location and length
> - interrupts: Should contain SSC interrupt
> +- clock-names: tuple listing input clock names.
> + Required elements: "pclk"
> +- clocks: phandles to input clocks.
>
>
> Required properties for devices compatible with "atmel,at91sam9g45-ssc":
> @@ -20,6 +23,8 @@ ssc0: ssc@fffbc000 {
> compatible = "atmel,at91rm9200-ssc";
> reg = <0xfffbc000 0x4000>;
> interrupts = <14 4 5>;
> + clocks = <&ssc0_clk>;
> + clock-names = "pclk";
> };
>
> - DMA transfer:
>
--
Nicolas Ferre
prev parent reply other threads:[~2013-12-19 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 15:01 [PATCH] drivers/misc: atmel-ssc: document clock properties Boris BREZILLON
2013-12-19 15:53 ` Nicolas Ferre [this message]
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=52B3168B.10004@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=arnd@arndb.de \
--cc=b.brezillon@overkiz.com \
--cc=broonie@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
/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