From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from rtits2.realtek.com.tw (rtits2.realtek.com [211.75.126.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B32983806B5 for ; Mon, 13 Apr 2026 05:56:37 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=211.75.126.72 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776059799; cv=none; b=LT+EmwtpAQejc2863EsPmnhJn6WxymqFOncGGCukOwHvKmngeXdRBxq3/w8KB+OP1dbvWdgOdji52iyACBF8w4qi8Yef4yXLFCkXrXbDl3W3Qjq0qglZJ5J4Q87SaUB4rlQZcSiqRr6eqzop5jh9LOwYXwibYDbswLWjm8L9vkI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776059799; c=relaxed/simple; bh=bNnrnUhMF6GJlvM4ilhd7gA1kL3sqNq1o++DY5Ig9N4=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:MIME-Version; b=JRBZQi1HhqGds09Fmv0TNHknTuqB8F5SVrdIMzVtC1ND2jXiTP7OD/fr9wkEcJ/L41i74S8sCPkRj8vcg+XWPbOFrLJ88O9mgopoKp0XeQVKGuaQzwmrR51PGLJhQmhVp/9MAybk35tCVHwBMiYBSFFhx9+kq6Ml2vHjQSX8+LE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=realtek.com; spf=pass smtp.mailfrom=realtek.com; dkim=pass (2048-bit key) header.d=realtek.com header.i=@realtek.com header.b=GyXPFs6W; arc=none smtp.client-ip=211.75.126.72 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=realtek.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=realtek.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=realtek.com header.i=@realtek.com header.b="GyXPFs6W" X-SpamFilter-By: ArmorX SpamTrap 5.80 with qID 63D5uHg553727833, This message is accepted by code: ctloc85258 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=realtek.com; s=dkim; t=1776059777; bh=bNnrnUhMF6GJlvM4ilhd7gA1kL3sqNq1o++DY5Ig9N4=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=GyXPFs6Wz/JUT1kFMhrl1HZsAfch8ooGDKb/LtGdh+y7faNrLQKYStDBGszm74dHC GNzO3Nv3iU+x00iwV0WdgSqxOO/fdv/x9GNvH3+kpc0GQOQYh23tVW6caeVjfBEA4L TdKSKuPtIUcrbdbgbaFQ+oAbRDDJq4KH/0zvg8CJ+zN+EvMkEG4a1BOvxOEqIR6XJD tGVHKVQFK9V6UZUp1pOJAdhRgrKbgRdZH2RhaSRz0k0oufysA67jCe/voFRkp+gOzd Qx6g6ooWGd27znfZiLT4P4D//5ZOcyak3SMWS28ZQ2/C7KUhf/G19rVUGBiZAq7epV AKJbtk0lIfRpw== Received: from mail.realtek.com (rtkexhmbs02.realtek.com.tw[172.21.6.41]) by rtits2.realtek.com.tw (8.15.2/3.26/5.94) with ESMTPS id 63D5uHg553727833 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 13 Apr 2026 13:56:17 +0800 Received: from RTKEXHMBS06.realtek.com.tw (10.21.1.56) by RTKEXHMBS02.realtek.com.tw (172.21.6.41) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1748.10; Mon, 13 Apr 2026 13:56:17 +0800 Received: from RTKEXHMBS06.realtek.com.tw ([fe80::ed72:3015:2840:4458]) by RTKEXHMBS06.realtek.com.tw ([fe80::ed72:3015:2840:4458%10]) with mapi id 15.02.1748.010; Mon, 13 Apr 2026 13:56:17 +0800 From: Ping-Ke Shih To: Thadeu Lima de Souza Cascardo CC: Kalle Valo , Yan-Hsuan Chuang , "linux-wireless@vger.kernel.org" , "kernel-dev@igalia.com" Subject: RE: [PATCH] rtw88: add TX power limit support to 114 and 130 channels Thread-Topic: [PATCH] rtw88: add TX power limit support to 114 and 130 channels Thread-Index: AQHcrZj6b0aZaPK17kqRjXoafOBZKbXX3tPQ///l4ICABPIGEA== Date: Mon, 13 Apr 2026 05:56:17 +0000 Message-ID: References: <20260306-rtw88_channel130-v1-1-ff25a5bc930a@igalia.com> <55c23c5551354c6f8752d620f268b37b@realtek.com> In-Reply-To: Accept-Language: en-US, zh-TW Content-Language: zh-TW Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Precedence: bulk X-Mailing-List: linux-wireless@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Thadeu Lima de Souza Cascardo wrote: > On Fri, Apr 10, 2026 at 03:56:11AM +0000, Ping-Ke Shih wrote: > > Thadeu Lima de Souza Cascardo wrote: > > > Though 114 and 130 are not usual channels, they are found in the wild= with > > > setups using 5350MHz as the center frequency of a 80MHz setup. > > > > What did the AP setup? channel 114 160MHz? > > I wonder why rtw88 can select a not usual channel 114 80MHz. > > > > Please share your environment setup. > > >=20 > This is a Mikrotik that uses channel 130 at 80MHz. I'm surprised that an AP can work on this not usual channel/bandwidth.=20 Can you change the setting to usual channel/bandwidth? We'd avoid using this unsupported channel/bandwidth by [1]. >=20 > > > > > > rtw88 supports that, but issues a WARNING because it cannot find the = TX > > > power limit for those channels. > > > > Actually, rtw88 hardware can't support that, so we are working on patch > > to avoid selecting unusual channels. Can it work properly with > > the AP after this patch? > > >=20 > It does work just fine even without the patch. The only issue is the > WARNING that is triggered. >=20 As internal discussion, hardware doesn't work on channel 130 80M, which means connection might be well, but it can't yield expected performan= ce. More, the power limit is not really verified on ch130 80M, so we wonder that the signal might not in expectation. By above reasons, we'd avoid using channel 114 and 130. [1] https://lore.kernel.org/linux-wireless/20260413053601.13037-1-pkshih@re= altek.com/T/#u