From: jeff.chen_1@oss.nxp.com
To: johannes@sipsolutions.net
Cc: linux-wireless@vger.kernel.org, francesco@dolcini.it,
kees+treewide@kernel.org, arend.vanspriel@broadcom.com,
benjamin.berg@intel.com
Subject: Re:[PATCH nxpwifi-next v3 1/3] wifi: nl80211: vendor-cmd: add NXP vendor command definitions
Date: Mon, 5 Oct 2026 16:31:21 +0800 [thread overview]
Message-ID: <20261005083121.2876637-1-jeff.chen_1@oss.nxp.com> (raw)
In-Reply-To: <20261005054414.2874415-2-jeff.chen_1@oss.nxp.com>
On 10/5/2026 1:49 PM, Johannes Berg wrote:
>> Example use cases include:
>> - Reading firmware TX power limit configuration for verification.
>> - Updating platform-specific TX power limit tables.
>> - Supporting manufacturing, validation, regulatory, and platform
>> bring-up workflows that require access to firmware-defined TX power
>> limit data.
>
> But ... none of this really needs full support on every production
> device, so it could just be debugfs?
>
> johannes
Hi Johannes
Sorry, the examples were not very precise.
The TRPC table is product-specific and is typically provided by the
module vendor or OEM. It depends on the RF characteristics of the
final product and may also vary by regulatory region.
This is not intended only for manufacturing or validation. It is used
to read and update firmware TX power limit configuration on deployed
systems.
I can clarify this in the next revision if needed.
rgards,
Jeff
next prev parent reply other threads:[~2026-10-05 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 5:44 [PATCH nxpwifi-next v3 0/3] wifi: nxpwifi: add TX power limit configuration support jeff.chen_1
2026-10-05 5:44 ` [PATCH nxpwifi-next v3 1/3] wifi: nl80211: vendor-cmd: add NXP vendor command definitions jeff.chen_1
2026-10-05 5:49 ` Johannes Berg
2026-10-05 8:31 ` jeff.chen_1 [this message]
2026-10-05 5:44 ` [PATCH nxpwifi-next v3 2/3] wifi: nxpwifi: add firmware TRPC command support jeff.chen_1
2026-10-05 5:44 ` [PATCH nxpwifi-next v3 3/3] wifi: nxpwifi: add netlink vendor command for TX power limits jeff.chen_1
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=20261005083121.2876637-1-jeff.chen_1@oss.nxp.com \
--to=jeff.chen_1@oss.nxp.com \
--cc=arend.vanspriel@broadcom.com \
--cc=benjamin.berg@intel.com \
--cc=francesco@dolcini.it \
--cc=johannes@sipsolutions.net \
--cc=kees+treewide@kernel.org \
--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