Linux wireless drivers development
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: <kvalo@kernel.org>
Cc: <linux-wireless@vger.kernel.org>
Subject: [PATCH 0/3] wifi: rtw89: correct BA CAM allocation
Date: Mon, 15 Aug 2022 15:07:00 +0800	[thread overview]
Message-ID: <20220815070703.26965-1-pkshih@realtek.com> (raw)

BA CAM is a global hardware resource, but we incorrectly see it as a
per-station resource. In station mode, it works well, but it will be wrong
if AP mode or multiple vif(s) in the future.

Therefore, move bitmap of BA_CAM to struct rtw89_dev::rtw89_cam_info.

Pine-Ke Shih (3):
  wifi: rtw89: 8852c: declare correct BA CAM number
  wifi: rtw89: 8852c: initialize and correct BA CAM content
  wifi: rtw89: correct BA CAM allocation

 drivers/net/wireless/realtek/rtw89/core.c     | 60 ++++++++++++-----
 drivers/net/wireless/realtek/rtw89/core.h     | 19 ++++--
 drivers/net/wireless/realtek/rtw89/debug.c    | 27 ++++++++
 drivers/net/wireless/realtek/rtw89/fw.c       | 66 ++++++++++++++++++-
 drivers/net/wireless/realtek/rtw89/fw.h       |  9 +++
 drivers/net/wireless/realtek/rtw89/rtw8852a.c |  3 +
 drivers/net/wireless/realtek/rtw89/rtw8852c.c |  3 +
 drivers/net/wireless/realtek/rtw89/ser.c      |  8 ++-
 8 files changed, 166 insertions(+), 29 deletions(-)

-- 
2.25.1


             reply	other threads:[~2022-08-15  7:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15  7:07 Ping-Ke Shih [this message]
2022-08-15  7:07 ` [PATCH 1/3] wifi: rtw89: 8852c: declare correct BA CAM number Ping-Ke Shih
2022-08-15  7:07 ` [PATCH 2/3] wifi: rtw89: 8852c: initialize and correct BA CAM content Ping-Ke Shih
2022-08-15  7:07 ` [PATCH 3/3] wifi: rtw89: correct BA CAM allocation Ping-Ke Shih
2022-08-15 12:20   ` 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=20220815070703.26965-1-pkshih@realtek.com \
    --to=pkshih@realtek.com \
    --cc=kvalo@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