From: nicolas.ferre@atmel•com (Nicolas Ferre)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] iio: at91: document ADC clock properties
Date: Thu, 19 Dec 2013 16:54:17 +0100 [thread overview]
Message-ID: <52B316A9.1060407@atmel.com> (raw)
In-Reply-To: <1387296973-7779-1-git-send-email-b.brezillon@overkiz.com>
On 17/12/2013 17:16, Boris BREZILLON :
> Document the clock properties required by the at91 ADC driver.
>
> Signed-off-by: Boris BREZILLON <b.brezillon@overkiz•com>
Acked-by: Nicolas Ferre <nicolas.ferre@atmel•com>
> ---
> .../devicetree/bindings/arm/atmel-adc.txt | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/atmel-adc.txt b/Documentation/devicetree/bindings/arm/atmel-adc.txt
> index d106146..9a1175b 100644
> --- a/Documentation/devicetree/bindings/arm/atmel-adc.txt
> +++ b/Documentation/devicetree/bindings/arm/atmel-adc.txt
> @@ -5,6 +5,9 @@ Required properties:
> <chip> can be "at91sam9260", "at91sam9g45" or "at91sam9x5"
> - reg: Should contain ADC registers location and length
> - interrupts: Should contain the IRQ line for the ADC
> + - clock-names: tuple listing input clock names.
> + Required elements: "adc_clk", "adc_op_clk".
> + - clocks: phandles to input clocks.
> - atmel,adc-channels-used: Bitmask of the channels muxed and enable for this
> device
> - atmel,adc-startup-time: Startup Time of the ADC in microseconds as
> @@ -44,6 +47,8 @@ adc0: adc at fffb0000 {
> compatible = "atmel,at91sam9260-adc";
> reg = <0xfffb0000 0x100>;
> interrupts = <20 4>;
> + clocks = <&adc_clk>, <&adc_op_clk>;
> + clock-names = "adc_clk", "adc_op_clk";
> atmel,adc-channel-base = <0x30>;
> atmel,adc-channels-used = <0xff>;
> atmel,adc-drdy-mask = <0x10000>;
>
--
Nicolas Ferre
next prev parent reply other threads:[~2013-12-19 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 16:16 [PATCH] iio: at91: document ADC clock properties Boris BREZILLON
2013-12-19 15:54 ` Nicolas Ferre [this message]
2013-12-22 18:05 ` Jonathan Cameron
2014-01-11 16:29 ` Jonathan Cameron
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=52B316A9.1060407@atmel.com \
--to=nicolas.ferre@atmel$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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