Linux wireless drivers development
 help / color / mirror / Atom feed
From: Salah Ahmed <haddad2inc@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] wifi: mac80211: make the phy tpt LED indicate real traffic
Date: Sat, 31 Oct 2026 00:59:35 +0300	[thread overview]
Message-ID: <20261030215937.18103-1-haddad2inc@gmail.com> (raw)

An access point's phy throughput LED currently counts frames that are never
delivered to any local interface, and keeps blinking on the broadcast an idle AP
bridges, so it cannot answer the only question a user asks of it: is anything
actually being transferred?

Patch 1 counts the trigger from delivered data only, moving the RX accounting
past BSS/interface matching in the rx path. Patch 2 keeps the LED resting in its
baseline state below a small idle threshold, so the residual broadcast of a
zero-client AP no longer produces the slowest blink step forever.

Both were exercised on ath9k (QCA9563) and ath10k (QCA9888) access points,
including a zero-client idle-solid battery and a link-flap battery over several
weeks of production uptime.

Salah Ahmed (2):
  wifi: mac80211: count the tpt LED trigger from delivered data only
  wifi: mac80211: keep the tpt LED solid below an idle threshold

 net/mac80211/led.c | 16 ++++++++++++++++
 net/mac80211/rx.c  |  7 ++-----
 2 files changed, 18 insertions(+), 5 deletions(-)

-- 
2.53.0


             reply	other threads:[~2026-10-30 21:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30 21:59 Salah Ahmed [this message]
2026-10-30 21:59 ` [PATCH 1/2] wifi: mac80211: count the tpt LED trigger from delivered data only Salah Ahmed
2026-10-30 21:59 ` [PATCH 2/2] wifi: mac80211: keep the tpt LED solid below an idle threshold Salah Ahmed

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=20261030215937.18103-1-haddad2inc@gmail.com \
    --to=haddad2inc@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    /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