Skip to content

RFC Add support for Intel Bluetooth bootloader device

Tedd Ho-Jeong An linux-bluetooth 2 versions – In review

Get series with b4
b4 am 20141208152422.577ad818@tedd-test

Versions newest first · linked by author and title

  1. v2 RFC Latest4 patches 12 repliesIn review
  2. v1 RFC3 patches 1 replySuperseded

Changes in v2 from the cover letter

Consolidate read version function and open firmware function Add enum for device mode indication to open the proper firmware

Patches in v2 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/4Bluetooth: Refactor Intel_read_version and opens firmware patch filedrivers/bluetooth/btusb.c+96 -952 replies
2/4Bluetooth: Set the firmware file extension based on firmware typedrivers/bluetooth/btusb.c+29 -142 replies
3/4Bluetooth: Set file extension to SFI file for bootloader modedrivers/bluetooth/btusb.c+12 -05 replies
4/4Bluetooth: Add support Intel Bluetooth bootloader devicedrivers/bluetooth/btusb.c+356 -03 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.

Read the v2 thread

Cover letter [RFC v2 0/4] Add support for Intel Bluetooth bootloader device

From: Tedd Ho-Jeong An <[email protected]>

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(-)
Signature · 1 line
1.9.1