From: Prashant Malani <pmalani@chromium.org>
To: linux-kernel@vger.kernel.org
Cc: enric.balletbo@collabora.com, bleung@chromium.org,
groeck@chromium.org, Prashant Malani <pmalani@chromium.org>,
Felipe Balbi <balbi@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org (open list:DESIGNWARE USB3 DRD IP
DRIVER)
Subject: [RFC PATCH 0/1] usb: dwc3: Extcon hotplug support to of-simple
Date: Fri, 22 May 2020 21:12:00 -0700 [thread overview]
Message-ID: <20200523041201.75217-1-pmalani@chromium.org> (raw)
Some platforms like rk3399 would like to power on the USB PHY layer only
when external devices are connected. This patch introduces optional
support for extcon USB_HOST events, so that child devices are
populated/depopulated when external devices are connected/disconnected,
respectively.
This is also useful since some PHY drivers like phy-rockchip-typec only
configure their Type C Phy on power on; if they are only powered on once
at boot by dwc3, these drivers will not be able to reconfigure their PHY
for peripherals plugged in later, like (Display Port) DP monitors.
I thought I’d send out an initial RFC patch, for comments and feedback
about the approach. Depending on feedback, we can refine this approach
and modify the bindings file.
Thanks,
Prashant Malani (1):
usb: dwc3: of-simple: Add extcon support
drivers/usb/dwc3/dwc3-of-simple.c | 149 +++++++++++++++++++++++++++++-
1 file changed, 146 insertions(+), 3 deletions(-)
--
2.27.0.rc0.183.gde8f92d652-goog
next reply other threads:[~2020-05-23 4:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-23 4:12 Prashant Malani [this message]
2020-05-23 4:12 ` [RFC PATCH 1/1] usb: dwc3: of-simple: Add extcon support Prashant Malani
2020-05-28 16:21 ` Guenter Roeck
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=20200523041201.75217-1-pmalani@chromium.org \
--to=pmalani@chromium.org \
--cc=balbi@kernel.org \
--cc=bleung@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.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).