stikonas has quit [Remote host closed the connection]
libv has quit [Ping timeout: 240 seconds]
adj__ has joined #linux-rockchip
adj_ has quit [Ping timeout: 248 seconds]
ddddddddd[m] has joined #linux-rockchip
icenowy[m] has joined #linux-rockchip
sphalerit has joined #linux-rockchip
mbakke has joined #linux-rockchip
adj__ has quit [Read error: Connection reset by peer]
adj_ has joined #linux-rockchip
adj__ has joined #linux-rockchip
adj_ has quit [Ping timeout: 255 seconds]
anarsoul|2 has quit [Quit: Leaving]
nighty- has joined #linux-rockchip
hgs has joined #linux-rockchip
<hgs>
hi guys,
<hgs>
i am having issues bringing up bluetooth interface on rk3399, following are the bluetooth dmesg logs https://pastebin.com/UvKP02kK
<hgs>
rfkill lists only root@rapsodo:~# rfkill list
<hgs>
0: bt_default: Bluetooth
<hgs>
Hard blocked: no
<hgs>
Soft blocked: no
kaspter has joined #linux-rockchip
nots has quit [Quit: Page closed]
<stdint>
clk_get failed
<stdint>
hgs, it is obvious that you miss the clock node, it is usually comes from the pmic
return0e has quit [Remote host closed the connection]
return0e has joined #linux-rockchip
anarsoul has quit [Remote host closed the connection]
lurchi_ has joined #linux-rockchip
lurchi__ has quit [Ping timeout: 276 seconds]
<hgs>
stdint: so is it related to kernel configs or debian os related
<hgs>
stdint: i am using ap6356 module which supports both wifi and bluetooth. wifi module is working but the bluetooth is not working. is it related to some kernel configs like enabling hci_uart etc or some broadcom bluetooth fimrware missing on the debian rootfs
<hgs>
stdint: atleast tat was what i was thinking, but now you had mentioned it is related to pmic..any reference on bringing up bluetooth support?
anarsoul has joined #linux-rockchip
<beeble>
hgs: you usually need a 32khz clock for bluetooth. the rk808 is capable of generating it on it's clk32out[1|2] pins
<beeble>
hgs: the LPO pin on your ampak module
<hgs>
beeble: in the hardware LPO is connected to RTC CLK0 WIFI
<hgs>
beeble: so some configuration in kernel?
<beeble>
hgs: devicetree. check your rk808 node if there are clock output defined and if your bluetooth node has a clock node register the rk808 clock
<beeble>
and be sure that your module is not in reset (BT_REG_ON)
<hgs>
beeble: thanks for the info
gnufan has quit [Quit: Leaving.]
<beeble>
hgs: you can look at other rk3399 boards, most of them do it similar. just be sure to select the correct clock output as the rk808 has two outputs
Omegamoon has joined #linux-rockchip
xerpi has joined #linux-rockchip
indy has quit [Read error: Connection reset by peer]