search

SolidRun / linux-fslc

Linux kernel source tree
Other
12 stars 27 forks source link

Bluetooth doesn't work for HummingBoard2 Solo/Dual Lite #36

Closed AAndranik closed 6 years ago

AAndranik commented 8 years ago

Gave this kind of error at bootlog:

I think something is changed in connection with microSOM compared with previous hummingboard edge, so there is need to do some changes in hummingboard2's device tree.

warped-rudi commented 8 years ago

How do you detect the bluetooth chip? ISTR, that - depending on the kernel or board - the BCM43xx will either appear under /sys/class/mmc_host/mmc1/... or /sys/class/mmc_host/mmc0/...

AAndranik commented 8 years ago

There are lot of files/folders in /sys/class/mmc_host/mmc0 and mmc1: device mmc0:aaaa power subsystem uevent device mmc1:0001 power subsystem uevent also there is mmc2 folder. I can't find BCM43.. there

warped-rudi commented 8 years ago

What does:

cat "/sys/class/mmc_host/mmc1/mmc1:0001/mmc1:0001:1/device"

say? It should show the ID of your bluetooth chip. I.e. "0x4330" for BCM4330 or "0x4329" for BCM4329 found on older uSOMs. Your OS should use this information to decide which firmware to load.

AAndranik commented 8 years ago

It returns "0x4330". There are "bcm4330.hcd", "brcmfmac4330-sdio.bin" and "brcmfmac4330-sdio.txt" files in "/lib/firmware/brcm/" directory but in bootlog I always receive the message "[warn] Not correct BT chip ... (warning)" so the OS couldn't load correct firmware for "bcm4330".

AAndranik commented 8 years ago

I found that bluetooth works on Debian Jessie (8.0) but doesn't work on Debian Wheezy (7.0).

jnettlet commented 6 years ago

Please test this against our latest 4.9 kernel. https://github.com/SolidRun/linux-fslc Currently this still requires the userspace firmware loader for the broadcom bluetooth support, however I have backported the serdev framework support into the kernel and will work on wiring that up for our older SOMs in the near future.