Messages in this thread | | | From | Guan-Yu Lin <> | Date | Fri, 2 Feb 2024 00:00:00 +0800 | 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@suse.com> wrote: > > > > 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 >
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.
| |