Received: by 2002:a25:e7d8:0:0:0:0:0 with SMTP id e207csp1242632ybh; Thu, 12 Mar 2020 20:31:34 -0700 (PDT) X-Google-Smtp-Source: ADFU+vuSlMz6XIepN+F+Smfo/A623wduv881wkXl7PjTsyLL67V/uRpMZvdyxcZc7494meMci89N X-Received: by 2002:a05:6808:a0a:: with SMTP id n10mr5450230oij.10.1584070294542; Thu, 12 Mar 2020 20:31:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1584070294; cv=none; d=google.com; s=arc-20160816; b=koF92gqPqZSNEBELxC+Bps2pUY1UApz3WaKF/xUcMpyYDYxsgmdMXMfosog448soZJ 6rYGs9jP69o1aksaMrv+yfYeZrOnwrbnqG8Ij0r880eqoUrS9Xl/f0f3GMLvsnWs7b1+ s/0QqqvmKJFjouSlD41cyS6ni6pvcGEhDcNgXS/fF4kNcG7E9eNPIoKiJ0Cac+WhldeL y5litzhNxefjyqgmXOVsDf5zTt2CQ45wrGE8ikz6oSSiZb9hmy3jCt7R+VD5IhP7roaO 1e4oLeCJL2YQzcjgW0Jpnt9G5XJV55e4+a/u7D1sNHTZWxYbwmJSP+gY3oQ+dSyvDuaX Jbow== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:subject:cc :to:from:authenticated-by; bh=VTtugq5a12WOYoPZT+mG55i/5Cn9xJzLfcOijnsub+I=; b=DLPVBScFbWus7Ui22EFRtdJWTjVo0VNcrfP4RDkGIeHjVDBL0gHWS0omerYNOn5JiH LRt+nvEKi7BkLpKCToJPJgYQXWA1+HtJ9W1jzezcLokuC7KiCmrehuHqT81OS+4JdsNR 2PJK6Z/G1q357fKfBVFrW1lkpZ4rPYrkKfHPP+9L+FzoN7LklkGIXuvwN3phPYOfo8eG tDYpFTYCkyll34XFwch0cZmRNbYTm3Ysd0Df472BOvxK04e8ybuWJyF9OQSVrcKX7vto i7zbKBBrMFi3POfaUUUcIYkn825fKBWQmvIjsDkDYhIGBNP3L79t5FDj315VpUFVsRgq tLCg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t71si3175656oif.84.2020.03.12.20.31.23; Thu, 12 Mar 2020 20:31:34 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726443AbgCMDac (ORCPT + 99 others); Thu, 12 Mar 2020 23:30:32 -0400 Received: from rtits2.realtek.com ([211.75.126.72]:54225 "EHLO rtits2.realtek.com.tw" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726371AbgCMDac (ORCPT ); Thu, 12 Mar 2020 23:30:32 -0400 Authenticated-By: X-SpamFilter-By: BOX Solutions SpamTrap 5.62 with qID 02D3UBiu000319, This message is accepted by code: ctloc85258 Received: from mail.realtek.com (RTEXMB06.realtek.com.tw[172.21.6.99]) by rtits2.realtek.com.tw (8.15.2/2.57/5.78) with ESMTPS id 02D3UBiu000319 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 13 Mar 2020 11:30:11 +0800 Received: from RTEXMB04.realtek.com.tw (172.21.6.97) by RTEXMB06.realtek.com.tw (172.21.6.99) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1779.2; Fri, 13 Mar 2020 11:30:11 +0800 Received: from localhost.localdomain (172.21.68.128) by RTEXMB04.realtek.com.tw (172.21.6.97) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1779.2; Fri, 13 Mar 2020 11:30:10 +0800 From: To: CC: , , , , Subject: [PATCH v3 0/2] rtw88: add coex related debugfs Date: Fri, 13 Mar 2020 11:30:05 +0800 Message-ID: <20200313033008.20070-1-yhchuang@realtek.com> X-Mailer: git-send-email 2.17.1 MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [172.21.68.128] X-ClientProxiedBy: RTEXMB03.realtek.com.tw (172.21.6.96) To RTEXMB04.realtek.com.tw (172.21.6.97) Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org From: Yan-Hsuan Chuang 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