From: Felipe Balbi <balbi@ti.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
David Cohen <david.a.cohen@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Stephen Boyd <sboyd@codeaurora.org>,
Baolu Lu <baolu.lu@linux.intel.com>,
Paul Bolle <pebolle@tiscali.nl>, <linux-usb@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [̈́PATCHv4 10/12] usb: dwc3: add ULPI interface support
Date: Fri, 8 May 2015 11:04:36 -0500 [thread overview]
Message-ID: <20150508160436.GC16571@saruman.tx.rr.com> (raw)
In-Reply-To: <20150508160033.GB16571@saruman.tx.rr.com>
[-- Attachment #1: Type: text/plain, Size: 730 bytes --]
On Fri, May 08, 2015 at 11:00:33AM -0500, Felipe Balbi wrote:
> On Fri, May 08, 2015 at 01:08:41PM +0300, Heikki Krogerus wrote:
> > > diff --git a/drivers/usb/dwc3/Kconfig b/drivers/usb/dwc3/Kconfig
> > > index 827c4f8..6f92b36 100644
> > > --- a/drivers/usb/dwc3/Kconfig
> > > +++ b/drivers/usb/dwc3/Kconfig
> > > @@ -11,6 +11,13 @@ config USB_DWC3
> > >
> > > if USB_DWC3
> > >
> > > +config USB_DWC3_ULPI
> > > + bool "Register ULPI PHY Interface"
> > > + depends on USB_ULPI_BUS
> >
> > Felipe, I need to change this as well to support ULPI bus as a module:
> >
> > depends on USB_ULPI_BUS=y || USB_ULPI_BUS=USB_DWC3
>
> fair enough :-)
BTW, are you sending a new series ?
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-05-08 16:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 6:19 [̈́PATCHv4 00/12] usb: ulpi bus Heikki Krogerus
2015-05-07 6:19 ` [̈́PATCHv4 01/12] usb: add bus type for USB ULPI Heikki Krogerus
2015-05-07 20:46 ` Greg Kroah-Hartman
2015-05-08 9:56 ` Heikki Krogerus
2015-05-07 6:19 ` [̈́PATCHv4 02/12] usb: dwc3: USB2 PHY register access bits Heikki Krogerus
2015-05-07 6:19 ` [̈́PATCHv4 03/12] usb: dwc3: ULPI or UTMI+ select Heikki Krogerus
2015-05-07 6:19 ` [̈́PATCHv4 04/12] usb: dwc3: store driver data earlier Heikki Krogerus
2015-05-07 6:19 ` [̈́PATCHv4 05/12] usb: dwc3: cache hwparams earlier Heikki Krogerus
2015-05-07 6:19 ` [̈́PATCHv4 06/12] usb: dwc3: soft reset to it's own function Heikki Krogerus
2015-05-07 6:19 ` [̈́PATCHv4 07/12] usb: dwc3: setup phys earlier Heikki Krogerus
2015-05-07 6:19 ` [̈́PATCHv4 08/12] usb: dwc3: add hsphy_interface property Heikki Krogerus
2015-05-07 6:19 ` [̈́PATCHv4 09/12] usb: dwc3: pci: add quirk for Baytrails Heikki Krogerus
2015-05-07 18:52 ` Felipe Balbi
2015-05-07 18:53 ` Felipe Balbi
2015-05-07 6:19 ` [̈́PATCHv4 10/12] usb: dwc3: add ULPI interface support Heikki Krogerus
2015-05-08 10:08 ` Heikki Krogerus
2015-05-08 16:00 ` Felipe Balbi
2015-05-08 16:04 ` Felipe Balbi [this message]
2015-05-11 9:54 ` Heikki Krogerus
2015-05-07 6:19 ` [̈́PATCHv4 11/12] phy: helpers for USB ULPI PHY registering Heikki Krogerus
2015-05-07 18:55 ` Felipe Balbi
2015-05-08 5:32 ` Kishon Vijay Abraham I
2015-05-07 6:19 ` [̈́PATCHv4 12/12] phy: add driver for TI TUSB1210 ULPI PHY Heikki Krogerus
2015-05-08 5:33 ` Kishon Vijay Abraham I
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=20150508160436.GC16571@saruman.tx.rr.com \
--to=balbi@ti.com \
--cc=baolu.lu@linux.intel.com \
--cc=david.a.cohen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=sboyd@codeaurora.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