linux-kernel - Re: [PATCH 1/2] dt-bindings: usb-ehci: Add an optional property "needs-reset-on-resume"

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 22 Dec 2014 09:06:51 -0800
From:	Doug Anderson <dianders@...gle.com>
To:	Wu Liang feng <wulf@...k-chips.com>
Cc:	Heiko Stübner <heiko@...ech.de>,
	Tao Huang <huangtao@...k-chips.com>,
	Kever Yang <kever.yang@...k-chips.com>,
	Eddie Cai <eddie.cai@...k-chips.com>,
	Roy Li <roy.li@...k-chips.com>, Chris <zyw@...k-chips.com>,
	Julius Werner <jwerner@...gle.com>,
	Pawel Osciak <posciak@...gle.com>,
	Tomasz Figa <tfiga@...gle.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: usb-ehci: Add an optional property "needs-reset-on-resume"

Wu Liang feng,

On Mon, Dec 22, 2014 at 2:36 AM, Wu Liang feng <wulf@...k-chips.com> wrote:
> Add device-tree bindings for EHCI so we can use "needs-reset-on-resume"
> property to force EHCI reset after resume if necessary. This is necessary
> on platforms like rk3288 that need a reset after resume to detect if a
> device has been disconnected during suspend time.
>
> Signed-off-by: Wu Liang feng <wulf@...k-chips.com>
> ---
>  Documentation/devicetree/bindings/usb/usb-ehci.txt | 1 +
>  1 file changed, 1 insertion(+)

It may not count for much given my lack of experience with the USB
subsystem, but I'll give it anyway:

Reviewed-by: Doug Anderson <dianders@...omium.org>

-Doug
--
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/