Linux wireless drivers development
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
	Bitterblue Smith <rtl8821cerfe2@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH rtw-next v2] wifi: rtw88: Fill fw_version member of struct wiphy
Date: Fri, 27 Mar 2026 06:23:39 +0000	[thread overview]
Message-ID: <4aa63ec1d1b74b7b83d1823844062885@realtek.com> (raw)
In-Reply-To: <2c90c306-f285-4ea7-b795-37a0f14ec27b@oss.qualcomm.com>


Jeff Johnson <jeff.johnson@oss.qualcomm.com> wrote:
> 
> On 3/26/2026 8:21 AM, Bitterblue Smith wrote:
> > Let userspace tools like lshw show the firmware version by filling the
> > fw_version member of struct wiphy.
> >
> > Before:
> >
> > configuration: broadcast=yes driver=rtw88_8814au
> > driverversion=6.19.6-arch1-1 firmware=N/A link=no multicast=yes
> > wireless=IEEE 802.11
> >
> > After:
> >
> > configuration: broadcast=yes driver=rtw88_8814au
> > driverversion=6.19.6-arch1-1 firmware=33.6.0 link=no multicast=yes
> > wireless=IEEE 802.11
> >
> > Signed-off-by: Bitterblue Smith <rtl8821cerfe2@gmail.com>
> > ---
> > v2:
> >  - Use local wiphy variable.
> > ---
> >  drivers/net/wireless/realtek/rtw88/main.c | 6 ++++++
> >  1 file changed, 6 insertions(+)
> >
> > diff --git a/drivers/net/wireless/realtek/rtw88/main.c
> b/drivers/net/wireless/realtek/rtw88/main.c
> > index c4f9758b4e96..cd9254370fcc 100644
> > --- a/drivers/net/wireless/realtek/rtw88/main.c
> > +++ b/drivers/net/wireless/realtek/rtw88/main.c
> > @@ -1805,6 +1805,7 @@ static void rtw_load_firmware_cb(const struct firmware
> *firmware, void *context)
> >  {
> >       struct rtw_fw_state *fw = context;
> >       struct rtw_dev *rtwdev = fw->rtwdev;
> > +     struct wiphy *wiphy = rtwdev->hw->wiphy;
> >
> >       if (!firmware || !firmware->data) {
> >               rtw_err(rtwdev, "failed to request firmware\n");
> > @@ -1819,6 +1820,11 @@ static void rtw_load_firmware_cb(const struct firmware
> *firmware, void *context)
> >       rtw_info(rtwdev, "%sFirmware version %u.%u.%u, H2C version %u\n",
> >                fw->type == RTW_WOWLAN_FW ? "WOW " : "",
> >                fw->version, fw->sub_version, fw->sub_index,
> fw->h2c_version);
> > +
> > +     if (fw->type == RTW_NORMAL_FW)
> > +             snprintf(wiphy->fw_version, sizeof(wiphy->fw_version),
> > +                      "%u.%u.%u",
> > +                      fw->version, fw->sub_version, fw->sub_index);
> >  }
> >
> >  static int rtw_load_firmware(struct rtw_dev *rtwdev, enum rtw_fw_type type)
> 
> generically speaking how useful is this?
> with MLO and multi-radio wiphy there can be multiple underlying hardware with
> different firmware versions. in recent ath drivers we are not filling this.

Thanks for the info.

Realtek WiFi has single one firmware version, I'd check firmware version by
kernel log personally. By commit message, Bitterblue uses lshw tool to read
the version, and I personally don't object this patch.

Ping-Ke


  reply	other threads:[~2026-03-27  6:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26 15:21 [PATCH rtw-next v2] wifi: rtw88: Fill fw_version member of struct wiphy Bitterblue Smith
2026-03-27  0:26 ` Jeff Johnson
2026-03-27  6:23   ` Ping-Ke Shih [this message]
2026-04-02  2:44 ` Ping-Ke Shih

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=4aa63ec1d1b74b7b83d1823844062885@realtek.com \
    --to=pkshih@realtek.com \
    --cc=jeff.johnson@oss.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rtl8821cerfe2@gmail.com \
    /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