[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAODwPW9-5abTDGwLyNRZ0hvn4+6T8ix55TqFhSy_xZx1VVuVNA@mail.gmail.com>
Date: Wed, 8 Jul 2015 12:41:51 -0700
From: Julius Werner <jwerner@...omium.org>
To: Alan Stern <stern@...land.harvard.edu>
Cc: Julius Werner <jwerner@...omium.org>, Felipe Balbi <balbi@...com>,
Douglas Anderson <dianders@...omium.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
John Youn <johnyoun@...opsys.com>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
Chris Zhong <zyw@...k-chips.com>,
Heiko Stuebner <heiko@...ech.de>,
Andrew Bresticker <abrestic@...omium.org>,
Alexandru Stan <amstan@...omium.org>, lyz <lyz@...k-chips.com>,
"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [REPOST PATCH 3/3] USB: dwc2: Don't turn off the usbphy in
suspend if wakeup is enabled
> But I don't see how you will make it work when the root hub itself is
> not enabled for wakeup and a non-hub device plugged into one of the
> root hub's ports is enabled.
>
> It seems like you would need a usb_hcd_wakeup_not_needed(hcd, port)
> subroutine.
We'd just put that in the Tegra platform driver, I guess. Iterate over
all ports, call usb_wakeup_enabled_descendants() on the connected
device (if any) and disable that port's PHY if it returns 0 or wasn't
connected. Since usb_wakeup_enabled_descendants() also counts
do_remote_wakeup from the device itself and is safe to call even on
non-hubs, that should work for all cases.
--
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/
Powered by blists - more mailing lists