From patchwork Tue Jun 16 12:46:10 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Shayne Chen X-Patchwork-Id: 215330 Return-Path: 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=-9.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU, HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_PATCH, MAILING_LIST_MULTI, MIME_BASE64_TEXT, SIGNED_OFF_BY, SPF_HELO_NONE, SPF_PASS, UNPARSEABLE_RELAY, USER_AGENT_GIT autolearn=unavailable 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 638F7C433E1 for ; Tue, 16 Jun 2020 12:46:51 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 4098B2071A for ; Tue, 16 Jun 2020 12:46:51 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=mediatek.com header.i=@mediatek.com header.b="BmQx9CxU" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728666AbgFPMqu (ORCPT ); Tue, 16 Jun 2020 08:46:50 -0400 Received: from mailgw01.mediatek.com ([210.61.82.183]:27315 "EHLO mailgw01.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1726526AbgFPMqu (ORCPT ); Tue, 16 Jun 2020 08:46:50 -0400 X-UUID: 08d2f915be1d4ee0a9833f846b7fe853-20200616 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mediatek.com; s=dk; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:Date:Subject:CC:To:From; bh=0zUnaVwf7NdA/yxdczKheQ3t79GOtZpyyLqwBUW4cDQ=; b=BmQx9CxUC+mvkntAi/PYoOWuPOxQuABN/tk84EaTG8t8jGwvGOcNZutj1k7WqQ3cQj5cRRpaG+u+Iss7+DDWSo1Y8L3VomXwxrY0SlHoriTJ6JEdXOv5kYUe4QcIUWnCC35dHV3UCrkhs9P2dtzJe0witpKJCCK9MwQpdLMobno=; X-UUID: 08d2f915be1d4ee0a9833f846b7fe853-20200616 Received: from mtkcas10.mediatek.inc [(172.21.101.39)] by mailgw01.mediatek.com (envelope-from ) (Cellopoint E-mail Firewall v4.1.10 Build 0809 with TLS) with ESMTP id 1121773539; Tue, 16 Jun 2020 20:46:46 +0800 Received: from mtkcas07.mediatek.inc (172.21.101.84) by mtkmbs02n1.mediatek.inc (172.21.101.77) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 16 Jun 2020 20:46:43 +0800 Received: from mtksdccf07.mediatek.inc (172.21.84.99) by mtkcas07.mediatek.inc (172.21.101.73) with Microsoft SMTP Server id 15.0.1497.2 via Frontend Transport; Tue, 16 Jun 2020 20:46:43 +0800 From: Shayne Chen To: Felix Fietkau CC: linux-wireless , Lorenzo Bianconi , Ryder Lee , Evelyn Tsai , linux-mediatek , Shayne Chen , Subject: [PATCH 1/4] dt-bindings: net: wireless: mt76: add ru property in power-limits node Date: Tue, 16 Jun 2020 20:46:10 +0800 Message-ID: <9ae2b6233284b60206e3513f7bf2eb03d2fbd724.1592276165.git.ryder.lee@mediatek.com> X-Mailer: git-send-email 2.18.0 MIME-Version: 1.0 X-MTK: N Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org This new property of power-limits node can be used to set per-rate tx power limits for 802.11ax rates. Cc: devicetree@vger.kernel.org Tested-by: Evelyn Tsai Signed-off-by: Shayne Chen --- The series is based on Felix's https://patchwork.kernel.org/project/linux-wireless/list/?series=295809 --- .../devicetree/bindings/net/wireless/mediatek,mt76.txt | 10 ++++++++++ 1 file changed, 10 insertions(+) -- 2.18.0 diff --git a/Documentation/devicetree/bindings/net/wireless/mediatek,mt76.txt b/Documentation/devicetree/bindings/net/wireless/mediatek,mt76.txt index 9d9ace0cfbf9..aefe880d36ff 100644 --- a/Documentation/devicetree/bindings/net/wireless/mediatek,mt76.txt +++ b/Documentation/devicetree/bindings/net/wireless/mediatek,mt76.txt @@ -101,6 +101,13 @@ Properties: which the rate set applies, followed by either 8 (MT7603/MT7628) or 10 (all other chips) power limit values. The order of the channel bandwidth settings is: 20, 40, 80, 160 MHz. +- ru: + sets of per-rate power limit values for 802.11ax rates for multiple + channel bandwidth or resource unit settings. + Each set starts with the number of channel bandwidth or resource unit + settings for which the rate set applies, followed by 12 power limit + values. The order of the channel resource unit settings is: + RU26, RU52, RU106, RU242/SU20, RU484/SU40, RU996/SU80, RU2x996/SU160. power-limit example: @@ -114,11 +121,14 @@ power-limits { ofdm = <23 23 23 23 23 23 23 23>; mcs = <1 23 23 23 23 23 23 23 23 23 23>, <3 22 22 22 22 22 22 22 22 22 22>; + ru = <3 22 22 22 22 22 22 22 22 22 22 22 22>, + <4 20 20 20 20 20 20 20 20 20 20 20 20>; }; r2 { channels = <100 181>; ofdm = <14 14 14 14 14 14 14 14>; mcs = <4 14 14 14 14 14 14 14 14 14 14>; + ru = <7 14 14 14 14 14 14 14 14 14 14 14 14>; }; }; };