From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Felipe Balbi <balbi@kernel.org>
Cc: Manu Gautam <mgautam@codeaurora.org>,
Rob Herring <robh+dt@kernel.org>,
Andy Gross <andy.gross@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 2/2] usb: dwc3: Add Qualcomm DWC3 glue driver
Date: Wed, 14 Mar 2018 15:40:03 +0200 [thread overview]
Message-ID: <20180314134003.GB10347@kuha.fi.intel.com> (raw)
In-Reply-To: <87woyfrqgr.fsf@linux.intel.com>
Hi,
On Wed, Mar 14, 2018 at 10:50:12AM +0200, Felipe Balbi wrote:
> >>> - Support to replace pip3 clock going to DWC3 with utmi clock
> >>> for hardware configuration where SSPHY is not used with DWC3.
> >> Is that SW configurable? Really? In any case seems like this and SESSVLD
> >> valid should be handled using Hans' and Heikki's mux support.
> >
> > Yes, with this we can use dwc3 without using SSPHY. Please point me to
> > those patches. There are only bunch of register writes in glue wrapper to
> > achieve the same.
>
> https://www.spinics.net/lists/linux-usb/msg160868.html
I'm not sure if that series is usable in this case. Though we do
control the VBUSVLD pin on DWC3 in the driver for the "Intel USB
mux" Hans is introducing, the framework for the USB role switches does
not provide any support for it.
The Intel USB mux driver simply enables VBUSVLD when device mode is
selected, and disables it if host mode is selected, and when the
selection is cleared (disconnection).
Br,
--
heikki
next prev parent reply other threads:[~2018-03-14 13:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 10:36 [PATCH v1 1/2] dt-bindings: usb: Update documentation for Qualcomm DWC3 driver Manu Gautam
2018-03-13 10:36 ` [PATCH v1 2/2] usb: dwc3: Add Qualcomm DWC3 glue driver Manu Gautam
2018-03-13 11:08 ` Felipe Balbi
2018-03-14 4:39 ` Manu Gautam
2018-03-14 8:50 ` Felipe Balbi
2018-03-14 13:40 ` Heikki Krogerus [this message]
2018-03-15 8:16 ` Manu Gautam
2018-03-14 4:21 ` kbuild test robot
2018-03-14 10:46 ` kbuild test robot
2018-03-18 12:49 ` [PATCH v1 1/2] dt-bindings: usb: Update documentation for Qualcomm DWC3 driver Rob Herring
2018-03-19 4:20 ` Manu Gautam
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=20180314134003.GB10347@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=andy.gross@linaro.org \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mgautam@codeaurora.org \
--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
all inboxes | Powered by JetHome®