From: Yan-Hsuan Chuang <yhchuang@xxxxxxxxxxx> Sometimes WiFi/BT coexistence problems are difficult to debug. There are many factors that can influence the coex. Such the different scenarios of BT's profile, or the environment. So it is very useful to have some tools to know the current status for WiFi and BT, so that we can check if the decision made by the coex mechanism is good for the current situation. Also we can stop the coex mechanism to stop making any decisions, and send some commands through user space, to help us check that specific strategies are good for the current situation. There's several thread talking about adding a btcoex subsystem in the stack [1][2], but seems hard to implement. So currently rtw88 can only add its own debugfs to debug for btcoex. The information is really important for developers to analyze on the WiFi-BT misbehavior. [1] https://patchwork.kernel.org/patch/10252135/ [2] https://www.spinics.net/lists/linux-wireless/msg133333.html v1 -> v2 * don't ignore "ignore wlan command" v2 -> v3 * Use scnprintf() instead of snprintf() * Use kstrtobool() instread of sscanf() Yan-Hsuan Chuang (2): rtw88: add a debugfs entry to dump coex's info rtw88: add a debugfs entry to enable/disable coex mechanism drivers/net/wireless/realtek/rtw88/coex.c | 492 ++++++++++++++++++ drivers/net/wireless/realtek/rtw88/coex.h | 10 + drivers/net/wireless/realtek/rtw88/debug.c | 62 +++ drivers/net/wireless/realtek/rtw88/main.h | 18 + drivers/net/wireless/realtek/rtw88/rtw8822b.c | 30 ++ drivers/net/wireless/realtek/rtw88/rtw8822c.c | 28 + 6 files changed, 640 insertions(+) -- 2.17.1
