From: Amelie Delaunay <amelie.delaunay@st.com>
To: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Amelie Delaunay <amelie.delaunay@st.com>
Subject: [PATCH v2 0/2] Introduce STM32 USB PHY Controller driver
Date: Thu, 1 Mar 2018 16:30:43 +0100 [thread overview]
Message-ID: <1519918245-17333-1-git-send-email-amelie.delaunay@st.com> (raw)
This patchset adds support for STMicroelectronics STM32 USB PHY Controller
(USBPHYC) which is embedded in STM32MP1 SoC.
The STM32 USBPHYC block contains a dual port High Speed UTMI+ PHY and a UTMI
switch that selects either USB OTG controller or USB Host controller for the
second PHY port.
---
Changes in v2:
* Update diagram to better describe the context.
* Change boolean dt propery st,port2-switch-to-host into u32 st,utmi-switch.
* Silent phy creation failure in case of -EPROBE_DEFER.
Amelie Delaunay (2):
dt-bindings: phy: add support for STM32 USB PHY Controller (USBPHYC)
phy: stm32: add support for STM32 USB PHY Controller (USBPHYC)
.../devicetree/bindings/phy/phy-stm32-usbphyc.txt | 46 +++
drivers/phy/st/Kconfig | 14 +
drivers/phy/st/Makefile | 1 +
drivers/phy/st/phy-stm32-usbphyc.c | 382 +++++++++++++++++++++
4 files changed, 443 insertions(+)
create mode 100644 Documentation/devicetree/bindings/phy/phy-stm32-usbphyc.txt
create mode 100644 drivers/phy/st/phy-stm32-usbphyc.c
--
2.7.4
next reply other threads:[~2018-03-01 15:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 15:30 Amelie Delaunay [this message]
2018-03-01 15:30 ` [PATCH v2 1/2] dt-bindings: phy: add support for STM32 USB PHY Controller (USBPHYC) Amelie Delaunay
2018-03-02 6:02 ` Kishon Vijay Abraham I
2018-03-02 14:42 ` Amelie DELAUNAY
2018-03-01 15:30 ` [PATCH v2 2/2] phy: stm32: " Amelie Delaunay
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=1519918245-17333-1-git-send-email-amelie.delaunay@st.com \
--to=amelie.delaunay@st.com \
--cc=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--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).