linux-kernel - Re: [PATCH] [RFC] usb: host: Allow userspace to control usb suspend flows

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAOuDEK3YcHxm4H2+n1r5KZoFK9PG9+XeJD49FCKaeX+KFhkrzQ@mail.gmail.com>
Date: Fri, 2 Feb 2024 00:00:00 +0800
From: Guan-Yu Lin <guanyulin@...gle.com>
To: Oliver Neukum <oneukum@...e.com>
Cc: Alan Stern <stern@...land.harvard.edu>, gregkh@...uxfoundation.org, 
	mathias.nyman@...el.com, royluo@...gle.com, hadess@...ess.net, 
	benjamin.tissoires@...hat.com, heikki.krogerus@...ux.intel.com, 
	grundler@...omium.org, yajun.deng@...ux.dev, dianders@...omium.org, 
	linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org, badhri@...gle.com, 
	albertccwang@...gle.com, pumahsu@...gle.com
Subject: Re: [PATCH] [RFC] usb: host: Allow userspace to control usb suspend flows

On Thu, Feb 1, 2024 at 5:38 PM Oliver Neukum <oneukum@...e.com> wrote:
>
>
>
> On 01.02.24 10:02, Guan-Yu Lin wrote:
> > On Wed, Jan 31, 2024 at 1:12 AM Alan Stern <stern@...land.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
>

Hi,

Given that in our use case the co-processor only supports USB subsystem, I'd
like to proceed with adding the attribute exclusively within the USB subsystem.
Please let me know if there is any further consideration, thanks.