From: Felipe Balbi <balbi@ti.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: Felipe Balbi <balbi@ti.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Baolu Lu <baolu.lu@linux.intel.com>, <linux-usb@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] phy: ulpi: add driver for TI TUSB1210
Date: Thu, 22 Jan 2015 14:51:24 -0600 [thread overview]
Message-ID: <20150122205124.GG22288@saruman.tx.rr.com> (raw)
In-Reply-To: <20150121113958.GC22716@kuha.fi.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1540 bytes --]
On Wed, Jan 21, 2015 at 01:39:58PM +0200, Heikki Krogerus wrote:
> Hi,
>
> On Wed, Jan 21, 2015 at 11:17:49AM +0200, Heikki Krogerus wrote:
> > On Tue, Jan 20, 2015 at 09:45:39AM -0600, Felipe Balbi wrote:
> > > > diff --git a/drivers/phy/ulpi/tusb1210.c b/drivers/phy/ulpi/tusb1210.c
> > > > new file mode 100644
> > > > index 0000000..ac77f98
> > > > --- /dev/null
> > > > +++ b/drivers/phy/ulpi/tusb1210.c
> > >
> > > do you really need this extra ulpi directory ?
> > >
> > > I wonder if phy-tusb1210.c as a name would be enough.
> >
> > IMO grouping the ULPI PHY drivers and other ULPI bus code into
> > separate folder from the start is the right thing to do.
>
> A correction to this comment. I probable don't need this folder. Like
> you said, phy-tusb1210.c should be enough..
>
> <snip>
>
> > > In fact, we might decide to add an entire ULPI bus, eventually, though
> > > I'm still considering if there's any benefit to that.
> >
> > I don't think I understand this comment? ULPI bus is what I'm
> > introducing in this set (the first patch in it)?
>
> ..I talked with Alex about this :). So I think the bus belongs under
> drivers/usb/core/ instead of driver/phy/. It's not really tied to the
> Generic PHY framework in any way, but ULPI is of course USB specific.
right, maybe drivers/usb/ulpi or maybe drivers/ulpi, and have
phy-tusb1201 register under that ulpi_bus_type instead of
platform_bus_type, but still use drivers/phy to register itself a phy
provider ;-)
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-01-22 20:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 9:18 [PATCH 0/3] phy: ulpi bus Heikki Krogerus
2015-01-20 9:18 ` [PATCH 1/3] phy: add bus for USB ULPI PHYs Heikki Krogerus
2015-01-20 9:18 ` [PATCH 2/3] usb: dwc3: add ULPI interface support Heikki Krogerus
2015-01-20 15:23 ` Felipe Balbi
2015-01-21 8:58 ` Heikki Krogerus
2015-01-20 9:18 ` [PATCH 3/3] phy: ulpi: add driver for TI TUSB1210 Heikki Krogerus
2015-01-20 15:45 ` Felipe Balbi
2015-01-21 9:17 ` Heikki Krogerus
2015-01-21 11:39 ` Heikki Krogerus
2015-01-22 20:51 ` Felipe Balbi [this message]
2015-01-23 8:23 ` Heikki Krogerus
2015-01-23 16:16 ` Felipe Balbi
2015-01-22 20:49 ` Felipe Balbi
2015-01-23 8:12 ` Heikki Krogerus
2015-01-23 16:18 ` Felipe Balbi
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=20150122205124.GG22288@saruman.tx.rr.com \
--to=balbi@ti.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=kishon@ti.com \
--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