From: jic23@kernel.org (Jonathan Cameron)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: at91: dts: add adc resolution stuff
Date: Fri, 29 Mar 2013 09:47:38 +0000 [thread overview]
Message-ID: <5155633A.3060701@kernel.org> (raw)
In-Reply-To: <1364548399-15827-1-git-send-email-ludovic.desroches@atmel.com>
On 03/29/2013 09:13 AM, ludovic.desroches at atmel.com wrote:
> From: Ludovic Desroches <ludovic.desroches@atmel.com>
>
> Add the ADC low and high resolution configuration and which one to use.
>
> Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
> ---
>
> Hi,
>
> This patch is a split from this set of patches:
> http://thread.gmane.org/gmane.linux.ports.arm.kernel/206130/focus=6321
>
> Then device tree changes can go through ARM-SOC and driver changes through the
> iio subsystem.
I am guessing the IIO side is to follow. Even when posting series where it different
bits are to go through different trees, it is useful to have them in one series so that
people can see the whole result.
>
> Regards
>
> Ludovic
>
> arch/arm/boot/dts/at91sam9260.dtsi | 3 +++
> arch/arm/boot/dts/at91sam9g45.dtsi | 3 +++
> arch/arm/boot/dts/at91sam9x5.dtsi | 3 +++
> 3 files changed, 9 insertions(+)
>
> diff --git a/arch/arm/boot/dts/at91sam9260.dtsi b/arch/arm/boot/dts/at91sam9260.dtsi
> index cb7bcc5..367a604 100644
> --- a/arch/arm/boot/dts/at91sam9260.dtsi
> +++ b/arch/arm/boot/dts/at91sam9260.dtsi
> @@ -484,6 +484,9 @@
> atmel,adc-drdy-mask = <0x10000>;
> atmel,adc-status-register = <0x1c>;
> atmel,adc-trigger-register = <0x04>;
> + atmel,adc-res = <8 10>;
> + atmel,adc-res-names = "lowres", "highres";
> + atmel,adc-use-res = "highres";
>
> trigger at 0 {
> trigger-name = "timer-counter-0";
> diff --git a/arch/arm/boot/dts/at91sam9g45.dtsi b/arch/arm/boot/dts/at91sam9g45.dtsi
> index 6b1d4ca..0fa28af 100644
> --- a/arch/arm/boot/dts/at91sam9g45.dtsi
> +++ b/arch/arm/boot/dts/at91sam9g45.dtsi
> @@ -484,6 +484,9 @@
> atmel,adc-drdy-mask = <0x10000>;
> atmel,adc-status-register = <0x1c>;
> atmel,adc-trigger-register = <0x08>;
> + atmel,adc-res = <8 10>;
> + atmel,adc-res-names = "lowres", "highres";
> + atmel,adc-use-res = "highres";
>
> trigger at 0 {
> trigger-name = "external-rising";
> diff --git a/arch/arm/boot/dts/at91sam9x5.dtsi b/arch/arm/boot/dts/at91sam9x5.dtsi
> index a98c0d5..08bcdd7 100644
> --- a/arch/arm/boot/dts/at91sam9x5.dtsi
> +++ b/arch/arm/boot/dts/at91sam9x5.dtsi
> @@ -505,6 +505,9 @@
> atmel,adc-drdy-mask = <0x1000000>;
> atmel,adc-status-register = <0x30>;
> atmel,adc-trigger-register = <0xc0>;
> + atmel,adc-res = <8 10>;
> + atmel,adc-res-names = "lowres", "highres";
> + atmel,adc-use-res = "highres";
>
> trigger at 0 {
> trigger-name = "external-rising";
>
next prev parent reply other threads:[~2013-03-29 9:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 9:13 [PATCH] ARM: at91: dts: add adc resolution stuff ludovic.desroches at atmel.com
2013-03-29 9:47 ` Jonathan Cameron [this message]
2013-03-29 14:37 ` Nicolas Ferre
2013-04-02 18:13 ` Jonathan Cameron
2013-03-29 16:28 ` Jean-Christophe PLAGNIOL-VILLARD
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=5155633A.3060701@kernel.org \
--to=jic23@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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).