From: Alexandre Torgue <alexandre.torgue@st.com>
To: Amelie Delaunay <amelie.delaunay@st.com>,
Rob Herring <robh+dt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Badhri Jagan Sridharan <badhri@google.com>,
Jun Li <lijun.kernel@gmail.com>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-usb@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
Fabrice Gasnier <fabrice.gasnier@st.com>
Subject: Re: [PATCH v5 0/5] STUSB1600 support on STM32MP15xx-DKx
Date: Tue, 17 Nov 2020 10:30:09 +0100 [thread overview]
Message-ID: <bfc72326-9de1-10dc-d40f-8b75a3b048dc@st.com> (raw)
In-Reply-To: <20201106165805.31534-1-amelie.delaunay@st.com>
Hi,
On 11/6/20 5:58 PM, Amelie Delaunay wrote:
> This series adds missing bindings for Type-C typec-power-opmode property
> and STUSB160x Type-C port controllers [1].
> STUSB160x driver requires to get power operation mode via device tree,
> that's why this series also adds the optional DT property
> typec-power-opmode for usb-c-connector to select the power operation mode
> capability.
> Tested on stm32mp157c-dk2 [2], which has a Type-C connector managed by
> STUSB1600, and connected to USB OTG controller.
>
> [1] https://www.st.com/en/interfaces-and-transceivers/usb-type-c-and-power-delivery-controllers.html
> [2] https://www.st.com/en/evaluation-tools/stm32mp157c-dk2.html
>
>
> Amelie Delaunay (5):
> dt-bindings: connector: add typec-power-opmode property to
> usb-connector
> dt-bindings: usb: Add DT bindings for STUSB160x Type-C controller
> usb: typec: stusb160x: fix power-opmode property with
> typec-power-opmode
> ARM: dts: stm32: add STUSB1600 Type-C using I2C4 on stm32mp15xx-dkx
> ARM: multi_v7_defconfig: enable STUSB160X Type-C port controller
> support
>
Device tree and bindings patches ([1],[2],[4],[5]) have been applied to
stm32-next (and will go through arm-soc tree).
Greg, I let you apply patch [3] into usb tree.
Thanks
Alex
> ---
> Changes in v5:
> - add additionalProperties to st,stusb160x yaml
> - add Heikki reviewed-by on stusb160x driver patch 3/5
> Changes in v4:
> - power-opmode DT property renamed to typec-power-opmode and mutually
> exclusive condition with new-source-frs-typec-current added
> - Due to DT property renaming, patch 3/5 is added to update stusb160x
> driver.
> ---
> .../bindings/connector/usb-connector.yaml | 24 +++++
> .../devicetree/bindings/usb/st,stusb160x.yaml | 87 +++++++++++++++++++
> arch/arm/boot/dts/stm32mp15-pinctrl.dtsi | 7 ++
> arch/arm/boot/dts/stm32mp15xx-dkx.dtsi | 30 +++++++
> arch/arm/configs/multi_v7_defconfig | 2 +
> drivers/usb/typec/stusb160x.c | 2 +-
> 6 files changed, 151 insertions(+), 1 deletion(-)
> create mode 100644 Documentation/devicetree/bindings/usb/st,stusb160x.yaml
>
prev parent reply other threads:[~2020-11-17 9:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 16:58 [PATCH v5 0/5] STUSB1600 support on STM32MP15xx-DKx Amelie Delaunay
2020-11-06 16:58 ` [PATCH v5 1/5] dt-bindings: connector: add typec-power-opmode property to usb-connector Amelie Delaunay
2020-11-09 15:03 ` Rob Herring
2020-11-09 15:54 ` Amelie DELAUNAY
2020-11-09 16:02 ` Rob Herring
2020-11-09 16:10 ` Amelie DELAUNAY
2020-11-11 20:25 ` Rob Herring
2020-11-06 16:58 ` [PATCH v5 2/5] dt-bindings: usb: Add DT bindings for STUSB160x Type-C controller Amelie Delaunay
2020-11-11 20:26 ` Rob Herring
2020-11-06 16:58 ` [PATCH v5 3/5] usb: typec: stusb160x: fix power-opmode property with typec-power-opmode Amelie Delaunay
2020-11-27 13:01 ` Amelie DELAUNAY
2020-11-27 13:07 ` Greg Kroah-Hartman
2020-11-27 13:12 ` Amelie DELAUNAY
2020-11-06 16:58 ` [PATCH v5 4/5] ARM: dts: stm32: add STUSB1600 Type-C using I2C4 on stm32mp15xx-dkx Amelie Delaunay
2020-11-06 16:58 ` [PATCH v5 5/5] ARM: multi_v7_defconfig: enable STUSB160X Type-C port controller support Amelie Delaunay
2020-11-17 9:30 ` 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=bfc72326-9de1-10dc-d40f-8b75a3b048dc@st.com \
--to=alexandre.torgue@st.com \
--cc=amelie.delaunay@st.com \
--cc=badhri@google.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@st.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=lijun.kernel@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-usb@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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).