Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp958313pxb; Wed, 3 Mar 2021 22:31:32 -0800 (PST) X-Google-Smtp-Source: ABdhPJyWcfqr36Z0iQ9//plF/hLJyYQn/Zsw54nzmyI7XZmv6It13rH+IpTLOXjYCumwxDSpwHB9 X-Received: by 2002:a17:906:a101:: with SMTP id t1mr2678134ejy.182.1614839492372; Wed, 03 Mar 2021 22:31:32 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1614839492; cv=none; d=google.com; s=arc-20160816; b=hfZUqjy0MOI5Y5m9natUc+4ir4QXMAyKBaI+z55QG30BDlDkBuaKsi6cgocPVYfqiS loN7r7R69ouJ7I1WpNNzHnY67G2hzUh8ZgKFu+mVAnbZA5zpowDFfJUQRanuW8X/ddC7 hDrk1a+MS3kkKbl8pREMOm5pa8WXdphFANRR97vify8Vlcrpp8B+Lef8deliyON9DJuU Xd2pFeS8jeRbqJaAGMGQfI4la/IXyNfC5wKR2LjYPd8grMcLvAi7FamY+c5AY8/inQri kArWrSizv6nGRkDMwE4V0f2+pDEZR7Ydwa1ETLjWws4LAOF25DRfcbJJWd3x80nmBJmP SnFA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=DsSBlNf4EXaAwJmAP2RXqC/NeSvnZ6EawMkhhwwqhy8=; b=dKk7oHsbABoRgTNpmAdb+khkQpHXHzK4L37gB6yEB6/Rx483Td9sQ4+ai5ewEukXCe X69Eac0NnSTqDaVZXguLycM9bNTW5l4uYfRUHF0heChl9eBaNOqZx7wlToeXu3bP0I1t Skqh3C7cp2v3TOYdgri2OdoI374GRDCZmSAa5jJs1ydIESjGlKCbz66fwF6pxvtdhlYC HNUnqgbtw8r7N5RZv8C+ayR0orUqJTQMrOtolM3eWKTsDesiEclSricq5CAvYxazGebK 1UbdEdwSkWHVdwbrkdbq0UmZf1+CIT34TulMg8IIeJfoEC1/jqF5kzfNNVNRJNxNqh0s mFlQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Lheh9tG6; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id e16si6637535edz.607.2021.03.03.22.31.09; Wed, 03 Mar 2021 22:31:32 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Lheh9tG6; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1351802AbhCBRtw (ORCPT + 99 others); Tue, 2 Mar 2021 12:49:52 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47904 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1578417AbhCBPQI (ORCPT ); Tue, 2 Mar 2021 10:16:08 -0500 Received: from mail-qt1-x832.google.com (mail-qt1-x832.google.com [IPv6:2607:f8b0:4864:20::832]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2BD86C061756 for ; Tue, 2 Mar 2021 07:08:03 -0800 (PST) Received: by mail-qt1-x832.google.com with SMTP id h9so5082191qtq.7 for ; Tue, 02 Mar 2021 07:08:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=DsSBlNf4EXaAwJmAP2RXqC/NeSvnZ6EawMkhhwwqhy8=; b=Lheh9tG6wk4rjSd4mQvAVKVJXQvm46sLRQGsb12SHoEeMRycT/oCP2CeGYfF5NG433 ItW3m28QEdPazBHKU7jA0bi1YGTtXUn0+6ZoFcj12M7AZ7CjNDusEBFV03ziE5Fuq1mH 6rgnMI2Ax+wSuDhTdSqpI+esMRwKyU0SHFFSecI1r0+3ePrOAnUzVHXu/DyMtt1PeiKf elgA3/M2Lj5FtPKuRJUXo9+YEjMMyHM6U7lAR4u4JTcRTEyLjxTLvW6PLF1GF1u5Eg0P CogEFVoXCNljGeWnmNlqV7gPt9Ec7jmlEwVLRDFqxRPLORwgijig5orzD/rb7yqVzkJc ZoWw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=DsSBlNf4EXaAwJmAP2RXqC/NeSvnZ6EawMkhhwwqhy8=; b=ZuS2aN2MbliU5uXWWZ5E0rfPcRFOnB7Dd9dCSS9+p/L0mR5VGW/KJXJObduH1Q0xyH 2r3OjXPVXE1nnhJkyki1Ju5YwHda9MQXacN/5OLElit+UxKAVzveH5vlu3Fkq9CWUBwX bpFQZztygQd2+Qe/XsCsgfV8Sai260Pfa7EQ7QbIVHBl11EvVvBPkE+/tcRA0sA+TysR VLat9uiEgjMdwn9/VGm3aVZqw4/y+vXY4Xvj1tzn4n/YeTEMmAZJVlE+WZpqNT7Gsfrp a/Cz25u9fRe9fYyNe1NMNq/4CEihVkNZsIAsvYTlLogGZ+32106o3MMeh35IUL9Xn/ws 3qjg== X-Gm-Message-State: AOAM5326OItgl5RtwaCbIsuxjTRm5tu6IA5vGGkf77zZjsHnYv/URXfd 6Mkvqo7ATsiCVaJnnCBKG4gKFh3FbbRJpdXf3Ag= X-Received: by 2002:ac8:6683:: with SMTP id d3mr18451797qtp.228.1614697682144; Tue, 02 Mar 2021 07:08:02 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?B?6YKx5ZCN56Kp?= Date: Tue, 2 Mar 2021 23:07:50 +0800 Message-ID: Subject: Re: Questions for TX power get/set implementation of realtek WiFi To: pkshih@realtek.com, tehuang@realtek.com, Larry.Finger@lwfinger.net Cc: Reto Schneider , kvalo@codeaurora.org, kuba@kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org =E9=82=B1=E5=90=8D=E7=A2=A9 =E6=96=BC 2021=E5=B9=B43= =E6=9C=882=E6=97=A5 =E9=80=B1=E4=BA=8C =E4=B8=8B=E5=8D=886:21=E5=AF=AB=E9= =81=93=EF=BC=9A > > Hi guys, > I'm planning to implement the get_txpower hook function of the > struct ieee80211_ops and handle the IEEE80211_CONF_CHANGE_POWER for > rtl8xxxu driver. So that users can get the information of the current > tx power limit and set a new limit value with iw commands. > > I found there's phy_txpwr_idx_to_dbm() of each driver in > realtek/rtlwifi to translate the tx power index parsed from efuse to > tx power level in dBm. Does the power level translated represent the > current tx power limit in dBm? In my RTL8188CUS module, the power > index of CCK/OFDM from efuse for each channel is basically 36/38, thus > the translated txpower level is 11dBm. Is this the expected value for > the default txpower limit value? Or do I need some other formula to > compute? > > And for the handler of IEEE80211_CONF_CHANGE_POWER, can I > translate the hw->conf.power_level with the phy_dbm_to_txpwr_idx > functions I found in some rtlwifi family drivers, then directly set > the txpower index with phy_set_txpower_index functions which write > power index to bbreg for different rates (CCK and OFDM)? Are there > some invalid values I should take care of because the TCP RX > performance seems to be extremely low when I write the power index > value translated from 20dBm to bbreg. Any suggestions for what I > should handle before writing the bbreg? > > Chris Sorry for confusion. I'm removing and correcting the invalid mail address h= ere.