From: Tedd Ho-Jeong An <tedd.an@intel.com>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Cc: "An, Tedd" <tedd.an@intel.com>,
Johan Hedberg <johan.hedberg@gmail.com>,
Marcel Holtmann <marcel@holtmann.org>
Subject: [RFC v2 0/4] Add support for Intel Bluetooth bootloader device
Date: Mon, 8 Dec 2014 15:24:22 -0800 [thread overview]
Message-ID: <20141208152422.577ad818@tedd-test> (raw)
From: Tedd Ho-Jeong An <tedd.an@intel.com>
Changes in v2:
Consolidate read version function and open firmware function
Add enum for device mode indication to open the proper firmware
This set of patches adds support for Intel Bluetooth bootloader device.
Compare to previous Intel Bluetooth device, this device is quite different
in a few ways:
1. Using bootloader (RAM)
This device is RAM based so full size of Bluetooth operational firmware
image has to be downloaded to the device in order to run as Bluetooth device.
2. New firmware image file (.sfi)
This device needs a different firmware image file, which size is about 500KB
and the format is also different from previous generation of file (.bseq).
The contents in the file has to be encaptulated by Intel_Sec_Send command.
3. Use Bulk EP
Since the size of firwmare image is big, using Control EP and Interrupt EP
for downloading is not fast enough(takes about 15 seconds). So it uses
Bulk EP to send and receive the data and downloading can be done under 2
seconds.
To do that, the driver has to re-route Intel_Sec_Send command to Bulk EP
even if it is HCI command during the setup stage. For correspond event,
it also re-route the event from Bulk EP to interrupt handler.
Tedd Ho-Jeong An (4):
Bluetooth: Refactor Intel_read_version and opens firmware patch file
Bluetooth: Set the firmware file extension based on firmware type
Bluetooth: Set file extension to SFI file for bootloader mode
Bluetooth: Add support Intel Bluetooth bootloader device
drivers/bluetooth/btusb.c | 560 ++++++++++++++++++++++++++++++++++++++--------
1 file changed, 472 insertions(+), 88 deletions(-)
--
1.9.1
reply other threads:[~2014-12-08 23:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20141208152422.577ad818@tedd-test \
--to=tedd.an@intel.com \
--cc=johan.hedberg@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.