[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100225162932.43ee42a8@neptune.home>
Date: Thu, 25 Feb 2010 16:29:32 +0100
From: Bruno Prémont <bonbons@...ux-vserver.org>
To: Jiri Kosina <jkosina@...e.cz>
Cc: linux-input@...r.kernel.org, linux-usb@...r.kernel.org,
linux-fbdev@...r.kernel.org, linux-kernel@...r.kernel.org,
"Rick L. Vinyard Jr." <rvinyard@...nmsu.edu>,
Nicu Pavel <npavel@...ner.com>
Subject: Re: [PATCH 1/3] picolcd: driver for PicoLCD HID device
On Thu, 25 February 2010 Jiri Kosina <jkosina@...e.cz> wrote:
>
> On Thu, 25 Feb 2010, Bruno Prémont wrote:
>
> > For the two sysfs attributes I currently use, the 'reset' one shall
> > probably be moved to debugfs (I would like to place it under
> > /sys/kernel/debug/hid/$device/ next to rdesc and event).
>
> Yes, that would make sense.
So I will move it.
> ( ... which reminds me to finally to the Documentation/ABI part in
> sync with respect to current HID code again ... )
>
> > By the way, I'm wondering why event does not list any of the
> > reports coming from my device though as I understand the code it
> > should be doing that before my raw_event function gets called...
>
> Sorry, what 'event' do you mean in 'event does not list any of the
> reports'?
Sorry, one 's' that got eaten between my brain and mail client. I
mean events file in debugfs.
For USB HID keyboard each key press generates "report dump" under
/sys/kernel/debug/hid/$device/events but for my PicoLCD I don't get
any entry in there. I'm wondering why.
Thanks,
Bruno
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists