From: Liyu <raise.sail@gmail.com>
To: Dmitry Torokhov <dtor@insightbb.com>
Cc: "Zephaniah E. Hull" <warp@aehallh.com>, greg <greg@kroah.com>,
Randy Dunlap <rdunlap@xenotime.net>,
LKML <linux-kernel@vger.kernel.org>, Liyu <raise.sail@gmail.com>,
linux-usb-devel <linux-usb-devel@lists.sourceforge.net>
Subject: Re: [linux-usb-devel] [PATCH] usb/hid: The HID Simple Driver Interface 0.3.2 (core)
Date: Mon, 09 Oct 2006 11:28:28 +0800 [thread overview]
Message-ID: <4529C1DC.4030403@gmail.com> (raw)
In-Reply-To: <200610081009.23978.dtor@insightbb.com>
Dmitry Torokhov wrote:
> Yes, I'd consider it a bug. Tearing down and re-creating input device
> generates proper hotplug notifications and userspace needs to respect
> them as capabilities may change even if ids stay the same. For example
> playing with atkbd's scroll attribute will regenerate an input device
> with[out] scroll capabilities but its input_id structure will stay the
> same.
>
So many people said I have some wrongs here ;) it should be truth.
I found our focus is howto or when send notification to userspace.
Intuitional, to reload such device is rather ugly means, it should have
one hotplug message for this case,
and userspace handle it. If only look from design, I will agree with my
argument, however, if also look from compatibility, I think I must agree
your arguments.
At last, you win! :D
I am going to reload.
PS: I found a behavior of usb subsystem, I can not sure whether it is
normal.
After I remove usbhid.ko, the uhci_hcd will reset device repeatly.
usbcore: registered new driver usbhid
/usr/src/redhat/BUILD/linux-2.6.18/drivers/usb/input/hid-core.c:
v2.6:USB HID core driver
usb 5-2: reset low speed USB device using uhci_hcd and address 3
usb 5-2: reset low speed USB device using uhci_hcd and address 3
usb 5-2: reset low speed USB device using uhci_hcd and address 3
usb 5-2: reset low speed USB device using uhci_hcd and address 3
usb 5-2: reset low speed USB device using uhci_hcd and address 3
Goodluck.
-Liyu
next prev parent reply other threads:[~2006-10-09 3:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 8:24 [PATCH] usb/hid: The HID Simple Driver Interface 0.3.2 (core) raise.sail
2006-09-29 16:59 ` Randy Dunlap
2006-09-29 17:35 ` Dmitry Torokhov
2006-10-08 3:07 ` raise.sail
2006-10-08 12:41 ` [linux-usb-devel] " Zephaniah E. Hull
2006-10-08 14:09 ` Dmitry Torokhov
2006-10-09 3:28 ` Liyu [this message]
2006-10-09 3:28 ` Liyu
2006-10-08 18:51 ` Anssi Hannula
2006-10-09 3:35 ` Liyu
2006-10-09 22:52 ` Anssi Hannula
2006-10-09 3:42 ` Dmitry Torokhov
2006-10-09 22:53 ` Anssi Hannula
2006-10-10 5:15 ` Dmitry Torokhov
2006-10-10 7:08 ` Liyu
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=4529C1DC.4030403@gmail.com \
--to=raise.sail@gmail.com \
--cc=dtor@insightbb.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=rdunlap@xenotime.net \
--cc=warp@aehallh.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