From: Lamarque Vieira Souza <lamarque@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] Fix for Acer Bluetooth Optical Rechargeable Mouse
Date: Fri, 17 Jul 2009 03:01:43 -0300 [thread overview]
Message-ID: <200907170301.43807.lamarque@gmail.com> (raw)
This patch works around one problem with my Acer Bluetooth Optical
Rechargeable Mouse where the cursor gets stuck at screen's upper-left corner.
Even my notebook's touchpad is not able to move cursor when the bluetooth
mouse is connected to my Acer Ferrari 4005 notebook. Using input session
instead of hid session solves this problem although the cursor still moves a
little sluggishly with the bluetooth mouse, cursor moves correctly using the
touchpad. My bluetooth mouse used to work well (no sluggish) until kernel
2.6.21, since then the problems are getting worse with each kernel release (it
got sluggish in 2.6.22 and this this upper-left corner problem appeared in
2.6.28 or 2.6.27).
Signed-off-by: Lamarque V. Souza <lamarque@gmail.com>
---
diff -Nru --show-c-function linux-2.6.30.1-orig/net/bluetooth/hidp/core.c
linux-2.6.30.1-lvs/net/bluetooth/hidp/core.c
--- linux-2.6.30.1-orig/net/bluetooth/hidp/core.c 2009-07-16
23:53:04.697925121 -0300
+++ linux-2.6.30.1-lvs/net/bluetooth/hidp/core.c 2009-07-17 02:35:03.969927384
-0300
@@ -73,6 +73,43 @@ static unsigned char hidp_keycode[256] =
static unsigned char hidp_mkeyspat[] = { 0x01, 0x01, 0x01, 0x01, 0x01, 0x01
};
+/* HIDP device quirks */
+enum {
+ HIDP_QUIRK_USE_INPUT_SESSION
+};
+
+struct quirk_id {
+ __u16 vendor;
+ __u16 product;
+ unsigned long quirks;
+};
+
+static const struct quirk_id hidp_quirks[] = {
+ {
+ /* Lamarque: Acer Bluetooth Optical Rechargeable Mouse
+ * does not work properly with hid session since 2.6.27. */
+ .vendor = 0x0458,
+ .product = 0x0058,
+ .quirks = 1 << HIDP_QUIRK_USE_INPUT_SESSION
+ },
+
+ { /* end: all zeroes */ }
+};
+
+static int quirk_test_bit(__u16 vendor, __u16 product, int quirk)
+{
+ const struct quirk_id *q = &hidp_quirks[0];
+
+ while (q->vendor != vendor && q->product != product &&
+ q->vendor && q->product)
+ q++;
+
+ if (q->vendor == vendor && q->product == product)
+ return test_bit(quirk, &q->quirks);
+
+ return 0;
+}
+
static struct hidp_session *__hidp_get_session(bdaddr_t *bdaddr)
{
struct hidp_session *session;
@@ -832,7 +869,9 @@ int hidp_add_connection(struct hidp_conn
session->flags = req->flags & (1 << HIDP_BLUETOOTH_VENDOR_ID);
session->idle_to = req->idle_to;
- if (req->rd_size > 0) {
+ if (req->rd_size > 0 &&
+ !quirk_test_bit(req->vendor, req->product,
+ HIDP_QUIRK_USE_INPUT_SESSION)) {
err = hidp_setup_hid(session, req);
if (err && err != -ENODEV)
goto err_skb;
next reply other threads:[~2009-07-17 6:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 6:01 Lamarque Vieira Souza [this message]
2009-07-23 20:28 ` [PATCH] Fix for Acer Bluetooth Optical Rechargeable Mouse Andrew Morton
2009-07-23 21:30 ` Lamarque Vieira Souza
2009-07-23 21:43 ` Andrew Morton
2009-07-23 22:00 ` Lamarque Vieira Souza
2009-07-23 22:06 ` Andrew Morton
2009-07-23 22:21 ` Lamarque Vieira Souza
2009-07-23 23:05 ` Anthony Waters
2009-07-23 23:59 ` Lamarque Vieira Souza
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=200907170301.43807.lamarque@gmail.com \
--to=lamarque@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-bluetooth@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox