From: Alexandre Torgue <alexandre.torgue@st.com>
To: Ludovic Barre <ludovic.Barre@st.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
Rob Herring <robh+dt@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-watchdog@vger.kernel.org,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 0/3] add iwdg2 support for stm32mp157c
Date: Wed, 20 Jun 2018 12:03:18 +0200 [thread overview]
Message-ID: <18d48b13-2ff8-b27f-9b08-c414477976da@st.com> (raw)
In-Reply-To: <1529481238-15277-1-git-send-email-ludovic.Barre@st.com>
Hi Ludovic
On 06/20/2018 09:53 AM, Ludovic Barre wrote:
> From: Ludovic Barre <ludovic.barre@st.com>
>
> This patch series updates stm32_iwdg driver to manage config
> by compatible. stm32mp1 config requires a pclk clock.
>
> Ludovic Barre (3):
> watchdog: stm32: add pclk feature for stm32mp1
> ARM: dts: stm32: add iwdg2 support for stm32mp157c
> ARM: dts: stm32: add iwdg2 support for stm32mp157c-ed1
>
> .../devicetree/bindings/watchdog/st,stm32-iwdg.txt | 21 +++-
> arch/arm/boot/dts/stm32mp157c-ed1.dts | 5 +
> arch/arm/boot/dts/stm32mp157c.dtsi | 8 ++
> drivers/watchdog/stm32_iwdg.c | 132 ++++++++++++++-------
> 4 files changed, 117 insertions(+), 49 deletions(-)
>
STM32 DT patches looks good to me. I will take them as soon as driver
part is acked.
Regards
Alex
prev parent reply other threads:[~2018-06-20 10:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 7:53 [PATCH V2 0/3] add iwdg2 support for stm32mp157c Ludovic Barre
2018-06-20 7:53 ` [PATCH V2 1/3] watchdog: stm32: add pclk feature for stm32mp1 Ludovic Barre
2018-06-20 9:19 ` Guenter Roeck
2018-06-20 13:24 ` Ludovic BARRE
2018-06-20 13:29 ` Guenter Roeck
2018-06-20 13:35 ` Ludovic BARRE
2018-06-20 7:53 ` [PATCH V2 2/3] ARM: dts: stm32: add iwdg2 support for stm32mp157c Ludovic Barre
2018-06-20 7:53 ` [PATCH V2 3/3] ARM: dts: stm32: add iwdg2 support for stm32mp157c-ed1 Ludovic Barre
2018-06-20 10:03 ` Alexandre Torgue [this message]
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=18d48b13-2ff8-b27f-9b08-c414477976da@st.com \
--to=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=ludovic.Barre@st.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh+dt@kernel.org \
--cc=wim@linux-watchdog.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).