From: Jonathan Cameron <jic23@kernel.org>
To: Fabrice Gasnier <fabrice.gasnier@st.com>
Cc: <robh+dt@kernel.org>, <linux@armlinux.org.uk>,
<mark.rutland@arm.com>, <mcoquelin.stm32@gmail.com>,
<alexandre.torgue@st.com>, <lars@metafoo.de>, <knaack.h@gmx.de>,
<pmeerw@pmeerw.net>, <benjamin.gaignard@linaro.org>,
<benjamin.gaignard@st.com>, <linux-iio@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/4] ARM: dts: stm32: Add DAC support on stm32f429
Date: Mon, 10 Jul 2017 21:56:07 +0100 [thread overview]
Message-ID: <20170710215607.1ef3caae@kernel.org> (raw)
In-Reply-To: <1499693040-12994-5-git-send-email-fabrice.gasnier@st.com>
On Mon, 10 Jul 2017 15:24:00 +0200
Fabrice Gasnier <fabrice.gasnier@st.com> wrote:
> Add support for DAC (Digital to Analog Converter) to STM32F429.
> STM32F429 DAC has two output channels.
>
> Signed-off-by: Fabrice Gasnier <fabrice.gasnier@st.com>
Driver support is working it's way towards mainline, though will be
next merge window now so no real rush on this one!
Acked-by: Joanthan Cameron <Jonathan.Cameron@huawei.com>
> ---
> arch/arm/boot/dts/stm32f429.dtsi | 25 +++++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/arch/arm/boot/dts/stm32f429.dtsi b/arch/arm/boot/dts/stm32f429.dtsi
> index b2a2b5c..f15f633 100644
> --- a/arch/arm/boot/dts/stm32f429.dtsi
> +++ b/arch/arm/boot/dts/stm32f429.dtsi
> @@ -354,6 +354,31 @@
> status = "disabled";
> };
>
> + dac: dac@40007400 {
> + compatible = "st,stm32f4-dac-core";
> + reg = <0x40007400 0x400>;
> + resets = <&rcc STM32F4_APB1_RESET(DAC)>;
> + clocks = <&rcc 0 STM32F4_APB1_CLOCK(DAC)>;
> + clock-names = "pclk";
> + #address-cells = <1>;
> + #size-cells = <0>;
> + status = "disabled";
> +
> + dac1: dac@1 {
> + compatible = "st,stm32-dac";
> + #io-channels-cells = <1>;
> + reg = <1>;
> + status = "disabled";
> + };
> +
> + dac2: dac@2 {
> + compatible = "st,stm32-dac";
> + #io-channels-cells = <1>;
> + reg = <2>;
> + status = "disabled";
> + };
> + };
> +
> usart7: serial@40007800 {
> compatible = "st,stm32-usart", "st,stm32-uart";
> reg = <0x40007800 0x400>;
next prev parent reply other threads:[~2017-07-10 20:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 13:23 [PATCH 0/4] Add support for STM32F4 DAC Fabrice Gasnier
2017-07-10 13:23 ` [PATCH 1/4] dt-bindings: iio: stm32-dac: add support for STM32F4 Fabrice Gasnier
2017-07-10 20:51 ` Jonathan Cameron
2017-07-14 14:41 ` Rob Herring
2017-07-10 13:23 ` [PATCH 2/4] iio: dac: stm32: fix error message Fabrice Gasnier
2017-07-10 20:51 ` Jonathan Cameron
2017-07-10 13:23 ` [PATCH 3/4] iio: dac: stm32: add support for stm32f4 Fabrice Gasnier
2017-07-10 20:54 ` Jonathan Cameron
2017-07-10 13:24 ` [PATCH 4/4] ARM: dts: stm32: Add DAC support on stm32f429 Fabrice Gasnier
2017-07-10 20:56 ` Jonathan Cameron [this message]
2017-07-27 7:29 ` 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=20170710215607.1ef3caae@kernel.org \
--to=jic23@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=benjamin.gaignard@linaro.org \
--cc=benjamin.gaignard@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@armlinux.org.uk \
--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).