From: Aurelien Jarno <aurelien@aurel32.net>
To: Amelie Delaunay <amelie.delaunay@st.com>
Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] USB support on stm32mp157 boards
Date: Thu, 5 Dec 2019 23:29:56 +0100 [thread overview]
Message-ID: <20191205222956.GA240447@aurel32.net> (raw)
In-Reply-To: <20191121161152.25541-1-amelie.delaunay@st.com>
On 2019-11-21 17:11, Amelie Delaunay wrote:
> This patchset adds support for USB (Host and OTG) on stm32mp157a-dk1.
> USB OTG HS is forced in Peripheral mode.
> This patchset also fixes USB on stm32mp157c-ev1: USB PHYS supplies were missing
> (CONFIG_REGULATOR_STM32_PWR) and usbotg_hs node requires phy-names property to
> get the phy.
>
> Amelie Delaunay (5):
> ARM: multi_v7_defconfig: enable STM32 PWR regulator
> ARM: dts: stm32: enable USBPHYC on stm32mp157a-dk1
> ARM: dts: stm32: enable USB Host (USBH) EHCI controller on
> stm32mp157a-dk1
> ARM: dts: stm32: enable USB OTG HS on stm32mp157a-dk1
> ARM: dts: stm32: add phy-names to usbotg_hs on stm32mp157c-ev1
>
> arch/arm/boot/dts/stm32mp157a-dk1.dts | 28 +++++++++++++++++++++++++++
> arch/arm/boot/dts/stm32mp157c-ev1.dts | 1 +
> arch/arm/configs/multi_v7_defconfig | 1 +
> 3 files changed, 30 insertions(+)
I tested the series on a stm32mp157c-dk2.
Tested-by: Aurelien Jarno <aurelien@aurel32.net>
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
prev parent reply other threads:[~2019-12-05 22:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 16:11 [PATCH 0/5] USB support on stm32mp157 boards Amelie Delaunay
2019-12-05 22:29 ` Aurelien Jarno [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=20191205222956.GA240447@aurel32.net \
--to=aurelien@aurel32.net \
--cc=alexandre.torgue@st.com \
--cc=amelie.delaunay@st.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=olof@lixom.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).