From: Jonathan Cameron <jic23@kernel.org>
To: Fabrice Gasnier <fabrice.gasnier@st.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
lars@metafoo.de, alexandre.torgue@st.com,
linux-iio@vger.kernel.org, pmeerw@pmeerw.net,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
mcoquelin.stm32@gmail.com, knaack.h@gmx.de,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/5] dt-bindings: iio: adc: stm32: add missing vdda supply
Date: Sat, 22 Jun 2019 10:36:36 +0100 [thread overview]
Message-ID: <20190622103636.63148958@archlinux> (raw)
In-Reply-To: <1560947398-11592-2-git-send-email-fabrice.gasnier@st.com>
On Wed, 19 Jun 2019 14:29:54 +0200
Fabrice Gasnier <fabrice.gasnier@st.com> wrote:
> Add missing vdda-supply, analog power supply, to STM32 ADC. It's required
> to properly supply the ADC.
>
> Fixes: 841fcea454fe ("Documentation: dt-bindings: Document STM32 ADC DT
> bindings")
>
> Signed-off-by: Fabrice Gasnier <fabrice.gasnier@st.com>
Applied to the togreg branch of iio.git and pushed out as testing for
the autobuilders to ignore completely.
thanks,
Jonathan
> ---
> Documentation/devicetree/bindings/iio/adc/st,stm32-adc.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/iio/adc/st,stm32-adc.txt b/Documentation/devicetree/bindings/iio/adc/st,stm32-adc.txt
> index 8346bcb..93a0bd2 100644
> --- a/Documentation/devicetree/bindings/iio/adc/st,stm32-adc.txt
> +++ b/Documentation/devicetree/bindings/iio/adc/st,stm32-adc.txt
> @@ -38,6 +38,7 @@ Required properties:
> It's required on stm32h7.
> - clock-names: Must be "adc" and/or "bus" depending on part used.
> - interrupt-controller: Identifies the controller node as interrupt-parent
> +- vdda-supply: Phandle to the vdda input analog voltage.
> - vref-supply: Phandle to the vref input analog reference voltage.
> - #interrupt-cells = <1>;
> - #address-cells = <1>;
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-22 9:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 12:29 [PATCH 0/5] Add missing vdda-supply to STM32 ADC Fabrice Gasnier
2019-06-19 12:29 ` [PATCH 1/5] dt-bindings: iio: adc: stm32: add missing vdda supply Fabrice Gasnier
2019-06-22 9:36 ` Jonathan Cameron [this message]
2019-06-19 12:29 ` [PATCH 2/5] iio: adc: stm32-adc: add missing vdda-supply Fabrice Gasnier
2019-06-22 9:39 ` Jonathan Cameron
2019-06-19 12:29 ` [PATCH 3/5] ARM: dts: stm32: remove fixed regulator unit address on stm32429i-eval Fabrice Gasnier
2019-06-19 12:29 ` [PATCH 4/5] ARM: dts: stm32: add missing vdda-supply to adc " Fabrice Gasnier
2019-06-19 12:29 ` [PATCH 5/5] ARM: dts: stm32: add missing vdda-supply to adc on stm32h743i-eval Fabrice Gasnier
2019-07-26 16:00 ` [PATCH 0/5] Add missing vdda-supply to STM32 ADC Alexandre Torgue
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=20190622103636.63148958@archlinux \
--to=jic23@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@st.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@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).