public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Shengyu Qu <wiagn233@outlook.com>, "nbd@nbd.name" <nbd@nbd.name>,
	"lorenzo@kernel.org" <lorenzo@kernel.org>,
	"ryder.lee@mediatek.com" <ryder.lee@mediatek.com>,
	"shayne.chen@mediatek.com" <shayne.chen@mediatek.com>,
	"sean.wang@mediatek.com" <sean.wang@mediatek.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>
Cc: "johannes@sipsolutions.net" <johannes@sipsolutions.net>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"angelogioacchino.delregno@collabora.com"
	<angelogioacchino.delregno@collabora.com>,
	Peter Chiu <chui-hao.chiu@mediatek.com>
Subject: RE: [PATCH v1] mt76: mt7915: wed: find rx token by physical address
Date: Wed, 12 Mar 2025 01:41:15 +0000	[thread overview]
Message-ID: <e144d2ffe9924d81a7b60f38cdcf516a@realtek.com> (raw)
In-Reply-To: <TYCPR01MB843726907C170CFE2D3EB7BE98D12@TYCPR01MB8437.jpnprd01.prod.outlook.com>

Shengyu Qu <wiagn233@outlook.com> wrote:
> 
> Hi Shih,
> 
> Can you also give this patch a review? Seems I also need to convert to
> reverse Xmas tree order for this patch, will do it in next version.

Yes. Please do it.

> 
> Best regards,
> Shengyu
> 
> 在 2025/2/22 19:38, Shengyu Qu 写道:
> > The token id in RxDMAD may be incorrect when it is not the last frame
> > due to WED HW bug. Lookup correct token id by physical address in sdp0.
> >
> > Downstream patch link:
> https://git01.mediatek.com/plugins/gitiles/openwrt/feeds/mtk-openwrt-feeds/+/737340322ab22b138fd200e02
> 0d61ffdbe3e36a9/autobuild/autobuild_5.4_mac80211_release/mt7988_wifi7_mac80211_mlo/package/kernel/mt76
> /patches/0062-mtk-wifi-mt76-mt7915-wed-find-rx-token-by-physical-a.patch
> >
> > Signed-off-by: Peter Chiu <chui-hao.chiu@mediatek.com>
> > Signed-off-by: Shengyu Qu <wiagn233@outlook.com>
> > ---
> >   drivers/net/wireless/mediatek/mt76/dma.c | 25 +++++++++++++++++++++++-
> >   1 file changed, 24 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/wireless/mediatek/mt76/dma.c b/drivers/net/wireless/mediatek/mt76/dma.c
> > index 844af16ee551..5bf63014263c 100644
> > --- a/drivers/net/wireless/mediatek/mt76/dma.c
> > +++ b/drivers/net/wireless/mediatek/mt76/dma.c
> > @@ -444,9 +444,32 @@ mt76_dma_get_buf(struct mt76_dev *dev, struct mt76_queue *q, int idx,
> >   	mt76_dma_should_drop_buf(drop, ctrl, buf1, desc_info);
> >
> >   	if (mt76_queue_is_wed_rx(q)) {
> > +		u32 id, find = 0;
> >   		u32 token = FIELD_GET(MT_DMA_CTL_TOKEN, buf1);
> > -		struct mt76_txwi_cache *t = mt76_rx_token_release(dev, token);
> > +		struct mt76_txwi_cache *t;
> > +
> > +		if (*more) {

Because of scope, should define 'find' (or 'found'?) as bool here.

> > +			spin_lock_bh(&dev->rx_token_lock);
> > +
> > +			idr_for_each_entry(&dev->rx_token, t, id) {

idr_find() can only get a pointer associated with the ID. Not sure if it can
have a reverse way -- get ID from pointer. With sequential search in data path,
cost is higher.

Maybe you can consider to build association between argument 'idx' and
pointer/token by another patch.

But logic is okay to me.

> > +				if (t->dma_addr == le32_to_cpu(desc->buf0)) {
> > +					find = 1;
> > +					token = id;
> > +
> > +					/* Write correct id back to DMA*/
> > +					u32p_replace_bits(&buf1, id,
> > +							  MT_DMA_CTL_TOKEN);
> > +					WRITE_ONCE(desc->buf1, cpu_to_le32(buf1));
> > +					break;
> > +				}
> > +			}
> > +
> > +			spin_unlock_bh(&dev->rx_token_lock);
> > +			if (!find)
> > +				return NULL;
> > +		}
> >
> > +		t = mt76_rx_token_release(dev, token);
> >   		if (!t)
> >   			return NULL;
> >


  reply	other threads:[~2025-03-12  1:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-22 11:38 [PATCH v1] mt76: mt7915: wed: find rx token by physical address Shengyu Qu
2025-03-11  8:51 ` Shengyu Qu
2025-03-12  1:41   ` Ping-Ke Shih [this message]
2025-03-12  9:09     ` Felix Fietkau
2025-03-13 12:43       ` Shengyu Qu
2025-03-13 12:47         ` Felix Fietkau
2025-03-13 13:09           ` Shengyu Qu

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=e144d2ffe9924d81a7b60f38cdcf516a@realtek.com \
    --to=pkshih@realtek.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=chui-hao.chiu@mediatek.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo@kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=nbd@nbd.name \
    --cc=ryder.lee@mediatek.com \
    --cc=sean.wang@mediatek.com \
    --cc=shayne.chen@mediatek.com \
    --cc=wiagn233@outlook.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