diff options
| author | Thomas Petazzoni | 2012-12-21 15:49:19 +0100 |
|---|---|---|
| committer | Arnd Bergmann | 2013-02-28 18:57:05 +0100 |
| commit | c9b7a72d988d3474f3127cd39084d18bcc2df3df (patch) | |
| tree | 676c9185fb4415a4ba52a3e1fa995b53db1c42dc /kernel/mutex-debug.h | |
| parent | 0c8cb1d4ae7d1a96be6a0bef18e7f44d88a18fdf (diff) | |
arm: mvebu: enable btmrvl driver in mvebu_defconfig
The Globalscale Mirabox platform, based on the Armada 370 from
Marvell, has a SD8787 Wireless/Bluetooth chip connected on the SDIO
interface. Now that the mvsdio has a Device Tree binding, and the
necessary Device Tree informations have been added at the SoC and
board level, let's enable the btmrvl driver for the Bluetooth part of
the SD8787 chip.
For now, the driver gets probed correctly, detects the device but
apparently fails to push the firmware to the device:
Bluetooth: vendor=0x2df, device=0x911a, class=255, fn=2
Bluetooth: FW failed to be active in time!
Bluetooth: Downloading firmware failed!
Bluetooth: vendor=0x2df, device=0x911b, class=255, fn=3
Bluetooth: FW failed to be active in time!
Bluetooth: Downloading firmware failed!
This will have to be investigated separately.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Jason Cooper <jason@lakedaemon.net>
Diffstat (limited to 'kernel/mutex-debug.h')
0 files changed, 0 insertions, 0 deletions