| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 18 Dec 2019 13:55:35 +0200
From: Christian Hewitt <christianshewitt@...il.com>
To: Soeren Moch <smoch@....de>
Cc: Kalle Valo <kvalo@...eaurora.org>,
Heiko Stuebner <heiko@...ech.de>,
linux-wireless@...r.kernel.org,
brcm80211-dev-list.pdl@...adcom.com,
brcm80211-dev-list@...ress.com, netdev@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org,
Neil Armstrong <narmstrong@...libre.com>
Subject: Re: [PATCH v2 0/9] brcmfmac: add support for BCM4359 SDIO chipset
> On 12 Dec 2019, at 1:52 am, Soeren Moch <smoch@....de> wrote:
>
> Add support for the BCM4359 chipset with SDIO interface and RSDB support
> to the brcmfmac wireless network driver in patches 1-7.
>
> Enhance devicetree of the RockPro64 arm64/rockchip board to use an
> AP6359SA based wifi/bt combo module with this chipset in patches 8-9.
>
>
> Chung-Hsien Hsu (1):
> brcmfmac: set F2 blocksize and watermark for 4359
>
> Soeren Moch (5):
> brcmfmac: fix rambase for 4359/9
> brcmfmac: make errors when setting roaming parameters non-fatal
> brcmfmac: add support for BCM4359 SDIO chipset
> arm64: dts: rockchip: RockPro64: enable wifi module at sdio0
> arm64: dts: rockchip: RockPro64: hook up bluetooth at uart0
>
> Wright Feng (3):
> brcmfmac: reset two D11 cores if chip has two D11 cores
> brcmfmac: add RSDB condition when setting interface combinations
> brcmfmac: not set mbss in vif if firmware does not support MBSS
Thanks for posting this series, this chip is widely used by a large number of current Amlogic devices!
Patches 1-7 have been tested on Amlogic G12B (Khadas VIM3) hardware with 5.5-rc kernel and a LibreELEC (distro) colleague also tested with a Khadas Edge board (RK3399). The Ampak 6398S module on both boards are detected and can connect to networks to pass basic functional testing.
On the VIM3 board I do see the following warning splat:
[ 7.987351] ------------[ cut here ]------------
[ 7.987382] WARNING: CPU: 5 PID: 36 at drivers/net/wireless/broadcom/brcm80211/brcmfmac/bcmsdh.c:776 brcmf_sdiod_sgtable_alloc+0x130/0x138 [brcmfmac]
[ 7.987384] Modules linked in: brcmfmac ecdh_generic brcmutil rtc_meson_vrtc videodev ecc cfg80211 gpio_pca953x rfkill ir_nec_decoder crct10dif_ce rc_khadas mali_kbase(O) meson_ir ao_cec_g12a mc rtc_hym8563 rc_core gpio_keys_polled adc_keys ipv6 nf_defrag_ipv6 crc_ccitt sch_fq_codel
[ 7.987403] CPU: 5 PID: 36 Comm: kworker/5:0 Tainted: G O 5.5.0-rc1 #1
[ 7.987404] Hardware name: Khadas VIM3 (DT)
[ 7.987417] Workqueue: events brcmf_driver_register [brcmfmac]
[ 7.987420] pstate: 80000005 (Nzcv daif -PAN -UAO)
[ 7.987432] pc : brcmf_sdiod_sgtable_alloc+0x130/0x138 [brcmfmac]
[ 7.987443] lr : brcmf_sdio_probe+0x28c/0x890 [brcmfmac]
[ 7.987444] sp : ffff80001017ba90
[ 7.987445] x29: ffff80001017ba90 x28: 0000000000000000
[ 7.987447] x27: 0000000000000000 x26: ffff0000a8c09400
[ 7.987449] x25: ffff80000a24cb08 x24: ffff0000a3800400
[ 7.987451] x23: ffff800012c618c8 x22: ffff0000a675e000
[ 7.987453] x21: ffff0000a675e000 x20: 0000000000000023
[ 7.987454] x19: ffff0000a3800000 x18: ffff800013b25908
[ 7.987456] x17: ffff800013b25d0c x16: ffff800013b25104
[ 7.987457] x15: 00000000f0000000 x14: 000000000000000a
[ 7.987459] x13: 0000000000000000 x12: 0000000000000001
[ 7.987460] x11: 0000000000000005 x10: 0101010101010101
[ 7.987461] x9 : ffffffffffffffff x8 : 7f7f7f7f7f7f7f7f
[ 7.987463] x7 : 00000000000001ff x6 : 0000000000000080
[ 7.987464] x5 : 0000000000000600 x4 : 0000000000000003
[ 7.987466] x3 : ffff0000a5a3d880 x2 : 0000000000000021
[ 7.987467] x1 : 0000000000000003 x0 : ffff0000a675e000
[ 7.987469] Call trace:
[ 7.987481] brcmf_sdiod_sgtable_alloc+0x130/0x138 [brcmfmac]
[ 7.987493] brcmf_sdio_probe+0x28c/0x890 [brcmfmac]
[ 7.987504] brcmf_sdiod_probe+0xe0/0x1c0 [brcmfmac]
[ 7.987516] brcmf_ops_sdio_probe+0x16c/0x208 [brcmfmac]
[ 7.987522] sdio_bus_probe+0xe0/0x1c8
[ 7.987526] really_probe+0xd8/0x428
[ 7.987529] driver_probe_device+0xdc/0x130
[ 7.987531] device_driver_attach+0x6c/0x78
[ 7.987533] __driver_attach+0x9c/0x168
[ 7.987535] bus_for_each_dev+0x70/0xc0
[ 7.987536] driver_attach+0x20/0x28
[ 7.987538] bus_add_driver+0x190/0x220
[ 7.987539] driver_register+0x60/0x110
[ 7.987541] sdio_register_driver+0x24/0x30
[ 7.987552] brcmf_sdio_register+0x14/0x48 [brcmfmac]
[ 7.987563] brcmf_driver_register+0xc/0x20 [brcmfmac]
[ 7.987567] process_one_work+0x1e0/0x358
[ 7.987569] worker_thread+0x40/0x488
[ 7.987571] kthread+0x118/0x120
[ 7.987573] ret_from_fork+0x10/0x18
[ 7.987575] ---[ end trace 808ac7e159d1fc33 ]---
I don’t see this on older Amlogic SoCs (GXL/GXM devices with various other BCM chips) or another Amlogic G12B device (same SoC with a different Ampak module) or some RK3399 devices, so it may be something board (Khadas VIM3) specific.
I also see some errors like:
[ 71.046597] brcmfmac: brcmf_sdio_readframes: RXHEADER FAILED: -5
[ 71.046652] brcmfmac: brcmf_sdio_rxfail: abort command, terminate frame, send NAK
[ 123.844863] brcmfmac: brcmf_sdio_bus_sleep: error while changing bus sleep state -5
[ 124.678329] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
[ 124.680226] mmc0: tuning execution failed: -5
[ 124.708843] brcmfmac: brcmf_sdio_bus_sleep: error while changing bus sleep state -5
[ 125.700765] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
[ 125.880372] brcmfmac: mmc_submit_one: CMD53 sg block read failed -22
[ 125.880393] brcmfmac: brcmf_sdio_rxglom: glom read of 512 bytes failed: -5
[ 125.880401] brcmfmac: brcmf_sdio_rxfail: abort command, terminate frame
[ 125.881262] brcmfmac: brcmf_sdio_readframes: brcmf_sdio_readframes: glom superframe w/o descriptor!
[ 125.881318] brcmfmac: brcmf_sdio_rxfail: terminate frame
[ 131.844289] brcmfmac: mmc_submit_one: CMD53 sg block write failed -22
[ 131.844302] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
[ 131.844488] brcmfmac: mmc_submit_one: CMD53 sg block write failed -22
[ 131.844494] brcmfmac: brcmf_sdio_txfail: sdio error, abort command and terminate frame
I’m not sure if that’s of any concern, but if yes, I’d be happy to apply any debugging patches you provide to generate output.
Thanks again for working on this chipset!
Christian
Powered by blists - more mailing lists