From: Rob Herring <robh@kernel.org>
To: Fabrice Gasnier <fabrice.gasnier@st.com>
Cc: jic23@kernel.org, alexandre.torgue@st.com, mark.rutland@arm.com,
mcoquelin.stm32@gmail.com, lars@metafoo.de, knaack.h@gmx.de,
pmeerw@pmeerw.net, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, benjamin.gaignard@linaro.org
Subject: Re: [PATCH v2 1/3] dt-bindings: iio: stm32-adc: add support for STM32MP1
Date: Mon, 7 May 2018 11:28:31 -0500 [thread overview]
Message-ID: <20180507162830.GA11497@rob-hp-laptop> (raw)
In-Reply-To: <1525247091-18143-2-git-send-email-fabrice.gasnier@st.com>
On Wed, May 02, 2018 at 09:44:49AM +0200, Fabrice Gasnier wrote:
> Document support for STM32MP1 ADC. It's quite similar to STM32H7 ADC.
> Introduce "st,stm32mp1-adc" compatible to handle variants of this
> hardware such as vregready flag, interrupts, clock rate.
>
> Signed-off-by: Fabrice Gasnier <fabrice.gasnier@st.com>
> ---
> Changes in v2:
> - Update dt-bindings following Rob's remark: STM32MP1 ADC has two
> interrupt lines
> ---
> Documentation/devicetree/bindings/iio/adc/st,stm32-adc.txt | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2018-05-07 16:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 7:44 [PATCH v2 0/3] Add support for STM32MP1 ADC Fabrice Gasnier
2018-05-02 7:44 ` [PATCH v2 1/3] dt-bindings: iio: stm32-adc: add support for STM32MP1 Fabrice Gasnier
2018-05-07 16:28 ` Rob Herring [this message]
2018-05-07 17:20 ` Jonathan Cameron
2018-05-02 7:44 ` [PATCH v2 2/3] iio: adc: " Fabrice Gasnier
2018-05-07 17:21 ` Jonathan Cameron
2018-05-02 7:44 ` [PATCH v2 3/3] ARM: dts: stm32: Add ADC support to stm32mp157c Fabrice Gasnier
2018-05-07 17:23 ` Jonathan Cameron
2018-05-22 15:51 ` Fabrice Gasnier
2018-05-06 17:54 ` [PATCH v2 0/3] Add support for STM32MP1 ADC 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=20180507162830.GA11497@rob-hp-laptop \
--to=robh@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=benjamin.gaignard@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@st.com \
--cc=jic23@kernel.org \
--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=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=pmeerw@pmeerw.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