[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <pzvceukkxvg6qy6ar6tj2lst7k5tyud3uhj5egy6dioeayajtq@3n2gwr35wwnc>
Date: Wed, 4 Feb 2026 13:44:21 +0800
From: Xu Yang <xu.yang_2@....com>
To: Frank Li <Frank.li@....com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>, Pengutronix Kernel Team <kernel@...gutronix.de>,
Fabio Estevam <festevam@...il.com>, Li Jun <jun.li@....com>,
Thinh Nguyen <Thinh.Nguyen@...opsys.com>, linux-usb@...r.kernel.org, devicetree@...r.kernel.org,
imx@...ts.linux.dev, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3] usb: dwc3: add may_lose_power flag
On Mon, Feb 02, 2026 at 10:36:15AM -0500, Frank Li wrote:
> On Mon, Feb 02, 2026 at 06:27:46PM +0800, Xu Yang wrote:
> > The current design assumes that the controller remains powered
> > when wakeup is enabled. However, some SoCs provide wakeup
> > capability even when the controller itself is powered down, using
> > separate dedicated wakeup logic. This allows additional power
> > savings, but requires the controller to be fully re‑initialized
> > after system resume.
> >
> > To support these SoCs, introduce a flag to track the controller’s
> > power state and use it throughout the suspend/resume flow.
>
> Nit: next time, wrap at pos 75 to reduce some lines.
OK.
>
> Reviewed-by: Frank Li <Frank.Li@....com>
> >
> > Signed-off-by: Xu Yang <xu.yang_2@....com>
Powered by blists - more mailing lists