linux-kernel - Re: USB: OMAP: questions on patch "Implement runtime idling and remote wakeup for OMAP EHCI controller"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <5344FE61.4030306@ti.com>
Date:	Wed, 9 Apr 2014 11:01:37 +0300
From:	Roger Quadros <rogerq@...com>
To:	Chao Xu <caesarxuchao@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	<stern@...land.harvard.edu>
Subject: Re: USB: OMAP: questions on patch "Implement runtime idling and remote
 wakeup for OMAP EHCI controller"

Hi,

On 04/09/2014 07:12 AM, Chao Xu wrote:
> Hi,
> 
> I have two questions about this patch series. Any help is appreciated.
> 1. in the cover letter(https://lkml.org/lkml/2013/7/10/355), it states
> "the series implements suspend/resume for the OMAP EHCI host
> controller during runtime idle". I don't understand when is the EHCI
> host controller "runtime idle"? Does "runtime idle" refers to when all
> attached USB devices are suspended? or does it refer to whenever there
> is no tx/rx ongoing in the EHCI host controller?

It refers to when all USB devices are auto-suspended.

> 
> 2. I think the purpose of the patch is to allow the USB power domain
> (namely, L3INIT power domain) to enter low power state. So assuming

Right.

> the power domain is now in RETENTION state, will the EHCI host be able
> to detect remote wakeup in this case? i.e. will the ULPI DATA0, DATA1
> and DATA3 reflect the Linestate and Interrupt when the L3INIT power
> domain is in RETENTION? Put it in another way, when the power domain
> in is a low power state defined in OMAP spec, is the USB host and PHY
> in  "low power mode" defined in USB spec?

The OMAP EHCI controller is not running and the OMAP USB_HS module is
idle as well and so it can't detect any changes on the ULPI lines.
The PHY is in low power state and should reflect the line status on the DAT0-1
lines.

During the suspended state, we use the IOring mechanism to detect a changed on DAT lines
and wake up the controller/system.

cheers,
-roger

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/