From: Greg KH <gregkh@linuxfoundation.org>
To: Guan-Yu Lin <guanyulin@google.com>
Cc: mathias.nyman@intel.com, gargaditya08@live.com, kekrby@gmail.com,
jeff.johnson@oss.qualcomm.com, quic_zijuhu@quicinc.com,
andriy.shevchenko@linux.intel.com, ben@decadent.org.uk,
broonie@kernel.org, quic_wcheng@quicinc.com,
krzysztof.kozlowski@linaro.org, sumit.garg@kernel.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v14 0/4] Support system sleep with offloaded usb transfers
Date: Wed, 4 Jun 2025 12:56:00 +0200 [thread overview]
Message-ID: <2025060407-geologic-excuse-9ca5@gregkh> (raw)
In-Reply-To: <20250604082449.2029156-1-guanyulin@google.com>
On Wed, Jun 04, 2025 at 08:23:06AM +0000, Guan-Yu Lin wrote:
> Wesley Cheng and Mathias Nyman's USB offload design enables a co-processor
> to handle some USB transfers, potentially allowing the system to sleep
> (suspend-to-RAM) and save power. However, Linux's System Sleep model halts
> the USB host controller when the main system isn't managing any USB
> transfers. To address this, the proposal modifies the system to recognize
> offloaded USB transfers and manage power accordingly. This way, offloaded
> USB transfers could still happen during system sleep (Suspend-to-RAM).
>
> This involves two key steps:
> 1. Transfer Status Tracking: Propose offload_usage and corresponding apis
> drivers could track USB transfers on the co-processor, ensuring the
> system is aware of any ongoing activity.
> 2. Power Management Adjustment: Modifications to the USB driver stack
> (xhci host controller driver, and USB device drivers) allow the system to
> sleep (Suspend-to-RAM) without disrupting co-processor managed USB
> transfers. This involves adding conditional checks to bypass some power
> management operations in the System Sleep model.
Is there a reason you aren't cc:ing the developers from a "big android
device company" that is currently testing and finding problems with this
patchset in their device testing? I will require their signed-off-by or
tested-by in order to even consider accepting this patch series based on
the issues they seem to be finding with it in an
internal-company-bug-reporting-platform that I seem to be also copied
on.
thanks,
greg k-h
next prev parent reply other threads:[~2025-06-04 10:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 8:23 [PATCH v14 0/4] Support system sleep with offloaded usb transfers Guan-Yu Lin
2025-06-04 8:23 ` [PATCH v14 1/4] usb: xhci-plat: separate dev_pm_ops for each pm_event Guan-Yu Lin
2025-06-04 8:23 ` [PATCH v14 2/4] usb: offload: add apis for offload usage tracking Guan-Yu Lin
2025-06-04 8:23 ` [PATCH v14 3/4] xhci: sideband: add api to trace sideband usage Guan-Yu Lin
2025-06-04 8:23 ` [PATCH v14 4/4] usb: host: enable USB offload during system sleep Guan-Yu Lin
2025-06-04 10:56 ` Greg KH [this message]
2025-06-04 12:32 ` [PATCH v14 0/4] Support system sleep with offloaded usb transfers Guan-Yu Lin
2025-06-19 9:27 ` Greg KH
2025-07-01 15:05 ` Guan-Yu Lin
2025-07-02 4:33 ` Guan-Yu Lin
2025-07-02 5:11 ` Jung Daehwan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2025060407-geologic-excuse-9ca5@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ben@decadent.org.uk \
--cc=broonie@kernel.org \
--cc=gargaditya08@live.com \
--cc=guanyulin@google.com \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=kekrby@gmail.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=quic_wcheng@quicinc.com \
--cc=quic_zijuhu@quicinc.com \
--cc=sumit.garg@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox