[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2025072637-corny-careless-8523@gregkh>
Date: Sat, 26 Jul 2025 08:43:16 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Cristian Ciocaltea <cristian.ciocaltea@...labora.com>
Cc: Valentina Manea <valentina.manea.m@...il.com>,
Shuah Khan <shuah@...nel.org>, Hongren Zheng <i@...ithal.me>,
"Brian G. Merrell" <bgmerrell@...ell.com>, kernel@...labora.com,
Greg Kroah-Hartman <gregkh@...e.de>, linux-usb@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 00/18] USB/IP VHCI suspend fix and driver cleanup
On Sat, Jul 26, 2025 at 01:08:02AM +0300, Cristian Ciocaltea wrote:
> The USB/IP Virtual Host Controller (VHCI) platform driver is expected to
> prevent entering system suspend when at least one remote device is
> attached to the virtual USB root hub.
>
> However, in some cases, the detection logic for active USB/IP
> connections doesn't seem to work reliably, e.g. when all devices
> attached to the virtual hub have been already suspended. This will
> normally lead to a broken suspend state, with unrecoverable resume.
>
> The first patch of the series provides a workaround to ensure the
> virtually attached devices do not enter suspend. Note this is currently
> limited to the client side (vhci_hcd) only, since the server side
> (usbip_host) doesn't implement system suspend prevention.
>
> Additionally, during the investigation I noticed and fixed a bunch of
> coding style issues, hence the subsequent patches contain all the
> changes needed to make checkpatch happy for the entire driver.
You are doing two major things here, fixing suspend, and cleaning up
checkpatch issues. Please make that two different patch sets as those
are not logical things to put together at all. Work on the suspend
issue first, and after that is all done and working, then consider
checkpatch cleanups, those are not that important overall :)
thanks,
greg k-h
Powered by blists - more mailing lists