linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: <linux-wireless@vger.kernel.org>
Cc: <ku920601@realtek.com>
Subject: [PATCH 4/9] wifi: rtw89: coex: Add PTA path control condition for chip RTL8922A
Date: Thu, 18 Apr 2024 10:12:02 +0800	[thread overview]
Message-ID: <20240418021207.32173-5-pkshih@realtek.com> (raw)
In-Reply-To: <20240418021207.32173-1-pkshih@realtek.com>

From: Ching-Te Ku <ku920601@realtek.com>

PTA(packet traffic arbitration) is a coexistence hardware feature.
Wi-Fi & Bluetooth owns their PTA, the function is to show whose PTA
control the traffic now. RTL8922A PTA control is controlled by hardware
logic, there is no register to monitor the setting.

Signed-off-by: Ching-Te Ku <ku920601@realtek.com>
Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
---
 drivers/net/wireless/realtek/rtw89/mac.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/wireless/realtek/rtw89/mac.c b/drivers/net/wireless/realtek/rtw89/mac.c
index aa5b396b5d2b..8b34044f7a8a 100644
--- a/drivers/net/wireless/realtek/rtw89/mac.c
+++ b/drivers/net/wireless/realtek/rtw89/mac.c
@@ -5705,7 +5705,7 @@ bool rtw89_mac_get_ctrl_path(struct rtw89_dev *rtwdev)
 	const struct rtw89_chip_info *chip = rtwdev->chip;
 	u8 val = 0;
 
-	if (chip->chip_id == RTL8852C)
+	if (chip->chip_id == RTL8852C || chip->chip_id == RTL8922A)
 		return false;
 	else if (chip->chip_id == RTL8852A || chip->chip_id == RTL8852B ||
 		 chip->chip_id == RTL8851B)
-- 
2.25.1


  parent reply	other threads:[~2024-04-18  2:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-18  2:11 [PATCH 0/9] wifi: rtw89: coex: update BT-coexistence mechanism for 8922A Ping-Ke Shih
2024-04-18  2:11 ` [PATCH 1/9] wifi: rtw89: coex: Allow Bluetooth doing traffic during Wi-Fi scan Ping-Ke Shih
2024-04-23 12:00   ` Ping-Ke Shih
2024-04-18  2:12 ` [PATCH 2/9] wifi: rtw89: coex: Add v7 firmware cycle status report Ping-Ke Shih
2024-04-18  2:12 ` [PATCH 3/9] wifi: rtw89: coex: Add version 3 report map of H2C command Ping-Ke Shih
2024-04-18  2:12 ` Ping-Ke Shih [this message]
2024-04-18  2:12 ` [PATCH 5/9] wifi: rtw89: coex: Update Bluetooth polluted Wi-Fi TX logic Ping-Ke Shih
2024-04-18  2:12 ` [PATCH 6/9] wifi: rtw89: coex: Add register monitor report v7 format Ping-Ke Shih
2024-04-18  2:12 ` [PATCH 7/9] wifi: rtw89: coex: Add GPIO signal control version 7 Ping-Ke Shih
2024-04-18  2:12 ` [PATCH 8/9] wifi: rtw89: coex: Add coexistence firmware control report version 8 Ping-Ke Shih
2024-04-18  2:12 ` [PATCH 9/9] wifi: rtw89: coex: Re-order the index for the report from firmware Ping-Ke Shih

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240418021207.32173-5-pkshih@realtek.com \
    --to=pkshih@realtek.com \
    --cc=ku920601@realtek.com \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).