From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.as201155.net (mail.as201155.net [185.84.6.188]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A8BF921A434 for ; Fri, 9 May 2025 10:57:02 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.84.6.188 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1746788224; cv=none; b=VcB1stcqC/zDT1VTCR8DTVNOjhgftxTp43fHAsjSCJDBkknlH16GGrCRGv/qpWLzEeroVbQVwpGFA4TtCleUMTId9OT1r5/+QecMKTDkLMix7qX7SaQO7dKZB0sTxC0mBAf+tV7HJSKFAGbGerSCwmqQLJEHvVJMSLsyvoyzc7I= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1746788224; c=relaxed/simple; bh=2IeBELKrdiOgj9sQP0UN1DOwP1jAHbiAvYs1eygumTU=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=AXVCsuQPo9fRQGxiuIYA2aDAFHVinXw/eBQoWbAl3u4V4ECDRb4qGAEBoL8tS+OjugdsWqIh8oKVtaa4LPXTphCvqzqSsOgQovjZKTRASUQjduec4B4LvGaZ1w3IaKeUT7KFkQYvRaDBfYowdHiEknNTCusM/Mw6eggJi2sBrO0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=dd-wrt.com; spf=pass smtp.mailfrom=dd-wrt.com; dkim=pass (1024-bit key) header.d=dd-wrt.com header.i=@dd-wrt.com header.b=DbuDqi1Z; arc=none smtp.client-ip=185.84.6.188 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=dd-wrt.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=dd-wrt.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=dd-wrt.com header.i=@dd-wrt.com header.b="DbuDqi1Z" Received: from smtps.newmedia-net.de ([2a05:a1c0:0:de::167]:57058 helo=webmail.newmedia-net.de) by mail.as201155.net with esmtps (TLS1) tls TLS_RSA_WITH_AES_256_CBC_SHA (Exim 4.97.1) (envelope-from ) id 1uDLNS-000000002Ns-1ED7; Fri, 09 May 2025 12:54:50 +0200 X-SASI-Hits: BODYTEXTP_SIZE_3000_LESS 0.000000, BODY_SIZE_1300_1399 0.000000, BODY_SIZE_2000_LESS 0.000000, BODY_SIZE_5000_LESS 0.000000, BODY_SIZE_7000_LESS 0.000000, CTE_7BIT 0.000000, DKIM_ALIGNS 0.000000, DKIM_SIGNATURE 0.000000, HTML_00_01 0.050000, HTML_00_10 0.050000, IN_REP_TO 0.000000, LEGITIMATE_SIGNS 0.000000, MSGID_SAMEAS_FROM_HEX_844412 0.100000, MSG_THREAD 0.000000, MULTIPLE_RCPTS 0.100000, MULTIPLE_REAL_RCPTS 0.000000, NO_CTA_FOUND 0.000000, NO_CTA_URI_FOUND 0.000000, NO_FUR_HEADER 0.000000, NO_URI_HTTPS 0.000000, OUTBOUND 0.000000, OUTBOUND_SOPHOS 0.000000, REFERENCES 0.000000, SENDER_NO_AUTH 0.000000, SUSP_DH_NEG 0.000000, USER_AGENT 0.000000, __ANY_URI 0.000000, __BODY_NO_MAILTO 0.000000, __BOUNCE_CHALLENGE_SUBJ 0.000000, __BOUNCE_NDR_SUBJ_EXEMPT 0.000000, __BULK_NEGATE 0.000000, __CT 0.000000, __CTE 0.000000, __CT_TEXT_PLAIN 0.000000, __DKIM_ALIGNS_1 0.000000, __DKIM_ALIGNS_2 0.000000, __DQ_NEG_DOMAIN 0.000000, __DQ_NEG_HEUR 0.000000, __DQ_NEG_IP 0.000000, __FORWARDED_MSG 0.000000, __FROM_DOMAIN_NOT_IN_BODY 0.000000, __FROM_NAME_NOT_IN_BODY 0.000000, __FUR_RDNS_SOPHOS 0.000000, __HAS_CC_HDR 0.000000, __HAS_FROM 0.000000, __HAS_MSGID 0.000000, __HAS_REFERENCES 0.000000, __HEADER_ORDER_FROM 0.000000, __IN_REP_TO 0.000000, __MAIL_CHAIN 0.000000, __MIME_BOUND_CHARSET 0.000000, __MIME_TEXT_ONLY 0.000000, __MIME_TEXT_P 0.000000, __MIME_TEXT_P1 0.000000, __MIME_VERSION 0.000000, __MOZILLA_USER_AGENT 0.000000, __MSGID_HEX_844412 0.000000, __MULTIPLE_RCPTS_CC_X2 0.000000, __MULTIPLE_RCPTS_TO_X2 0.000000, __NO_HTML_TAG_RAW 0.000000, __OUTBOUND_SOPHOS_FUR 0.000000, __OUTBOUND_SOPHOS_FUR_IP 0.000000, __OUTBOUND_SOPHOS_FUR_RDNS 0.000000, __RCVD_PASS 0.000000, __REFERENCES 0.000000, __SANE_MSGID 0.000000, __SCAN_D_NEG 0.000000, __SCAN_D_NEG2 0.000000, __SCAN_D_NEG_HEUR 0.000000, __SCAN_D_NEG_HEUR2 0.000000, __SUBJ_ALPHA_END 0.000000, __SUBJ_ALPHA_NEGATE 0.000000, __SUBJ_REPLY 0.000000, __TO_MALFORMED_2 0.000000, __TO_NAME 0.000000, __TO_NAME_DIFF_FROM_ACC 0.000000, __TO_REAL_NAMES 0.000000, __URI_NO_MAILTO 0.000000, __URI_NO_WWW 0.000000, __USER_AGENT 0.000000, __X_MAILSCANNER 0.000000 X-SASI-Probability: 8% X-SASI-RCODE: 200 X-SASI-Version: Antispam-Engine: 5.1.4, AntispamData: 2025.5.9.102728 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dd-wrt.com; s=mikd; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:From:References:Cc:To:Subject:MIME-Version:Date:Message-ID; bh=ZG2A4M5HrVgKF6WnP9PNNHK6AW1G98Fm256GbohKp/Q=; b=DbuDqi1ZaFYwjx5i5xL5AZnuMiPGC7LSokOxZZlYaXa+/n1eIHgYouA7PK3XQAc5424w86nuQU+ZUinejDGv5Fjtv7oVEmd5XBpIpghzF9e1bEPyMd03WTJ7Osd2LW6klnNL3jQOheFxNDhAppbqHJ6jE7P8ZaLJz3SW9sr87WE=; Message-ID: <73b2bd16-66aa-405c-acda-237d56be63dd@dd-wrt.com> Date: Fri, 9 May 2025 12:54:47 +0200 Precedence: bulk X-Mailing-List: linux-wireless@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Beta Subject: Re: Question about TX power To: Alexander Wilhelm , Jeff Johnson Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org References: From: Sebastian Gottschall In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Received-SPF: pass (webmail.newmedia-net.de: localhost is always allowed.) client-ip=127.0.0.1; envelope-from=s.gottschall@dd-wrt.com; helo=webmail.newmedia-net.de; X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: s.gottschall@dd-wrt.com X-SA-Exim-Scanned: No (on webmail.newmedia-net.de); SAEximRunCond expanded to false X-NMN-MailScanner-Information: Please contact the ISP for more information X-NMN-MailScanner-ID: 1uDLNQ-0009U4-FE X-NMN-MailScanner: Found to be clean X-NMN-MailScanner-From: s.gottschall@dd-wrt.com X-Received: from localhost ([127.0.0.1] helo=webmail.newmedia-net.de) by webmail.newmedia-net.de with esmtp (Exim 4.72) (envelope-from ) id 1uDLNQ-0009U4-FE; Fri, 09 May 2025 12:54:48 +0200 Am 09.05.2025 um 10:43 schrieb Alexander Wilhelm: > Hello devs, > > I'd like to understand how TX power setting works on ath11k devices. For example > when I'm using channel 36 for ETSI based regulatory domain, I can set up to 23 > dBm. But then I get only 20 dBm as a result. On different channels and/or > regulatory domains I get different reductions. I tried to follow the source > code. As far as I understood is that 'ath11k_mac_txpower_recalc' sets the > correct values and 'ath11k_mac_op_get_txpower' return the different one. > > My question is where this reduction offset is encoded. Is it in the module's > firmware or is it part of the boardfile? Thank you in advance. > > > Best regards > Alexander Wilhelm the boardfile contains chipset specific calibration data which also defines the hardware power limits (more specific data also included in the on board calibration flash of the device or if its a router, in flash memory of the router itself. in addition it includes a regulatory database which is used by the firmware for managing the total power. you have also to consider that the 23dbm are specified without antenna gain. so if the antenna gain is 3 dbm, you get 20 dbm in total. this antenna gain may again be specified in the boardfile. so you will not find your answers in any sourcecode. its all encoded in binary data. Sebastian