[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130129101230.GO8708@arwen.pp.htv.fi>
Date: Tue, 29 Jan 2013 12:12:30 +0200
From: Felipe Balbi <balbi@...com>
To: Roger Quadros <rogerq@...com>
CC: <balbi@...com>, <tony@...mide.com>, <stern@...land.harvard.edu>,
<linux@....linux.org.uk>, <sameo@...ux.intel.com>,
<gregkh@...uxfoundation.org>, <eballetbo@...il.com>,
<javier@...hile0.org>, <sshtylyov@...sta.com>,
<linux-usb@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v3 10/30] USB: ehci-omap: Use PHY APIs to get the PHY
device and put it out of suspend
On Tue, Jan 29, 2013 at 12:08:23PM +0200, Roger Quadros wrote:
> On 01/29/2013 11:57 AM, Felipe Balbi wrote:
> > Hi,
> >
> > On Tue, Jan 29, 2013 at 11:50:32AM +0200, Roger Quadros wrote:
> >> For each port that is in PHY mode we obtain a PHY device using the USB PHY
> >> library and put it out of suspend.
> >>
> >> It is up to platform code to associate the PHY to the controller's
> >> port and it is upto the PHY driver to manage the PHY's resources.
> >>
> >> Also remove wired spacing around declarations we come across.
> >>
> >> Signed-off-by: Roger Quadros <rogerq@...com>
> >
> > ideally, this would be done generically by ehci-hcd.ko itself. Alan,
> > would you have objections provided it doesn't break anyone else ?
> >
> Agreed, and PHY suspend/resume should be done at port granularity.
right.
> But considering the erratas we have in OMAP EHCI, I would still prefer to
> have control of the PHY in ehci-omap. We might even have to do some ULPI
> transfers in certain scenarios to work around some of the erratas.
fair enough, then let's start with your change and make it more generic
later.
--
balbi
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists