From: Greg KH <gregkh@linuxfoundation.org>
To: Puma Hsu <pumahsu@google.com>
Cc: mka@chromium.org, dianders@chromium.org, albertccwang@google.com,
raychi@google.com, howardyen@google.com, leejj@google.com,
hch@infradead.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] add hooks for usb suspend and resume
Date: Wed, 14 Dec 2022 09:48:56 +0100 [thread overview]
Message-ID: <Y5mN+MLD/8oBU1Ay@kroah.com> (raw)
In-Reply-To: <20221214081456.714859-1-pumahsu@google.com>
On Wed, Dec 14, 2022 at 04:14:54PM +0800, Puma Hsu wrote:
> In mobile, a co-processor can be used for USB audio. When the co-processor
> is working for USB audio, the co-processor is the user/owner of the USB
> driver, and the ACPU is able to sleep in such condition to improve power
> consumption. In order to support this, we need to create hooks in suspend
> and resume functions. We also upload our implementations for reviewing.
>
> Puma Hsu (2):
> usb: core: add hooks for usb suspend and resume
> usb: core: add implementations for usb suspend/resume hooks
>
> drivers/usb/core/driver.c | 36 +++++++++++++
> drivers/usb/core/usb-hooks-impl-goog.c | 72 ++++++++++++++++++++++++++
> drivers/usb/core/usb.h | 5 ++
> 3 files changed, 113 insertions(+)
> create mode 100644 drivers/usb/core/usb-hooks-impl-goog.c
>
> ---
> Changes in v2:
> - Remove the wrong input in the Makefile
> - Change description in commit message
>
> --
> 2.39.0.rc1.256.g54fd8350bd-goog
>
My review comments on v1 still pertain here.
next prev parent reply other threads:[~2022-12-14 8:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 8:14 [PATCH v2 0/2] add hooks for usb suspend and resume Puma Hsu
2022-12-14 8:14 ` [PATCH v2 1/2] usb: core: " Puma Hsu
2022-12-14 8:14 ` [PATCH v2 2/2] usb: core: add implementations for usb suspend/resume hooks Puma Hsu
2022-12-14 8:57 ` Christoph Hellwig
2022-12-14 8:48 ` Greg KH [this message]
2022-12-14 9:17 ` [PATCH v2 0/2] add hooks for usb suspend and resume Oliver Neukum
[not found] ` <CAGCq0LZ6PLF+CCOAU6LSr3DaZ78MQ3kAmKwnXPEtjC76GsRPUg@mail.gmail.com>
2022-12-23 14:52 ` Greg KH
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=Y5mN+MLD/8oBU1Ay@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=albertccwang@google.com \
--cc=dianders@chromium.org \
--cc=hch@infradead.org \
--cc=howardyen@google.com \
--cc=leejj@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mka@chromium.org \
--cc=pumahsu@google.com \
--cc=raychi@google.com \
/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