Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Yu Zhang(Yuriy)" <yu.zhang@oss.qualcomm.com>
To: "Paweł Owoc" <frut3k7@gmail.com>
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org,
	quic_yuzha@quicinc.com
Subject: Re: [PATCH] wifi: ath11k: add support for MU EDCA
Date: Sat, 22 Nov 2025 15:55:10 +0800	[thread overview]
Message-ID: <35c554a3-efdd-425c-ac34-858a927bbe15@oss.qualcomm.com> (raw)
In-Reply-To: <CAKEyCaD4=qeQZYYOv4BTrqUJkZa+jnea1b3BL434X1iGMA-_xg@mail.gmail.com>



On 11/21/2025 4:41 PM, Paweł Owoc wrote:
> On Fri, Nov 21, 2025 at 6:00 AM Yu Zhang(Yuriy)
> <yu.zhang@oss.qualcomm.com> wrote:
>>
>> hi,
>>
>>   From your log/calltrace, I didn’t see any errors related to MU EDCA;
>> what I saw were related to SMPS. Did you also add changes related to SMPS?
>>
>> Yuriy
> 
> Hi Yuriy,
> 
> Thanks for your reply. The ath11k driver is version 6.14.12.
> Everything works if I remove the mu_edca setting without any other changes.
> 
> The problem doesn't occur with the newer IPQ8074 firmware, version 2.12-01460,
> which hasn't been publicly released.

So the newer IPQ8074 firmware fixed this issue, great.

> 
> More details: https://github.com/openwrt/openwrt/issues/20702
> 
> Regards,


  reply	other threads:[~2025-11-22  7:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-21  5:00 [PATCH] wifi: ath11k: add support for MU EDCA Yu Zhang(Yuriy)
2025-11-21  8:41 ` Paweł Owoc
2025-11-22  7:55   ` Yu Zhang(Yuriy) [this message]
2025-11-22 10:17     ` Sebastian Gottschall
2025-11-24  1:09       ` Yu Zhang(Yuriy)
2025-11-24  4:35         ` Vasanthakumar Thiagarajan
2025-11-24  8:34           ` Paweł Owoc
2025-12-15 13:30             ` Paweł Owoc
  -- strict thread matches above, loose matches on Subject: below --
2025-11-19  8:09 Paweł Owoc
2025-01-24  6:13 Yu Zhang(Yuriy)
2025-01-31  4:16 ` Vasanthakumar Thiagarajan
2025-02-03 22:49 ` Jeff Johnson

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=35c554a3-efdd-425c-ac34-858a927bbe15@oss.qualcomm.com \
    --to=yu.zhang@oss.qualcomm.com \
    --cc=ath11k@lists.infradead.org \
    --cc=frut3k7@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_yuzha@quicinc.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