From: Dmitry Torokhov <dtor@insightbb.com>
To: linux-input@atrey.karlin.mff.cuni.cz
Cc: Jiri Kosina <jikos@jikos.cz>,
Torsten Kaiser <just.for.lkml@googlemail.com>,
Adrian Bunk <bunk@kernel.org>, Nick Sillik <n.sillik@temple.edu>,
David Brownell <david-b@pacbell.net>,
Greg Kroah-Hartman <gregkh@suse.de>,
linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [RFC: 2.6 patch] remove the USB_STORAGE_ONETOUCH driver
Date: Sun, 28 Oct 2007 22:38:10 -0400 [thread overview]
Message-ID: <200710282238.11692.dtor@insightbb.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0710282134020.18815@twin.jikos.cz>
On Sunday 28 October 2007 16:39, Jiri Kosina wrote:
> On Sun, 28 Oct 2007, Torsten Kaiser wrote:
>
> > But it looks like that uses another driver:
> > hiddev0hidraw1: USB HID v1.10 Device [Western Digital External HDD] on
> > usb-0000:00:02.1-5.2
> > Otherwise I would be willing to try to test this, if someone would tell
> > me how to check that the second commit did fix the suspend problem.
>
> If you need to unbind usbhid driver from the device and bind another one,
> you can use the 'unbind' and 'bind' files in sysfs.
>
> As soon as the driver you are willing to test is bound to the device, you
> can go ahead with testing any functionality you wish (probably
> suspend/resume cycle is needed here?).
>
> If the device is claimed by usbhid driver (because its descriptor probably
> states that it's HID-compliant device) and should be claimed by another
> driver, it's necessary to add it to usbhid blacklist -- just let me know.
>
Maybe onetouch driver is not needed after all. I wonder what key/button does
HID deriver reports when it binds to it... Torsten, could you please post
your /proc/bus/input/devices?
--
Dmitry
next prev parent reply other threads:[~2007-10-29 2:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-28 15:52 [RFC: 2.6 patch] remove the USB_STORAGE_ONETOUCH driver Adrian Bunk
2007-10-28 17:48 ` Torsten Kaiser
2007-10-28 20:39 ` Jiri Kosina
2007-10-29 2:38 ` Dmitry Torokhov [this message]
2007-10-29 6:01 ` Torsten Kaiser
2007-10-29 14:22 ` [linux-usb-devel] " Alan Stern
2007-10-29 14:28 ` Jiri Kosina
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=200710282238.11692.dtor@insightbb.com \
--to=dtor@insightbb.com \
--cc=bunk@kernel.org \
--cc=david-b@pacbell.net \
--cc=gregkh@suse.de \
--cc=jikos@jikos.cz \
--cc=just.for.lkml@googlemail.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=n.sillik@temple.edu \
/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