From: Oliver Neukum <oneukum@suse.com>
To: Guan-Yu Lin <guanyulin@google.com>,
Alan Stern <stern@rowland.harvard.edu>
Cc: gregkh@linuxfoundation.org, mathias.nyman@intel.com,
royluo@google.com, hadess@hadess.net,
benjamin.tissoires@redhat.com, heikki.krogerus@linux.intel.com,
oneukum@suse.com, grundler@chromium.org, yajun.deng@linux.dev,
dianders@chromium.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, badhri@google.com,
albertccwang@google.com, pumahsu@google.com
Subject: Re: [PATCH] [RFC] usb: host: Allow userspace to control usb suspend flows
Date: Thu, 1 Feb 2024 10:38:44 +0100 [thread overview]
Message-ID: <09fce208-72b1-49e8-988e-ea149fbaf0b5@suse.com> (raw)
In-Reply-To: <CAOuDEK2VSBcQdLKt27VrLUxH2S22275ffbe5mdVM=vBZDhceQA@mail.gmail.com>
On 01.02.24 10:02, Guan-Yu Lin wrote:
> On Wed, Jan 31, 2024 at 1:12 AM Alan Stern <stern@rowland.harvard.edu> wrote:
>>
>> On Tue, Jan 30, 2024 at 06:47:13AM +0000, Guan-Yu Lin wrote:
>> Why does this affect only the USB subsystem? Can't the co-processor
>> use other, non-USB, devices on the system?
>>
> In our use case, the co-processor only supports USB subsystem. There might be
> other co-processors support more subsystems, but we're not sure about how they
> will interact with the system.
Hi,
it would be very good if you decided this now, before we add attributes.
The reason is that if this feature is needed for multiple subsystems,
the attribute should be added to the generic device structure, so that
the naming and semantics are consistent.
You really don't want to repeat this discussion for every subsystem.
Regards
Oliver
next prev parent reply other threads:[~2024-02-01 9:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 6:47 Guan-Yu Lin
2024-01-30 16:41 ` Greg KH
2024-02-01 7:22 ` Guan-Yu Lin
2024-01-30 17:12 ` Alan Stern
2024-02-01 9:02 ` Guan-Yu Lin
2024-02-01 9:38 ` Oliver Neukum [this message]
2024-02-01 16:00 ` Guan-Yu Lin
2024-02-01 18:06 ` 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=09fce208-72b1-49e8-988e-ea149fbaf0b5@suse.com \
--to=oneukum@suse.com \
--cc=albertccwang@google.com \
--cc=badhri@google.com \
--cc=benjamin.tissoires@redhat.com \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=grundler@chromium.org \
--cc=guanyulin@google.com \
--cc=hadess@hadess.net \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=pumahsu@google.com \
--cc=royluo@google.com \
--cc=stern@rowland.harvard.edu \
--cc=yajun.deng@linux.dev \
/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
Powered by JetHome