public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
To: Ping-Ke Shih <pkshih@realtek.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH rtw-next] wifi: rtw89: Fill fw_version member of struct wiphy
Date: Thu, 26 Mar 2026 14:04:43 +0200	[thread overview]
Message-ID: <857919ae-e0bb-4dc8-9145-4071ac28cec0@gmail.com> (raw)
In-Reply-To: <9c25a5eee4194356b4d0210b2bace5f2@realtek.com>

On 26/03/2026 03:55, Ping-Ke Shih wrote:
> Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
>> Let userspace tools like lshw show the firmware version by filling the
>> fw_version member of struct wiphy.
>>
>> Before:
>>
>> configuration: broadcast=yes driver=rtw89_8852au
>> driverversion=6.19.6-arch1-1 firmware=N/A link=no multicast=yes
>> wireless=IEEE 802.11
>>
>> After:
>>
>> configuration: broadcast=yes driver=rtw89_8852au
>> driverversion=6.19.6-arch1-1 firmware=0.13.36.2 link=no multicast=yes
>> wireless=IEEE 802.11
>>
>> Signed-off-by: Bitterblue Smith <rtl8821cerfe2@gmail.com>
>> ---
>>  drivers/net/wireless/realtek/rtw89/fw.c | 8 ++++++++
>>  1 file changed, 8 insertions(+)
>>
>> diff --git a/drivers/net/wireless/realtek/rtw89/fw.c
>> b/drivers/net/wireless/realtek/rtw89/fw.c
>> index 45d8c5e70084..55aee6eb8478 100644
>> --- a/drivers/net/wireless/realtek/rtw89/fw.c
>> +++ b/drivers/net/wireless/realtek/rtw89/fw.c
>> @@ -755,6 +755,14 @@ static int rtw89_fw_update_ver(struct rtw89_dev *rtwdev,
>>                    fw_suit->major_ver, fw_suit->minor_ver, fw_suit->sub_ver,
>>                    fw_suit->sub_idex, fw_suit->commitid, fw_suit->cmd_ver,
>> type);
>>
>> +       if (type == RTW89_FW_NORMAL || type == RTW89_FW_NORMAL_CE ||
>> +           type == RTW89_FW_NORMAL_B)
>> +               snprintf(rtwdev->hw->wiphy->fw_version,
>> +                        sizeof(rtwdev->hw->wiphy->fw_version),
> 
> nit: how about defining a local variable wiphy? as well as rtw88.
> 

Okay, I will do that.

>> +                        "%u.%u.%u.%u",
>> +                        fw_suit->major_ver, fw_suit->minor_ver,
>> +                        fw_suit->sub_ver, fw_suit->sub_idex);
>> +
>>         return 0;
>>  }
>>
>> --
>> 2.53.0
> 


  reply	other threads:[~2026-03-26 12:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-25 22:21 [PATCH rtw-next] wifi: rtw89: Fill fw_version member of struct wiphy Bitterblue Smith
2026-03-26  1:55 ` Ping-Ke Shih
2026-03-26 12:04   ` Bitterblue Smith [this message]
2026-03-26  9:41 ` kernel test robot
2026-03-26 10:31 ` kernel test robot
2026-03-27  1:19 ` kernel test robot

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=857919ae-e0bb-4dc8-9145-4071ac28cec0@gmail.com \
    --to=rtl8821cerfe2@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.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