Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp9162659ybi; Tue, 23 Jul 2019 23:05:55 -0700 (PDT) X-Google-Smtp-Source: APXvYqwOxc0zEcDATeQ96+wRtzAqyf0SeDh4ARKk2n2UA4a5wZFNTqX1ggd7ibITrG5gxqeUXDRY X-Received: by 2002:a17:90a:3724:: with SMTP id u33mr85029922pjb.19.1563948355691; Tue, 23 Jul 2019 23:05:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1563948355; cv=none; d=google.com; s=arc-20160816; b=gyaHPmqEy28t7wYpl5MQN58rKuSsh1JmR8e3YMjq6zH7Bb4dvs9Es9LKdtDQ/aXgtz m/Tt6X5TwlE1Y5rOncYO19ZMYA6C0bee+gjxbBoQE+2tC8UNAn2DR+JXCzEEwSXc1jhe N/8hgJ9coc4i//W9aOgguHcu3HZ9AemFDsbCxnotcz5fHE+XUzxaMG75IbgpYrdUqVxT wQDrEHCKuRhTWkTQ5NJEwd2gabWrN9sIpq8hEbuNRRamxMy7yQXO1wzwSXyFiyorHytg 2NFKh09vpymDDwC59XZcldN+LAds0ECtpJ4Rvz3OqCtfBiO2irAYvUJaC+xw736xwptY PfTA== 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=ux+qwoHu/PD+311h0rkcvQaS7tWcuLrnb7GC5Zm9ogk=; b=SF85svuhjte9w8OImaHhm0VGIdzLpMh+rQ8rVHWLTeY3rqzuunLMpq+S3mzV2Pfrpy W/C/HYezle9626QuQVKaQOUq6S1X7Y+cJRBt/s3Lkrez5+3av5uuLaUYaDHFNlAoJdzq 8O1dTXQfPzl8PVnmhJa2Lmj8S/dAE2gkCAJCyXjKOoIhIT2KABuJJr4gI0+Ni/L1GPz4 Mzj6tXiwtgD9f6jPb2LGKBxSfTNN0BVa0dj+gnjxypsvlhgA1OyTSpfrBEi78qW2D2U/ Avranai0dXuLot+oy7nEfRhwGZVGXKneGAGifkelhdUE9cx+HW8kfEAks4NGODTdZnDj Kg0w== 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 y2si12192088pgp.284.2019.07.23.23.05.40; Tue, 23 Jul 2019 23:05:55 -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 S1726339AbfGXGFC (ORCPT + 99 others); Wed, 24 Jul 2019 02:05:02 -0400 Received: from rtits2.realtek.com ([211.75.126.72]:49311 "EHLO rtits2.realtek.com.tw" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725990AbfGXGFC (ORCPT ); Wed, 24 Jul 2019 02:05:02 -0400 Authenticated-By: X-SpamFilter-By: BOX Solutions SpamTrap 5.62 with qID x6O64o4O011105, This message is accepted by code: ctloc85258 Received: from mail.realtek.com (RTITCASV01.realtek.com.tw[172.21.6.18]) by rtits2.realtek.com.tw (8.15.2/2.57/5.78) with ESMTPS id x6O64o4O011105 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 24 Jul 2019 14:04:50 +0800 Received: from localhost.localdomain (172.21.68.126) by RTITCASV01.realtek.com.tw (172.21.6.18) with Microsoft SMTP Server id 14.3.439.0; Wed, 24 Jul 2019 14:04:50 +0800 From: To: CC: , , Subject: [PATCH 0/5] rtw88: add support for BT co-existence mechanism Date: Wed, 24 Jul 2019 14:04:28 +0800 Message-ID: <1563948273-17910-1-git-send-email-yhchuang@realtek.com> X-Mailer: git-send-email 2.7.4 MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [172.21.68.126] Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org From: Yan-Hsuan Chuang This patch set mainly adds a BT co-existence mechanism, which helps WiFi device to work with BT device concurrently without interfering each other. For Realtek's WiFi/BT combo devices, the co-existence mechanism is on the WiFi side. The first two patches "rtw88: switch specified efuse bank" and "rtw88: check efuse for BT FT S1" aim to check if the device is able to run with WiFi + BT, because some of the earlier devices manufactured are in development for testing. These device hence did not program the efuse for BT. Without being programed, some of the hardware parameters are incorrect. The rest of the patches add BTcoex support. BTcoex needs to wake up events that is waiting for some C2H reported in IRQ context, so these C2H skbs do not required to be queued into workqueues to be processed. What we need to do is to simply wake it uin IRQ context. And actually C2H workqueue context should be protected by rtwdev->mutex lock to perform some hardware operations against mac80211 callbacks. The final patch contains the most of the BTcoex logic. It is not that complicated, just to gather information and make decision on WiFi driver side. What makes the code so much is that the mechanism needs to take care of a lot of WiFi/BT combinations. Such as if WiFi is at 2G or is having a lot of traffic or is connecting to AP. And BT has many profiles such as A2DP/HID/PAN or it is slave or not. Yan-Hsuan Chuang (5): rtw88: switch specified efuse bank rtw88: check efuse for BT FT S1 rtw88: allow c2h operation in irq context rtw88: enclose c2h cmd handle with mutex rtw88: add BT co-existence support drivers/net/wireless/realtek/rtw88/Makefile | 1 + drivers/net/wireless/realtek/rtw88/coex.c | 2462 +++++++++++++++++++++++++ drivers/net/wireless/realtek/rtw88/coex.h | 363 ++++ drivers/net/wireless/realtek/rtw88/efuse.c | 30 +- drivers/net/wireless/realtek/rtw88/fw.c | 135 +- drivers/net/wireless/realtek/rtw88/fw.h | 73 + drivers/net/wireless/realtek/rtw88/mac80211.c | 19 + drivers/net/wireless/realtek/rtw88/main.c | 45 +- drivers/net/wireless/realtek/rtw88/main.h | 233 +++ drivers/net/wireless/realtek/rtw88/pci.c | 6 +- drivers/net/wireless/realtek/rtw88/ps.c | 9 + drivers/net/wireless/realtek/rtw88/reg.h | 62 + drivers/net/wireless/realtek/rtw88/rtw8822b.c | 460 ++++- drivers/net/wireless/realtek/rtw88/rtw8822c.c | 355 +++- 14 files changed, 4216 insertions(+), 37 deletions(-) create mode 100644 drivers/net/wireless/realtek/rtw88/coex.c create mode 100644 drivers/net/wireless/realtek/rtw88/coex.h -- 2.7.4