All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomas Carnecky <tom@dbservice.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: hid device not claimed but /dev/input/event exists
Date: Tue, 19 Feb 2008 19:11:31 +0100	[thread overview]
Message-ID: <47BB1BD3.3040609@dbservice.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0802191846250.30955@jikos.suse.cz>

Jiri Kosina wrote:
> On Tue, 19 Feb 2008, Tomas Carnecky wrote:
> 
>> The device apparently has four 'interfaces' - whatever that is, see [1]. 
>> It seems like usbhid probes interface 2 (which is the LCD plus a few 
>> buttons, probably the four just under the LCD, as described [1]). 
>> Because usbhid doesn't know how to handle the buttons, it fails. But 
>> then it probes interface 3 which is a 'proper' HID device with 
>> well-defined buttons.
> 
> Yes, the dump clearly shows that.
> 
> Does anything appear in dmesg when you press those buttons? There should 
> be messages resembling the one you already have there:
> 
> drivers/hid/hid-core.c: report (size 8) (unnumbered)
> drivers/hid/hid-core.c: report 0 (size 8) =  00 00 28 00 00 00 00 00
> 
> and they should react to keys such as FastForward, Play, Mute, Volume Up, 
> etc.

Nothing. Not even after I removed the alsa-usb-audio driver. All I see 
is Keyboard.*, but the events from the speaker should be Key.*, right?

It looks like the speaker goes into a different mode once the USB cable 
is plugged in. Without the USB cable, the Z-10 acts as simple/dumb 
speaker, the volume up/down buttons change the internal volume, and I 
see that on the display, too. The play/next/prev song buttons don't do 
anything, which is quite obvious.
But once the USB cable is plugged in, the volume up/down buttons stop 
reacting. I assume they are now meant to send events to the computer so 
that some software can decide what to do. But features that are not 
useful for the computer (bass/treble), can still be controlled using the 
buttons on the speaker. The buttons are not dead. I can see that because 
the display goes to sleep after a few seconds of inactivity, and when I 
press the volume buttons, it wakes up and displays the current volume. 
So the speaker is definitely seeing that the buttons are being pressed.

Is there a USB packet inspector/dumper, like libpcap for network?

tom

  reply	other threads:[~2008-02-19 18:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-19 16:30 hid device not claimed but /dev/input/event exists Tomas Carnecky
2008-02-19 16:51 ` Jiri Kosina
2008-02-19 17:42   ` Tomas Carnecky
2008-02-19 17:48     ` Jiri Kosina
2008-02-19 18:11       ` Tomas Carnecky [this message]
2008-02-19 18:19       ` Tomas Carnecky
2008-02-19 20:03         ` 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=47BB1BD3.3040609@dbservice.com \
    --to=tom@dbservice.com \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.