From: Puma Hsu <pumahsu@google.com>
To: gregkh@linuxfoundation.org, mka@chromium.org, dianders@chromium.org
Cc: albertccwang@google.com, raychi@google.com, howardyen@google.com,
leejj@google.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, Puma Hsu <pumahsu@google.com>
Subject: [PATCH 0/2] add vendor hooks for usb suspend and resume
Date: Wed, 14 Dec 2022 15:06:48 +0800 [thread overview]
Message-ID: <20221214070650.703793-1-pumahsu@google.com> (raw)
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 vendor hooks in
suspend and resume functions, and also upload our implementations for
reference.
Puma Hsu (2):
usb: core: add vendor hook for usb suspend and resume
usb: core: add implementations for usb suspend/resume hooks
drivers/usb/core/Makefile | 2 +-
drivers/usb/core/driver.c | 36 +++++++++++++
drivers/usb/core/usb-hooks-impl-goog.c | 72 ++++++++++++++++++++++++++
drivers/usb/core/usb.h | 5 ++
4 files changed, 114 insertions(+), 1 deletion(-)
create mode 100644 drivers/usb/core/usb-hooks-impl-goog.c
--
2.39.0.rc1.256.g54fd8350bd-goog
next reply other threads:[~2022-12-14 7:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 7:06 Puma Hsu [this message]
2022-12-14 7:06 ` [PATCH 1/2] usb: core: add vendor hook " Puma Hsu
2022-12-14 7:20 ` Puma Hsu
2022-12-14 7:36 ` Christoph Hellwig
2022-12-14 8:20 ` Greg KH
2022-12-14 9:38 ` kernel test robot
2022-12-14 9:38 ` kernel test robot
2022-12-14 10:59 ` kernel test robot
2022-12-14 7:06 ` [PATCH 2/2] usb: core: add implementations for usb suspend/resume hooks Puma Hsu
2022-12-14 8:21 ` Greg KH
2022-12-14 9:48 ` kernel test robot
2022-12-19 12:32 ` kernel test robot
2022-12-14 8:17 ` [PATCH 0/2] add vendor hooks for usb suspend and resume 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=20221214070650.703793-1-pumahsu@google.com \
--to=pumahsu@google.com \
--cc=albertccwang@google.com \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.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=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
all inboxes | Powered by JetHome®