Linux wireless drivers development
 help / color / mirror / Atom feed
From: Cristian Papa <pcristian292@gmail.com>
To: Felix Fietkau <nbd@nbd.name>
Cc: linux-wireless@vger.kernel.org
Subject: mt76: test report for three pending power-save fixes (MT7603E/MT7662E)
Date: Wed, 14 Oct 2026 03:22:43 -0300	[thread overview]
Message-ID: <20261014062426.9282-1-pcristian292@gmail.com> (raw)

Hi Felix,

I backported these commits from your pending branch, unchanged, onto
mt76 be5ce7910521 (backports 7.2, Linux 6.18.44) for a TP-Link Archer
XR500v (MT7603E 2.4 GHz + MT7662E 5 GHz):

  56b110804361 wifi: mt76: mt76x02: serialise wcid drop mask updates
  05fc7fb18f09 wifi: mt76: mt76x02: clear the wcid drop mask for all powersave responses
  2b7be52496ac wifi: mt76: honour the more-data flag when releasing buffered frames

With a phone associated to the MT7662E AP, three screen-off/wake cycles
(60 s each, browsing after each wake) worked without reconnecting, and
there were no resets or kernel warnings. The same three cycles on the
MT7603E AP, with a 1 Hz ping from the AP to the phone running throughout
(about 8 minutes), gave 474/474 replies, no reassociation, no resets and
no kernel warnings.

This is only a functional smoke test: I did not capture PS-Poll/U-APSD
or check MoreData/EOSP over the air, and the image carries other local
changes, so it does not isolate each commit.

Is anything holding these back from master, or is there a specific test
that would help?

Thanks,
Cristian

                 reply	other threads:[~2026-10-14  6:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20261014062426.9282-1-pcristian292@gmail.com \
    --to=pcristian292@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nbd@nbd.name \
    /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