From: Oliver Neukum <oneukum@suse.com>
To: Puma Hsu <pumahsu@google.com>,
gregkh@linuxfoundation.org, mka@chromium.org,
dianders@chromium.org
Cc: 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 10:17:28 +0100 [thread overview]
Message-ID: <c5f24a60-2756-dc99-ee48-99a657a9626c@suse.com> (raw)
In-Reply-To: <20221214081456.714859-1-pumahsu@google.com>
On 14.12.22 09:14, 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.
Ok, before this gets hopelessly unproductive, please describe what
you are aiming at and operating on in greater detail.
It looks to me like you have an audio device that is connected
to the host by USB _and_ another bus. Is that correct?
Will you submit the "subdriver" that drives the device over
that secondary bus?
The operation over the secondary bus requires a hook in USB
power management. Why?
Secondly, the naming is atrocious.
Now could we please first define the technical nature of the issue,
so that we fully understand it before we debate the desirability?
Regards
Oliver
next prev parent reply other threads:[~2022-12-14 9:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 8:14 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 ` [PATCH v2 0/2] add hooks for usb suspend and resume Greg KH
2022-12-14 9:17 ` Oliver Neukum [this message]
[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=c5f24a60-2756-dc99-ee48-99a657a9626c@suse.com \
--to=oneukum@suse.com \
--cc=albertccwang@google.com \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.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
all inboxes | Powered by JetHome®