Linux wireless drivers development
 help / color / mirror / Atom feed
From: Dmitry Gomzyakov <nicerok11@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: Dmitry Gomzyakov <nicerok11@gmail.com>
Subject: [PATCH 1/2] wifi: mt76: connac: add MT7991A (0x7991) to is_mt7996()
Date: Sun, 10 May 2026 15:29:10 +0500	[thread overview]
Message-ID: <20260510102911.1883849-2-kyoto1337@protonmail.com> (raw)
In-Reply-To: <20260510102911.1883849-1-kyoto1337@protonmail.com>

From: Dmitry Gomzyakov <nicerok11@gmail.com>

The MT7991A chipset uses PCI device ID 0x7991 (MT7996_DEVICE_ID_2),
but is_mt7996() only checks for 0x7990. This causes MT7991A devices
to use incorrect chip-specific settings, such as:
- MSDU_CNT_V2 instead of MSDU_CNT in TX descriptors
- Wrong WTBL BMC size (32 instead of 64)
- Incorrect prefetch depth for MCU queues

Fixes: 63a4edf1cb74 ("wifi: mt76: mt7996: add macros for pci decive id")
Signed-off-by: Dmitry Gomzyakov <nicerok11@gmail.com>
---
 mt76_connac.h | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/mt76_connac.h b/mt76_connac.h
index 51423c77..db07f3dc 100644
--- a/mt76_connac.h
+++ b/mt76_connac.h
@@ -230,7 +230,8 @@ static inline bool is_mt798x(struct mt76_dev *dev)
 
 static inline bool is_mt7996(struct mt76_dev *dev)
 {
-	return mt76_chip(dev) == 0x7990;
+	u16 chip = mt76_chip(dev);
+	return chip == 0x7990 || chip == 0x7991;
 }
 
 static inline bool is_mt7992(struct mt76_dev *dev)
-- 
2.54.0


  reply	other threads:[~2026-05-10 10:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-10 10:29 [PATCH 0/2] wifi: mt76: fix NAT performance degradation on MT799x Dmitry Gomzyakov
2026-05-10 10:29 ` Dmitry Gomzyakov [this message]
2026-05-10 10:29 ` [PATCH 2/2] wifi: mt76: mt7996: always fill txwi for 802.3 packets Dmitry Gomzyakov

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=20260510102911.1883849-2-kyoto1337@protonmail.com \
    --to=nicerok11@gmail.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