public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: <linux-wireless@vger.kernel.org>
Cc: <phhuang@realtek.com>
Subject: [PATCH rtw-next v2 0/4] wifi: rtw89: fw: update role_maintain H2C command
Date: Thu, 27 Feb 2025 21:12:24 +0800	[thread overview]
Message-ID: <20250227131228.8457-1-pkshih@realtek.com> (raw)

The role_maintain H2C command is to tell firmware the role of a mac_id,
and two additional fields are added by this patchset to support coming
MLO.

The patch 3/4 is to correct message format by the way.

The patch 4/4 is to prevent breaking users that use obsolete firmware.

v2:
 - add patch 4/4 that is structural dependency

Ping-Ke Shih (2):
  wifi: rtw89: fw: correct debug message format in
    rtw89_build_txpwr_trk_tbl_from_elm()
  wifi: rtw89: fw: don't reject firmware in blacklist to prevent
    breaking users

Po-Hao Huang (2):
  wifi: rtw89: fw: use struct to fill role_maintain H2C command
  wifi: rtw89: fw: update role_maintain H2C command for roles operating
    on band 1

 drivers/net/wireless/realtek/rtw89/fw.c | 42 +++++++++++++++----------
 drivers/net/wireless/realtek/rtw89/fw.h | 28 ++++++-----------
 2 files changed, 36 insertions(+), 34 deletions(-)

-- 
2.25.1


             reply	other threads:[~2025-02-27 13:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27 13:12 Ping-Ke Shih [this message]
2025-02-27 13:12 ` [PATCH rtw-next v2 1/4] wifi: rtw89: fw: use struct to fill role_maintain H2C command Ping-Ke Shih
2025-03-05 11:51   ` Ping-Ke Shih
2025-02-27 13:12 ` [PATCH rtw-next v2 2/4] wifi: rtw89: fw: update role_maintain H2C command for roles operating on band 1 Ping-Ke Shih
2025-02-27 13:12 ` [PATCH rtw-next v2 3/4] wifi: rtw89: fw: correct debug message format in rtw89_build_txpwr_trk_tbl_from_elm() Ping-Ke Shih
2025-02-27 13:12 ` [PATCH rtw-next v2 4/4] wifi: rtw89: fw: don't reject firmware in blacklist to prevent breaking users 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=20250227131228.8457-1-pkshih@realtek.com \
    --to=pkshih@realtek.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=phhuang@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