From: Joao Paulo Rechi Vita <jprvita@openbossa.org>
To: David Herrmann <dh.herrmann@googlemail.com>
Cc: Claudio Takahasi <claudio.takahasi@openbossa.org>,
Jiri Kosina <jkosina@suse.cz>,
linux-input@vger.kernel.org, chen.ganir@ti.com,
linux-bluetooth@vger.kernel.org, anderson.lizardo@openbossa.org,
marcel@holtmann.org
Subject: Re: [RFC v2 0/1] User-space HID I/O Driver
Date: Thu, 26 Apr 2012 15:19:20 -0300 [thread overview]
Message-ID: <CAAngNMbj3tzeDFvbm7KmHHR6vOYc02gq1d5aqeisgSD+N6HixA@mail.gmail.com> (raw)
In-Reply-To: <CANq1E4SZQCjNstK2Fbwce5TxzYkRv=avDbyP7AthvABno76+bA@mail.gmail.com>
On Thu, Apr 26, 2012 at 2:54 PM, David Herrmann
<dh.herrmann@googlemail.com> wrote:
> Hi Claudio
>
> On Thu, Apr 26, 2012 at 7:22 PM, Claudio Takahasi
> <claudio.takahasi@openbossa.org> wrote:
>> Hi David/Jiri,
> [snip]
>>
>> The basic features are now working, we have tested HoG keyboard and
>> mouse. The major features missing related to HID are output/feature
>> reports, and suspend.
>
> Output reports should be working. Only thing missing is feature input
> reports. They are not implemented yet. However, what driver (except
> hidraw and picolcd) uses them?
>
>> My HID knowledge is quite limited but it seems that output reports are
>> not working on uhid, at least I didn't see events from the host. Even
>> for USB keyboard it doesn't work, do you have any pointers?
>
> Do you actually handle the UHID_OUTPUT and UHID_OUTPUT_EV events from
> UHID? I have looked at the HoG code recently and haven't seen any code
> that correctly parses UHID_OUTPUT_EV packets? These packets contain
> LED (capslock, numlock etc.) updates so the keyboard can actually set
> them. They also contain BELL/SOUND codes for such devices. Only other
> non-standard stuff is sent through UHID_OUTPUT reports. If there are
> problems with it, I can help implementing this.
>
We're handling these events, but this code has not been sent to the
mailing list yet. We're going to re-send the same patchset as before,
with comments fixed, and send a RFC for the output reports handling
afterwards.
> Regarding UHID, I will send an updated version this weekend which
> mainly improves the internal buffer handling. The API will stay the
> same, however, I might implement the feature input reports, then
> everything should be ready for merging upstream (if the review cycles
> go well ;)).
>
Good to hear that! We've been using it on a daily basis to work on the
HoG implementation and haven't noticed any major issue.
--=20
Jo=C3=A3o Paulo Rechi Vita
Openbossa Labs - INdT
next prev parent reply other threads:[~2012-04-26 18:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 20:20 [RFC v2 0/1] User-space HID I/O Driver David Herrmann
2012-03-26 20:20 ` [RFC v2 1/1] HID: User-space I/O driver support for HID subsystem David Herrmann
2012-03-27 19:13 ` Marcel Holtmann
2012-03-27 21:51 ` David Herrmann
2012-03-27 22:22 ` Marcel Holtmann
2012-03-28 11:15 ` Nicolas Pouillon
2012-03-29 12:28 ` David Herrmann
2012-03-27 18:43 ` [RFC v2 0/1] User-space HID I/O Driver Joao Paulo Rechi Vita
2012-04-03 17:55 ` Joao Paulo Rechi Vita
2012-04-03 22:14 ` Jiri Kosina
2012-04-04 22:59 ` Joao Paulo Rechi Vita
2012-04-26 17:22 ` Claudio Takahasi
2012-04-26 17:54 ` David Herrmann
2012-04-26 18:19 ` Joao Paulo Rechi Vita [this message]
2012-03-28 10:50 ` 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=CAAngNMbj3tzeDFvbm7KmHHR6vOYc02gq1d5aqeisgSD+N6HixA@mail.gmail.com \
--to=jprvita@openbossa.org \
--cc=anderson.lizardo@openbossa.org \
--cc=chen.ganir@ti.com \
--cc=claudio.takahasi@openbossa.org \
--cc=dh.herrmann@googlemail.com \
--cc=jkosina@suse.cz \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=marcel@holtmann.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).