From: Oliver Neukum <oneukum@suse.com>
To: Alan Stern <stern@rowland.harvard.edu>, Hongyu Xie <xy521521@gmail.com>
Cc: oneukum@suse.com, gregkh@linuxfoundation.org, brauner@kernel.org,
jlayton@kernel.org, jack@suse.cz, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, xiehongyu1@kylinos.cn
Subject: Re: [PATCH next] usb: usbfs: Add reset_resume for usbfs
Date: Wed, 17 Jul 2024 17:27:51 +0200 [thread overview]
Message-ID: <dd3583a1-e66d-46e5-aba8-61ffb268f9a7@suse.com> (raw)
In-Reply-To: <5413aa3b-92ba-4367-b720-2fa4161638b5@rowland.harvard.edu>
On 17.07.24 15:44, Alan Stern wrote:
> On Wed, Jul 17, 2024 at 11:13:39AM +0800, Hongyu Xie wrote:
>> From: Hongyu Xie <xiehongyu1@kylinos.cn>
>>
>>
>>
>> On 2024/7/17 10:05, Alan Stern wrote:
>
> That's right, it should be possible to avoid rebinding. But we can't do
> this until we have some way to tell the userspace driver that a reset
> has occurred. Oliver's idea is to do this by returning a special error
> code for the next ioctl, and I can't think of anything better.
I wish you could, for this is supremely inelegant. In particular
it forces user space to reinit the device when it is needed, instead
of when it is idle.
Yet, I think conceptually the first ioctl absolutely must fail,
because the device state has been lost.
Regards
Oliver
next prev parent reply other threads:[~2024-07-17 15:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 8:43 Hongyu Xie
2024-07-11 8:59 ` Oliver Neukum
2024-07-11 14:41 ` Alan Stern
2024-07-15 8:53 ` Oliver Neukum
2024-07-15 14:22 ` Alan Stern
2024-07-16 12:44 ` Oliver Neukum
2024-07-17 1:43 ` Hongyu Xie
2024-07-17 2:05 ` Alan Stern
2024-07-17 3:13 ` Hongyu Xie
2024-07-17 7:52 ` Oliver Neukum
2024-07-17 13:44 ` Alan Stern
2024-07-17 15:27 ` Oliver Neukum [this message]
2024-07-17 7:42 ` Oliver Neukum
2024-07-18 3:23 ` Hongyu Xie
2024-07-12 3:10 ` Hongyu Xie
2024-07-13 2:22 ` Alan Stern
2024-07-15 1:13 ` Hongyu Xie
2024-07-15 8:40 ` Oliver Neukum
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=dd3583a1-e66d-46e5-aba8-61ffb268f9a7@suse.com \
--to=oneukum@suse.com \
--cc=brauner@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=xiehongyu1@kylinos.cn \
--cc=xy521521@gmail.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®