[RFC PATCH 4/6] USB: ehci-omap: Suspend the controller during bus suspend
balbi at ti.com
Mon Jul 1 12:49:20 EDT 2013
On Mon, Jul 01, 2013 at 12:24:07PM -0400, Alan Stern wrote:
> On Mon, 1 Jul 2013, Roger Quadros wrote:
> > On 06/28/2013 10:06 PM, Alan Stern wrote:
> > > On Fri, 28 Jun 2013, Roger Quadros wrote:
> > >
> > >>> That's not what I meant. Never mind the pinctrl; I was asking about
> > >>> the EHCI controller itself. Under what circumstances does the
> > >>> controller assert its wakeup signal? And how do you tell it to stop
> > >>> asserting that signal?
> > >>
> > >> I believe this would be through the EHCI Interrupt enable register (USBINTR).
> > >> I'm not aware of any other mechanism.
> > >
> > > That's strange, because ehci_suspend() sets the intr_enable register to
> > > 0. So how do you ever get any wakeup interrupts at all?
> > Because after ehci_suspend() for OMAP, we solely rely on the out of band wake up
> > mechanism. i.e. Pad wakeup.
> I don't know what Pad wakeup is. The wakeup signal has to originate
> from the EHCI controller, doesn't it? If not, how does the Pad know
> when a wakeup is needed?
That's really an OMAP thing, I guess. Pad wakeup sits in the PRCM (IIRC)
inside and always on power domain. EHCI sits in another power domain
which be turned off. When it's turned off (power gated and clock gated)
the EHCI block has no means to wakeup whatsoever. That's when pad wakeup
comes into play. It is generated when PRCM sees a change in the actual
pad of the die. To check who should 'own' the wakeup, it checks the
muxing settings to verify whose pad is that.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 836 bytes
Desc: Digital signature
More information about the linux-arm-kernel