From: David Herrmann <dh.herrmann@googlemail.com>
To: linux-input@vger.kernel.org
Cc: jkosina@suse.cz, padovan@profusion.mobi, dh.herrmann@googlemail.com
Subject: [RFC 02/12] HID: wiimote: Register wiimote hid driver stub
Date: Wed, 15 Jun 2011 01:45:47 +0200 [thread overview]
Message-ID: <1308095157-4699-3-git-send-email-dh.herrmann@googlemail.com> (raw)
In-Reply-To: <1308095157-4699-1-git-send-email-dh.herrmann@googlemail.com>
The wiimote uses a fake HID protocol. Hence, we need to prevent
HIDINPUT and HIDDEV from parsing wiimote data and instead parse
raw hid events.
Add VID/PID to hid-core so the special driver is loaded on new
wiimotes.
Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
---
drivers/hid/hid-core.c | 1 +
drivers/hid/hid-ids.h | 3 ++
drivers/hid/hid-wiimote.c | 62 ++++++++++++++++++++++++++++++++++++++++++++-
3 files changed, 65 insertions(+), 1 deletions(-)
diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
index c957c4b..4482556 100644
--- a/drivers/hid/hid-core.c
+++ b/drivers/hid/hid-core.c
@@ -1502,6 +1502,7 @@ static const struct hid_device_id hid_have_special_driver[] = {
{ HID_USB_DEVICE(USB_VENDOR_ID_ZYDACRON, USB_DEVICE_ID_ZYDACRON_REMOTE_CONTROL) },
{ HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_MICROSOFT, USB_DEVICE_ID_MS_PRESENTER_8K_BT) },
+ { HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_NINTENDO, USB_DEVICE_ID_NINTENDO_WIIMOTE) },
{ }
};
diff --git a/drivers/hid/hid-ids.h b/drivers/hid/hid-ids.h
index 0b374a6..480ce6e 100644
--- a/drivers/hid/hid-ids.h
+++ b/drivers/hid/hid-ids.h
@@ -491,6 +491,9 @@
#define USB_VENDOR_ID_NEXTWINDOW 0x1926
#define USB_DEVICE_ID_NEXTWINDOW_TOUCHSCREEN 0x0003
+#define USB_VENDOR_ID_NINTENDO 0x057e
+#define USB_DEVICE_ID_NINTENDO_WIIMOTE 0x0306
+
#define USB_VENDOR_ID_NTRIG 0x1b96
#define USB_DEVICE_ID_NTRIG_TOUCH_SCREEN 0x0001
#define USB_DEVICE_ID_NTRIG_TOUCH_SCREEN_1 0x0003
diff --git a/drivers/hid/hid-wiimote.c b/drivers/hid/hid-wiimote.c
index 8a770e6..ed4fe18 100644
--- a/drivers/hid/hid-wiimote.c
+++ b/drivers/hid/hid-wiimote.c
@@ -10,18 +10,78 @@
* any later version.
*/
+#include <linux/hid.h>
#include <linux/module.h>
+#include "hid-ids.h"
#define WIIMOTE_VERSION "0.1"
#define WIIMOTE_NAME "Nintendo Wii Remote"
-static int __init wiimote_init(void)
+static int wiimote_hid_event(struct hid_device *hdev, struct hid_report *report,
+ u8 *raw_data, int size)
+{
+ if (size < 1)
+ return -EINVAL;
+
+ return 0;
+}
+
+static int wiimote_hid_probe(struct hid_device *hdev,
+ const struct hid_device_id *id)
{
+ int ret;
+
+ ret = hid_parse(hdev);
+ if (ret) {
+ hid_err(hdev, "HID parse failed\n");
+ return ret;
+ }
+
+ ret = hid_hw_start(hdev, HID_CONNECT_HIDRAW);
+ if (ret) {
+ hid_err(hdev, "HW start failed\n");
+ return ret;
+ }
+
+ hid_info(hdev, "New device registered\n");
return 0;
}
+static void wiimote_hid_remove(struct hid_device *hdev)
+{
+ hid_info(hdev, "Device removed\n");
+ hid_hw_stop(hdev);
+}
+
+static const struct hid_device_id wiimote_hid_devices[] = {
+ { HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_NINTENDO,
+ USB_DEVICE_ID_NINTENDO_WIIMOTE) },
+ { }
+};
+MODULE_DEVICE_TABLE(hid, wiimote_hid_devices);
+
+static struct hid_driver wiimote_hid_driver = {
+ .name = "wiimote",
+ .id_table = wiimote_hid_devices,
+ .probe = wiimote_hid_probe,
+ .remove = wiimote_hid_remove,
+ .raw_event = wiimote_hid_event,
+};
+
+static int __init wiimote_init(void)
+{
+ int ret;
+
+ ret = hid_register_driver(&wiimote_hid_driver);
+ if (ret)
+ pr_err("Can't register wiimote hid driver\n");
+
+ return ret;
+}
+
static void __exit wiimote_exit(void)
{
+ hid_unregister_driver(&wiimote_hid_driver);
}
module_init(wiimote_init);
--
1.7.5.2
next prev parent reply other threads:[~2011-06-14 23:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 23:45 [RFC 00/12] Nintendo Wii Remote Device Driver David Herrmann
2011-06-14 23:45 ` [RFC 01/12] HID: wiimote: Add Nintendo Wii Remote driver stub David Herrmann
2011-06-14 23:45 ` David Herrmann [this message]
2011-06-14 23:45 ` [RFC 03/12] HID: wiimote: Add wiimote device structure David Herrmann
2011-06-15 6:20 ` Oliver Neukum
2011-06-14 23:45 ` [RFC 04/12] HID: wiimote: Register input device in wiimote hid driver David Herrmann
2011-06-14 23:45 ` [RFC 05/12] HID: wiimote: Synchronize wiimote input and hid event handling David Herrmann
2011-06-15 6:34 ` Oliver Neukum
2011-06-16 9:20 ` Jiri Kosina
2011-06-16 10:18 ` Oliver Neukum
2011-06-16 10:29 ` David Herrmann
2011-06-16 10:42 ` Oliver Neukum
2011-06-14 23:45 ` [RFC 06/12] HID: wiimote: Add wiimote send function David Herrmann
2011-06-14 23:45 ` [RFC 07/12] HID: wiimote: Add output queue for wiimote driver David Herrmann
2011-06-15 6:37 ` Oliver Neukum
2011-06-14 23:45 ` [RFC 08/12] HID: wiimote: Add wiimote event handler David Herrmann
2011-06-14 23:45 ` [RFC 09/12] HID: wiimote: Add wiimote input button parser David Herrmann
2011-06-14 23:45 ` [RFC 10/12] HID: wiimote: Add wiimote led request David Herrmann
2011-06-14 23:45 ` [RFC 11/12] HID: wiimote: Cache wiimote led state David Herrmann
2011-06-15 6:40 ` Oliver Neukum
2011-06-14 23:45 ` [RFC 12/12] HID: wiimote: Add sysfs support to wiimote driver David Herrmann
2011-06-16 18:35 ` Jiri Kosina
2011-06-17 14:58 ` David Herrmann
2011-06-16 18:36 ` [RFC 00/12] Nintendo Wii Remote Device Driver 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=1308095157-4699-3-git-send-email-dh.herrmann@googlemail.com \
--to=dh.herrmann@googlemail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=padovan@profusion.mobi \
/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).