Guys, I’m bringing rk3576 sbc (nanopi-r76s) to mainline linux. All works well except 8822cs wifi (m2 key module; sdio intf) my user spacce is iwd 3.9. linux-fw is current master. 6.16-rc7 without any rtw88 related patches. 8822cs is recognised by kernel but works ok only in 1 per 10 or so boots. In other 9 non-working cases i’m getting: 1. no any networks are discovered 2. dmesg is stormed with [ 106.684159] rtw88_8822cs mmc1:0001:1: unsupported rf path (1) [ 106.684667] rtw88_8822cs mmc1:0001:1: unsupported rf path (1) [ 106.685169] rtw88_8822cs mmc1:0001:1: unsupported rf path (1) [ 106.716150] rtw88_8822cs mmc1:0001:1: unsupported rf path (1) [ 106.718596] rtw88_8822cs mmc1:0001:1: unsupported rf path (1) [ 106.721630] rtw88_8822cs mmc1:0001:1: unsupported rf path (1) [ 106.722132] rtw88_8822cs mmc1:0001:1: unsupported rf path (1) [ 106.722632] rtw88_8822cs mmc1:0001:1: unsupported rf path (1) [ 106.723132] rtw88_8822cs mmc1:0001:1: unsupported rf path (1) [ 106.723683] rtw88_8822cs mmc1:0001:1: unsupported rf path (1) [ 106.730767] rtw88_8822cs mmc1:0001:1: unsupported rf path (1) [ 109.357579] rtw88_8822cs mmc1:0001:1: unsupported rf path (1) (full dmesg: https://termbin.com/i1db ) 3. comparing debug output of iwd for working and non working states i see: non-working—————————————————: Wiphy: 0, Name: phy0 Permanent Address: 70:68:71:a2:a8:0d 2.4GHz Band: Bitrates (non-HT): 1.0 Mbps 2.0 Mbps 5.5 Mbps 11.0 Mbps 6.0 Mbps 9.0 Mbps 12.0 Mbps 18.0 Mbps 24.0 Mbps 36.0 Mbps 48.0 Mbps 54.0 Mbps HT Capabilities: HT40 Short GI for 20Mhz Short GI for 40Mhz HT RX MCS indexes: 0-7 32 5GHz Band: Bitrates (non-HT): 6.0 Mbps 9.0 Mbps 12.0 Mbps 18.0 Mbps 24.0 Mbps 36.0 Mbps 48.0 Mbps 54.0 Mbps HT Capabilities: HT40 Short GI for 20Mhz Short GI for 40Mhz HT RX MCS indexes: 0-7 32 VHT Capabilities: Short GI for 80Mhz Max RX MCS: 0-9 for NSS: 1 Max TX MCS: 0-9 for NSS: 1 Ciphers: BIP-CMAC-256 BIP-GMAC-256 BIP-GMAC-128 CCMP-256 GCMP-256 GCMP-128 BIP-CMAC-128 CCMP-128 TKIP Supported iftypes: station working--------------------------: Wiphy: 0, Name: phy0 Permanent Address: 70:68:71:a2:a8:0d 2.4GHz Band: Bitrates (non-HT): 1.0 Mbps 2.0 Mbps 5.5 Mbps 11.0 Mbps 6.0 Mbps 9.0 Mbps 12.0 Mbps 18.0 Mbps 24.0 Mbps 36.0 Mbps 48.0 Mbps 54.0 Mbps HT Capabilities: HT40 Short GI for 20Mhz Short GI for 40Mhz HT RX MCS indexes: 0-15 32 5GHz Band: Bitrates (non-HT): 6.0 Mbps 9.0 Mbps 12.0 Mbps 18.0 Mbps 24.0 Mbps 36.0 Mbps 48.0 Mbps 54.0 Mbps HT Capabilities: HT40 Short GI for 20Mhz Short GI for 40Mhz HT RX MCS indexes: 0-15 32 VHT Capabilities: Short GI for 80Mhz Max RX MCS: 0-9 for NSS: 2 Max TX MCS: 0-9 for NSS: 2 Ciphers: BIP-CMAC-256 BIP-GMAC-256 BIP-GMAC-128 CCMP-256 GCMP-256 GCMP-128 BIP-CMAC-128 CCMP-128 TKIP Supported iftypes: station As you see main diff is in HT RX MCS indexes and VHT caps. Working: HT RX MCS indexes: 0-15 Non-working: HT RX MCS indexes: 0-7 Isn’t that 8-15 are for 2x2mimo? So maybe - by some reason - hw sometimes reports support for only 1x mimo but receives from air 2x mimo (2 streams) and thats why I see hell of "unsupported rf path" errors from driver? My kernel is compiled with CONFIG_RTW88_DEBUG=y CONFIG_RTW88_DEBUGFS=y - so if there is need for any extra debug info - i’ll be more than happy to provide…. If you have any ideas how to move forward with this - i’ll be more than happy to listen.
