stikonas has quit [Remote host closed the connection]
vstehle has quit [Ping timeout: 246 seconds]
kever has joined #linux-rockchip
ganbold has quit [Quit: Leaving]
JohnDoe_71Rus has joined #linux-rockchip
vagrantc has quit [Quit: leaving]
vstehle has joined #linux-rockchip
tomeu has joined #linux-rockchip
xming has joined #linux-rockchip
<xming>
hi is ap6335 supported on firefly rk3288 with mainline kernel? With 5.1.0 I don't see ant reference in the firefly's dtsi
ldevulder_ is now known as ldevulder
yann has quit [Read error: No route to host]
warpme_ has joined #linux-rockchip
<mmind00>
xming: sdio devices normally get probed automatically and the dt _can_ provide additional info but doesn't have to ... so essetially, as long as the &sdio-node is enabled it should already find the wifi module, if the driver itself is actually built
stikonas has joined #linux-rockchip
wwilly has joined #linux-rockchip
<xming>
mmind00: is this the correct driver? CONFIG_B43 if so multi_v7_defconfig doesn't enble it by default
stikonas has quit [Remote host closed the connection]
warpme_ has quit [Quit: warpme_]
<mmind00>
xming: I don't know ... never really needed the wifi on my test-boards ... but you should be able to compare sdio device-ids ... the mmc subsystem should print these when it finds a mmc device (or in /sys) ... and compare that with the device-ids in the driver
BenG83 has joined #linux-rockchip
return0e has joined #linux-rockchip
<xming>
mmind00: sorry I am a bit lost here
<xming>
ther are not entries under /sys/bus/sdio/devices
<xming>
and isn't mmc for the internal flash/sd
<xming>
also I can't find anyting realated to wifi in dmesg
<mmind00>
xming: let me check ... in any case, according to https://wikidevi.com/wiki/AMPAK, the AP6335 is in fact based on the BCM4339, so that driver could be the right one
<mmind00>
xming: checking rk3288-firefly.dtsi I see that sdio0 gets enabled ... so at least it should detect the card ... the flow is: mmc-host gets probed, host detects sdio-card (grep for mmc in dmesg), host checks sdio-id and binds to a matching driver (this b43 maybe)
return0e has quit [Remote host closed the connection]
wwilly has quit [Ping timeout: 268 seconds]
<mmind00>
xming: yep ... and even hotplug-capable ;-)
<xming>
ok going to compile b43 and see if it helps
<mmind00>
xming: hmm, you can see that mmc1 there is the host that should have the wifi card (non-removable and the others have mmc + sd card)
<mmind00>
xming: as for sys ... try somewhere under the host controller itself (bus/mmc or so)... I think the bus/sdio/devices might only get filled after it bound to the driver
* xming
needs something like lspci
<xming>
only mmc0:1234 mmc2:0001 under :/sys/bus/mmc/devices/
<xming>
mmc0 is the uSD and mmc2 is the internal flash
<xming>
oh it needs a fw
return0e has joined #linux-rockchip
field^Mop has joined #linux-rockchip
warpme_ has joined #linux-rockchip
<xming>
still no dice
BenG83 has quit [Remote host closed the connection]
nsaenz has quit [Remote host closed the connection]
kever has quit [Ping timeout: 248 seconds]
nsaenz has joined #linux-rockchip
ldevulder has quit [Ping timeout: 246 seconds]
<xming>
mmind00: nvram_AP6335.txt isn't a blob, do I need a fw_bcm43xxx.bin
ldevulder has joined #linux-rockchip
warpme_ has quit [Quit: warpme_]
BenG83 has quit [Quit: Leaving]
inode has quit [Ping timeout: 258 seconds]
JohnDoe_71Rus has quit [Ping timeout: 252 seconds]
<xming>
I really don't see any attempt to load any fw
<xming>
tried b43, b43legacy and brcmfmac
<xming>
modinfo says that brcmfmac looks for brcm/brcmfmac?????-sdio.bin and not nvram_AP6335.txt
mrjay has joined #linux-rockchip
<mrjay>
xming: you need both firmware binary and txt
<mrjay>
xming: what linux do you use? debian, archlinux other?
<xming>
alpine
<mrjay>
xming: try to install firmware package of your distribution
<xming>
I did
<mrjay>
i.e. in debian it is named linux-firmware
<xming>
I have bunch of files in /lib/firmware/brcm/bcm*
<xming>
AFAIK, if the hw is present and fw is missing, it will be printed in dmesg
<xming>
and it did that for regulatory.db
<mrjay>
could you paste output of the "dmesg -k | grep -i brcmfmac"
<xming>
it's empty
<xming>
FWIW it's a self compiled kernel (mainline 5.1) with multi_v7_defconfig
<mrjay>
without any changes? you need to enable CONFIG_BRCMFMAC=m CONFIG_BRCMFMAC_PROTO_BCDC=y CONFIG_BRCMFMAC_SDIO=y and not enable: CONFIG_BRCMFMAC_USB is not set # CONFIG_BRCMFMAC_PCIE is not set
<mani_s>
mmind00, have you tested i2c2 on rk3399 w/ mainline?
<mani_s>
it is not working on couple of our boards but with the vendor kernel it works fine
<mmind00>
mani_s: on rk3399-scarlet the digitzer-pen is connected to i2c2 and that worked in a test just now
<mmind00>
mani_s: I guess double check pinctrl settings or take a look at the i2c-scl-*-time-ns properties in rk3399-gru-scarlet.dtsi to see if something helps
<mani_s>
mmind00, okay, thanks for testing!
<mani_s>
sure, will check it out!
mrjay has joined #linux-rockchip
kever has joined #linux-rockchip
<mrjay>
xming: to make wifi work you need to add some things to dts: