From: Felipe Balbi <balbi@ti.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH V2] usb: phy: R-Car Gen2: Use usb_add_phy_dev
Date: Mon, 09 Dec 2013 20:59:19 +0000 [thread overview]
Message-ID: <20131209205919.GB29143@saruman.home> (raw)
In-Reply-To: <1386618033-27670-1-git-send-email-valentine.barshak@cogentembedded.com>
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
On Mon, Dec 09, 2013 at 12:32:37PM -0800, Greg Kroah-Hartman wrote:
> On Tue, Dec 10, 2013 at 12:16:13AM +0400, Valentine wrote:
> > On 12/09/2013 11:41 PM, Felipe Balbi wrote:
> > > Hi,
> > >
> > > On Mon, Dec 09, 2013 at 11:40:33PM +0400, Valentine Barshak wrote:
> > >> Use usb_add_phy_dev instead of usb_add_phy, so that devices can
> > >> be bound to the phy. This is needed to set up USB phy for
> > >> some internal PCI USB host controllers on R-Car Gen2.
> > >>
> > >> Changes from previous version:
> > >> * Fixed function names in the commit log
> > >>
> > >> Signed-off-by: Valentine Barshak <valentine.barshak@cogentembedded.com>
> > >
> > > Was this a regression on v3.13 or can it wait for v3.14 ?
> > >
> >
> > I hope it's OK to have it on 3.13.
> >
> > The major reason for the change is to use the USB HCD phy handling
> > updates that are available now in the usb-next branch of Greg's tree:
> > commit 1ae5799ef6: usb: hcd: Initialize USB phy if needed
>
> But that patch isn't going to Linus until 3.14, so this has to wait
> until then as well.
3.14 it is, thanks
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-12-09 20:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 19:40 [PATCH V2] usb: phy: R-Car Gen2: Use usb_add_phy_dev Valentine Barshak
2013-12-09 19:41 ` Felipe Balbi
2013-12-09 20:16 ` Valentine
2013-12-09 20:32 ` Greg Kroah-Hartman
2013-12-09 20:59 ` Felipe Balbi [this message]
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=20131209205919.GB29143@saruman.home \
--to=balbi@ti.com \
--cc=linux-sh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.