From: Tedd Ho-Jeong An <tedd.an@intel.com>
To: linux-bluetooth <linux-bluetooth@vger.kernel.org>
Cc: marcel <marcel@holtmann.org>, albert.o.ho@intel.com
Subject: [RFC 0/3] Support for Intel BT USB driver
Date: Mon, 10 Sep 2012 15:34:51 -0700 [thread overview]
Message-ID: <1860916.qXTngGPbFd@tedd-ubuntu> (raw)
From: Tedd Ho-Jeong An <tedd.an@intel.com>
These set of patches adds Intel BT USB support. The patch adds an extension
to execute of vendor specific initialization at early stage (before normal
BT controller initialization & after the USB is initialized).
- During the USB probe time, if the VID/PID are matched, it executes a
vendor specific initialization routine and uses a vendor specific HCI
event handler. When completed, the existing HCI event handler is restored.
- When vendor specific initialization completes, normal BT controller
initialization continues.
The rest of patches are Intel specific implementation.
Tedd Ho-Jeong An (3):
Bluetooth: Add initial skeleton for Intel BT USB support
Bluetooth: Implement Intel specific device initialization
Bluetooth: Add timeout for Intel specific device initialization
drivers/bluetooth/Makefile | 2 +-
drivers/bluetooth/btusb.c | 29 +++
drivers/bluetooth/btusb.h | 31 +++
drivers/bluetooth/btusb_intel.c | 420 ++++++++++++++++++++++++++++++++++++++
include/net/bluetooth/hci_core.h | 6 +
net/bluetooth/hci_core.c | 16 ++
6 files changed, 503 insertions(+), 1 deletion(-)
create mode 100644 drivers/bluetooth/btusb.h
create mode 100644 drivers/bluetooth/btusb_intel.c
--
1.7.9.5
next reply other threads:[~2012-09-10 22:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 22:34 Tedd Ho-Jeong An [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-09-10 21:29 [RFC 0/3] Support for Intel BT USB driver Tedd Ho-Jeong An
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=1860916.qXTngGPbFd@tedd-ubuntu \
--to=tedd.an@intel.com \
--cc=albert.o.ho@intel.com \
--cc=linux-bluetooth@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).