Message ID | 20200309075852.11454-1-yhchuang@realtek.com |
---|---|
Headers | show
Return-Path: <SRS0=sCwD=42=vger.kernel.org=linux-wireless-owner@kernel.org> X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI, SPF_HELO_NONE, SPF_PASS, USER_AGENT_GIT autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id EB313C10F27 for <linux-wireless@archiver.kernel.org>; Mon, 9 Mar 2020 07:59:07 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id B74D820728 for <linux-wireless@archiver.kernel.org>; Mon, 9 Mar 2020 07:59:07 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726379AbgCIH7H (ORCPT <rfc822;linux-wireless@archiver.kernel.org>); Mon, 9 Mar 2020 03:59:07 -0400 Received: from rtits2.realtek.com ([211.75.126.72]:57820 "EHLO rtits2.realtek.com.tw" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725942AbgCIH7H (ORCPT <rfc822;linux-wireless@vger.kernel.org>); Mon, 9 Mar 2020 03:59:07 -0400 Authenticated-By: X-SpamFilter-By: BOX Solutions SpamTrap 5.62 with qID 0297wva1011842, 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 0297wva1011842 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 9 Mar 2020 15:58:57 +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; Mon, 9 Mar 2020 15:58:57 +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; Mon, 9 Mar 2020 15:58:56 +0800 From: <yhchuang@realtek.com> To: <kvalo@codeaurora.org> CC: <linux-wireless@vger.kernel.org>, <briannorris@chromium.org> Subject: [PATCH v2 0/2] rtw88: add coex related debugfs Date: Mon, 9 Mar 2020 15:58:50 +0800 Message-ID: <20200309075852.11454-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: <linux-wireless.vger.kernel.org> X-Mailing-List: linux-wireless@vger.kernel.org |
Series |
rtw88: add coex related debugfs
|
expand
|
From: Yan-Hsuan Chuang <yhchuang@realtek.com> 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. v1 -> v2 * don't ignore "ignore wlan command" 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 | 63 +++ 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, 641 insertions(+)