All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nicolas Escande" <nico.escande@gmail.com>
To: "Jeff Johnson" <quic_jjohnson@quicinc.com>,
	<ath11k@lists.infradead.org>, <ath12k@lists.infradead.org>
Cc: "Kalle Valo" <kvalo@kernel.org>
Subject: Re: ath12k & ath11k beacon miss detection
Date: Fri, 23 Feb 2024 09:39:13 +0100	[thread overview]
Message-ID: <CZCBN3MIGKZS.2DZMAGUD4RS59@gmail.com> (raw)
In-Reply-To: <a35eca5b-e6e6-46e8-85b5-dbcbda0d2f04@quicinc.com>

On Wed Feb 21, 2024 at 1:46 AM CET, Jeff Johnson wrote:
[...]
>
> The ath12k driver is still work-in-progress and there is quite a bit of
> functionality missing there due to the refactoring to handle 802.11be
> Multi-Link Operation. However I'm surprised that ath11k has this issue.
> I've asked the development team to look at this. It would be helpful for
> you to open a bug to track the issue. Please see
> <https://wireless.wiki.kernel.org/en/users/drivers/ath11k/bugreport>.

Yeah I fugured as much for ath12k so I thought I try to do as it was done in
ath11k and that's how I found out it wasn't working either there.

Thanks for having your guys looking into it, in the mean time here is a link to
the bug report on buzilla https://bugzilla.kernel.org/show_bug.cgi?id=218522

I'll be happy to test anything you can throw at me on this

> Thanks!
> /jeff


  reply	other threads:[~2024-02-23  8:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-20 17:11 ath12k & ath11k beacon miss detection Nicolas Escande
2024-02-21  0:46 ` Jeff Johnson
2024-02-23  8:39   ` Nicolas Escande [this message]
2024-03-15 10:06   ` Nicolas Escande
2024-03-15 19:55     ` Jeff Johnson
2024-03-18  8:33       ` Nicolas Escande
2025-01-09 16:46       ` Nicolas Escande
2024-02-21  7:02 ` Kalle Valo
2024-02-23  8:42   ` Nicolas Escande
2024-02-23 10:17     ` Kalle Valo

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=CZCBN3MIGKZS.2DZMAGUD4RS59@gmail.com \
    --to=nico.escande@gmail.com \
    --cc=ath11k@lists.infradead.org \
    --cc=ath12k@lists.infradead.org \
    --cc=kvalo@kernel.org \
    --cc=quic_jjohnson@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.