diff options
| author | Petri Gynther <pgynther@google.com> | 2014-05-08 15:50:01 -0700 |
|---|---|---|
| committer | Marcel Holtmann <marcel@holtmann.org> | 2014-05-08 16:12:57 -0700 |
| commit | 10d4c6736ea6e6ff293dd588551270bca00ca45d (patch) | |
| tree | c2689d3f8918ad863653eb183a6bd5fb2a3d159c /net/bluetooth | |
| parent | 5ae76a94150c86a6e0ee84eb74e7f7e1909b8d39 (diff) | |
| download | linux-stable-10d4c6736ea6e6ff293dd588551270bca00ca45d.tar.gz linux-stable-10d4c6736ea6e6ff293dd588551270bca00ca45d.tar.bz2 linux-stable-10d4c6736ea6e6ff293dd588551270bca00ca45d.zip | |
Bluetooth: btusb: Add Broadcom patch RAM support
After hardware reset, some BCM Bluetooth adapters obtain their initial firmware
from OTPROM chip. Once this initial firmware is running, the firmware can be
further upgraded over HCI interface with .hcd files provided by Broadcom. This
is also known as "patch RAM" support. This change implements that.
If the .hcd file is not found in /lib/firmware, BCM Bluetooth adapter continues
to operate with the initial firmware. Sample kernel log:
hotplug: sys=firmware act=add fw=brcm/BCM20702A0-0a5c-22be.hcd dev=...
Bluetooth: hci0: BCM: patch brcm/BCM20702A0-0a5c-22be.hcd not found
If the .hcd file is found, btusb driver pushes it to the BCM Bluetooth adapter and
it starts using the new firmware. Sample kernel log:
hotplug: sys=firmware act=add fw=brcm/BCM20702A0-0a5c-22be.hcd dev=...
Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1000 lmp_ver=06 lmp_subver=220e
Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1389 lmp_ver=06 lmp_subver=220e
Above, we can see that hci_rev goes from 1000 to 1389 as a result of the upgrade.
Signed-off-by: Petri Gynther <pgynther@google.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Diffstat (limited to 'net/bluetooth')
0 files changed, 0 insertions, 0 deletions