From: David Herrmann <dh.herrmann@googlemail.com>
To: Joao Paulo Rechi Vita <jprvita@openbossa.org>
Cc: linux-input@vger.kernel.org, jkosina@suse.cz,
marcel@holtmann.org, claudio.takahasi@openbossa.org,
linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 0/1] HID: User-space HID I/O driver (UHID)
Date: Thu, 3 May 2012 17:33:37 +0200 [thread overview]
Message-ID: <CANq1E4QaRHtGxt3d=Z2mvqAFhTY2zid20GGNZ2ZzHjStGepc+A@mail.gmail.com> (raw)
In-Reply-To: <CAAngNMabAxO9fVN2DM=5xPJAVk_is3QoS1=+TGZPJAbY3TYHMQ@mail.gmail.com>
Hi Joao
On Wed, May 2, 2012 at 9:09 PM, Joao Paulo Rechi Vita
<jprvita@openbossa.org> wrote:
> On Mon, Apr 30, 2012 at 12:27 PM, David Herrmann
> <dh.herrmann@googlemail.com> wrote:
>> Hi
>>
>> This implements a hid_ll_driver user-space interface similar to uinput f=
or the
>> input devices. It allows to implement the HID transport-layer in user-sp=
ace as
>> required by Bluetooth Low-Energy (HoG).
>>
>> This is my "first final revision" for the module. Please review and test=
.
>> Changes from the previous RFCs include:
>> =A0- The feature-report mechanism is now implemented
>> =A0- Several min_t() fixes
>> =A0- Minor coding-style issues
>>
>> I did not change __attribute__((__packed__)) to __packed as the latter o=
ne is
>> not provided to user-space.
>>
>> If there are any more issues, please tell me. And for the record, the Ho=
G devs
>> told me that they are working since several months with it now so we hav=
e a real
>> user-space application that needs it ;)
>>
>> If there are no more issues (which i doubt) I can also resend this split=
ted into
>> multiple patches.
>>
>
> Thanks for your work, David. I'll test and review this new version.
> Did you find out the what is the problem when passing BUS_BLUETOOTH on
> the 'bus' field of the create request?
I've spent some time looking into that but I haven't found the
problem, yet. Maybe Jiri can comment here.
> Also, how does the HID subsystem differentiate from HID protocol
> versions? We've just found out that HoG exposes what HID protocol
> version the device implements, is it the case of having an extra field
> on the uhid_create_req structure to pass this information, or is it
> already present on the HID descriptor (sorry for my limited knowledge
> on the HID protocol itself)?
There is already a "version" field in UHID_CREATE. It isn't mandatory,
though, so setting it to 0 works. I even think the HID core doesn't
even look into that value except for printk messages.
> --
> Jo=E3o Paulo Rechi Vita
> Openbossa Labs - INdT
Thanks
David
next prev parent reply other threads:[~2012-05-03 15:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 15:27 [PATCH 0/1] HID: User-space HID I/O driver (UHID) David Herrmann
2012-04-30 15:27 ` [PATCH 1/1] HID: User-space I/O driver support for HID subsystem David Herrmann
2012-05-02 19:09 ` [PATCH 0/1] HID: User-space HID I/O driver (UHID) Joao Paulo Rechi Vita
2012-05-03 15:33 ` David Herrmann [this message]
2012-05-05 15:50 ` David Herrmann
2012-05-10 10:19 ` Jiri Kosina
2012-05-20 10:40 ` David Herrmann
2012-05-23 13:55 ` 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='CANq1E4QaRHtGxt3d=Z2mvqAFhTY2zid20GGNZ2ZzHjStGepc+A@mail.gmail.com' \
--to=dh.herrmann@googlemail.com \
--cc=claudio.takahasi@openbossa.org \
--cc=jkosina@suse.cz \
--cc=jprvita@openbossa.org \
--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).