Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: jeff.chen_1@oss.nxp.com, linux-wireless@vger.kernel.org
Cc: francesco@dolcini.it, arend.vanspriel@broadcom.com,
	benjamin.berg@intel.com,  Jeff Chen <jeff.chen_1@nxp.com>
Subject: Re: [PATCH nxpwifi-next v3 1/3] wifi: nl80211: vendor-cmd: add NXP vendor command definitions
Date: Mon, 05 Oct 2026 07:49:47 +0200	[thread overview]
Message-ID: <7b3912fd8744fe5ec0c60b7da1fa9bfae0f87896.camel@sipsolutions.net> (raw)
In-Reply-To: <20261005054414.2874415-2-jeff.chen_1@oss.nxp.com>

On Mon, 2026-10-05 at 13:44 +0800, jeff.chen_1@oss.nxp.com wrote:
> From: Jeff Chen <jeff.chen_1@nxp.com>
> 
> Add NXP vendor command and attribute definitions for use with
> NL80211_CMD_VENDOR.
> 
> The initial user of this interface is the Transmit Rate-based Power
> Control (TRPC) configuration command.
> 
> The TRPC table is a firmware-defined ABI that contains TX power limit
> data. Existing nl80211 TX power interfaces allow TX power levels to be
> configured, but do not provide an interface for exchanging TRPC table
> data between userspace and firmware.
> 
> Therefore, the TRPC configuration interface is exposed through a vendor
> command. The kernel does not interpret the TRPC table contents and only
> passes the table data between userspace and firmware.
> 
> 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

  reply	other threads:[~2026-10-05  5:49 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 [this message]
2026-10-05  8:31   ` jeff.chen_1
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=7b3912fd8744fe5ec0c60b7da1fa9bfae0f87896.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=arend.vanspriel@broadcom.com \
    --cc=benjamin.berg@intel.com \
    --cc=francesco@dolcini.it \
    --cc=jeff.chen_1@nxp.com \
    --cc=jeff.chen_1@oss.nxp.com \
    --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