From: David Herrmann <dh.herrmann@gmail.com>
To: Daniel Nicoletti <dantti12@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
Marcel Holtmann <marcel@holtmann.org>,
Gustavo Padovan <gustavo@padovan.org>,
"open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
Jiri Kosina <jkosina@suse.cz>
Subject: Re: [PATCH] Bluetooth: hidp: register HID devices async
Date: Fri, 24 May 2013 15:53:28 +0200 [thread overview]
Message-ID: <CANq1E4RLoJQWBehsbLhgtd8hYDUDFj61eDQOPvM+Wk8i56qHxw@mail.gmail.com> (raw)
In-Reply-To: <CACo8zOc=zYVQ3dSooEjGRCD_YenczwCPepC=85pbXv0T7fxb5A@mail.gmail.com>
Hi
On Fri, May 24, 2013 at 12:46 AM, Daniel Nicoletti <dantti12@gmail.com> wrote:
> Ok, just tested with my two Apple mouses (Trackpad & MagicMouse),
> and with the ENODATA patch it now works perfectly, the other mouse
> doesn't freeze when connecting and the udev signals are also properly
> emitted, is there some formal way of adding a tested-by?
>
> tested-by: Daniel Nicoletti <dantti12@gmail.com>
Just this line is enough. Thanks!
It's weird, though, that the other patch is required. With this patch
here, hid_get_raw_report() should work just fine on bluetooth _and_
usb devices. And the fact that you no longer get a delay means that
I/O is working properly. However, the GET_REPORT request seems to fail
after device-initialization for some reason.
My guess is that we send REPORT_INIT requests in hid_start() and
Bluetooth devices seem to not work well with that. Hence, they send an
HANDSHAKE error for each report once. This seems to fall into the same
time-span where we send our first battery-request during registration
and hence HIDP-core thinks the battery-request failed.
@Jiri, @Marcel are you sure report-initialization is needed for
BT-HIDP devices? BT-HID-profile doesn't mention it, but it relies
heavily on USB-HID (which I haven't read..)..
Anyway, would be nice to see both patches applied.
Cheers
David
next prev parent reply other threads:[~2013-05-24 13:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 11:10 [PATCH] Bluetooth: hidp: register HID devices async David Herrmann
[not found] ` <1369307425-5993-1-git-send-email-dh.herrmann-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-05-23 21:20 ` Daniel Nicoletti
2013-05-23 22:46 ` Daniel Nicoletti
2013-05-24 13:53 ` David Herrmann [this message]
2013-05-28 8:45 ` Jiri Kosina
2013-05-28 15:52 ` Gustavo Padovan
2013-05-29 13:20 ` 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=CANq1E4RLoJQWBehsbLhgtd8hYDUDFj61eDQOPvM+Wk8i56qHxw@mail.gmail.com \
--to=dh.herrmann@gmail.com \
--cc=dantti12@gmail.com \
--cc=gustavo@padovan.org \
--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).