linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Shayne Chen <shayne.chen@mediatek.com>, Felix Fietkau <nbd@nbd.name>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	Lorenzo Bianconi <lorenzo@kernel.org>,
	Ryder Lee <ryder.lee@mediatek.com>,
	Evelyn Tsai <evelyn.tsai@mediatek.com>,
	linux-mediatek <linux-mediatek@lists.infradead.org>,
	Peter Chiu <chui-hao.chiu@mediatek.com>,
	StanleyYP Wang <StanleyYP.Wang@mediatek.com>
Subject: RE: [PATCH 04/10] wifi: mt76: mt7996: rework DMA configuration for mt7990
Date: Mon, 31 Mar 2025 05:47:39 +0000	[thread overview]
Message-ID: <2f4874d10d86432693c73bfcb76e56dc@realtek.com> (raw)
In-Reply-To: <20250328055058.1648755-5-shayne.chen@mediatek.com>

Shayne Chen <shayne.chen@mediatek.com> wrote:

[...]

> -       if (is_mt7996(&dev->mt76)) {
> +       switch (mt76_chip(&dev->mt76)) {
> +       case MT7992_DEVICE_ID:
> +               RXQ_CONFIG(MT_RXQ_BAND1_WA, WFDMA0, MT_INT_RX_DONE_WA_EXT, MT7996_RXQ_MCU_WA_EXT);
> +               RXQ_CONFIG(MT_RXQ_BAND1, WFDMA0, MT_INT_RX_DONE_BAND1, MT7996_RXQ_BAND1);
> +               break;
> +       case MT7990_DEVICE_ID:

Does it mean MT7990_DEVICE_ID_2/MT7992_DEVICE_ID_2 (suffix with _2) has different
behavior from MT7990_DEVICE_ID/MT7992_DEVICE_ID ?

> +               RXQ_CONFIG(MT_RXQ_BAND1, WFDMA0, MT_INT_RX_DONE_BAND1, MT7996_RXQ_BAND1);
> +               RXQ_CONFIG(MT_RXQ_TXFREE_BAND0, WFDMA0,
> +                          MT_INT_RX_TXFREE_BAND0_MT7990, MT7990_RXQ_TXFREE0);
> +               if (dev->hif2)
> +                       RXQ_CONFIG(MT_RXQ_TXFREE_BAND1, WFDMA0,
> +                                  MT_INT_RX_TXFREE_BAND1_MT7990, MT7990_RXQ_TXFREE1);
> +               break;
> +       case MT7996_DEVICE_ID:
> +       default:
>                 /* mt7996 band2 */
> -               RXQ_CONFIG(MT_RXQ_BAND2, WFDMA0, MT_INT_RX_DONE_BAND2, MT7996_RXQ_BAND2);
>                 RXQ_CONFIG(MT_RXQ_BAND2_WA, WFDMA0, MT_INT_RX_DONE_WA_TRI, MT7996_RXQ_MCU_WA_TRI);
> -       } else {
> -               /* mt7992 band1 */
> -               RXQ_CONFIG(MT_RXQ_BAND1, WFDMA0, MT_INT_RX_DONE_BAND1, MT7996_RXQ_BAND1);
> -               RXQ_CONFIG(MT_RXQ_BAND1_WA, WFDMA0, MT_INT_RX_DONE_WA_EXT, MT7996_RXQ_MCU_WA_EXT);
> +               RXQ_CONFIG(MT_RXQ_BAND2, WFDMA0, MT_INT_RX_DONE_BAND2, MT7996_RXQ_BAND2);
> +               break;
>         }
> 
>         if (dev->has_rro) {




  reply	other threads:[~2025-03-31  5:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28  5:50 [PATCH 00/10] Add MT7990 support Shayne Chen
2025-03-28  5:50 ` [PATCH 01/10] wifi: mt76: mt7996: add macros for pci decive id Shayne Chen
2025-03-28  5:50 ` [PATCH 02/10] wifi: mt76: connac: add support to load firmware for mt7990 Shayne Chen
2025-03-31  4:40   ` Ping-Ke Shih
2025-04-01 13:25     ` Shayne Chen
2025-04-02  1:24       ` Ping-Ke Shih
2025-03-28  5:50 ` [PATCH 03/10] wifi: mt76: mt7996: rework WA mcu command " Shayne Chen
2025-03-28  5:50 ` [PATCH 04/10] wifi: mt76: mt7996: rework DMA configuration " Shayne Chen
2025-03-31  5:47   ` Ping-Ke Shih [this message]
2025-04-01 13:32     ` Shayne Chen
2025-03-28  5:50 ` [PATCH 05/10] wifi: mt76: mt7996: rework register mapping " Shayne Chen
2025-03-28  5:50 ` [PATCH 06/10] wifi: mt76: mt7996: add eeprom support " Shayne Chen
2025-03-28  5:50 ` [PATCH 07/10] wifi: mt76: mt7996: adjust HW capabilities " Shayne Chen
2025-03-28  5:50 ` [PATCH 08/10] wifi: mt76: connac: rework TX descriptor and TX free " Shayne Chen
2025-03-28  5:50 ` [PATCH 09/10] wifi: mt76: mt7996: rework background radar check " Shayne Chen
2025-03-31  5:55   ` Ping-Ke Shih
2025-04-01 13:47     ` Shayne Chen
2025-04-02  1:30       ` Ping-Ke Shih
2025-04-02 15:35         ` Ben Greear
2025-04-07  0:48           ` Ping-Ke Shih
2025-03-28  5:50 ` [PATCH 10/10] wifi: mt76: mt7996: add PCI device id " Shayne Chen

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=2f4874d10d86432693c73bfcb76e56dc@realtek.com \
    --to=pkshih@realtek.com \
    --cc=StanleyYP.Wang@mediatek.com \
    --cc=chui-hao.chiu@mediatek.com \
    --cc=evelyn.tsai@mediatek.com \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo@kernel.org \
    --cc=nbd@nbd.name \
    --cc=ryder.lee@mediatek.com \
    --cc=shayne.chen@mediatek.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;
as well as URLs for NNTP newsgroup(s).