From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Felipe Balbi <balbi@ti.com>,
David Cohen <david.a.cohen@linux.intel.com>,
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 01/12] usb: add bus type for USB ULPI
Date: Fri, 8 May 2015 12:56:21 +0300 [thread overview]
Message-ID: <20150508095621.GA6154@kuha.fi.intel.com> (raw)
In-Reply-To: <20150507204604.GA28684@kroah.com>
On Thu, May 07, 2015 at 10:46:04PM +0200, Greg Kroah-Hartman wrote:
> On Thu, May 07, 2015 at 09:19:21AM +0300, Heikki Krogerus wrote:
> > +config USB_ULPI_BUS
> > + bool "USB ULPI PHY interface support"
>
> Can't we make this a module?
There is actually nothing preventing it.
I removed the possibility of building this as a module at one point
because... I guess just because a voice inside my head told me to do
so. Thanks for catching this one.
> > + depends on USB_SUPPORT
> > + help
> > + Say yes if you have ULPI PHY attached to your USB controller.
>
> You need to put more information here as to what "ULPI" means, and how
> would anyone know if they have this type of thing attached to their USB
> controller.
>
> You need to help users / distros out in letting them know if they should
> enable this or not. As it is, I have no idea if I should even enable
> this on my systems...
OK.
Thanks,
--
heikki
next prev parent reply other threads:[~2015-05-08 9:58 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 [this message]
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
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=20150508095621.GA6154@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=balbi@ti.com \
--cc=baolu.lu@linux.intel.com \
--cc=david.a.cohen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--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