From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Ludovic Desroches <ludovic.desroches@microchip.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: alexandre.belloni@free-electrons.com,
Eugen.Hristev@microchip.com, "# 3 . 16+" <stable@vger.kernel.org>
Subject: Re: [PATCH 1/2] ARM: dts: at91: sama5d3_xplained: fix ADC vref
Date: Mon, 10 Apr 2017 11:04:44 +0200 [thread overview]
Message-ID: <0c78ac8e-1e1f-14c3-e510-1caf857d4ef5@microchip.com> (raw)
In-Reply-To: <20170410082517.19628-1-ludovic.desroches@microchip.com>
Le 10/04/2017 à 10:25, Ludovic Desroches a écrit :
> The voltage reference for the ADC is not 3V but 3.3V since it is connected to
> VDDANA.
>
> Signed-off-by: Ludovic Desroches <ludovic.desroches@microchip.com>
> Cc: <stable@vger.kernel.org> # 3.16+
Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
> ---
> arch/arm/boot/dts/at91-sama5d3_xplained.dts | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/boot/dts/at91-sama5d3_xplained.dts b/arch/arm/boot/dts/at91-sama5d3_xplained.dts
> index c51fc65..7a0fa1a 100644
> --- a/arch/arm/boot/dts/at91-sama5d3_xplained.dts
> +++ b/arch/arm/boot/dts/at91-sama5d3_xplained.dts
> @@ -162,6 +162,7 @@
> };
>
> adc0: adc@f8018000 {
> + atmel,adc-vref = <3300>;
> pinctrl-0 = <
> &pinctrl_adc0_adtrg
> &pinctrl_adc0_ad0
>
--
Nicolas Ferre
next prev parent reply other threads:[~2017-04-10 9:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 8:25 [PATCH 1/2] ARM: dts: at91: sama5d3_xplained: fix ADC vref Ludovic Desroches
2017-04-10 8:25 ` [PATCH 2/2] ARM: dts: at91: sama5d3_xplained: not all ADC channels are available Ludovic Desroches
[not found] ` <20170410082517.19628-2-ludovic.desroches-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org>
2017-04-10 9:04 ` Nicolas Ferre
2017-04-10 10:28 ` Alexandre Belloni
2017-04-10 9:04 ` Nicolas Ferre [this message]
2017-04-10 10:28 ` [PATCH 1/2] ARM: dts: at91: sama5d3_xplained: fix ADC vref Alexandre Belloni
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=0c78ac8e-1e1f-14c3-e510-1caf857d4ef5@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=Eugen.Hristev@microchip.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=stable@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).