Hello,
This is a special BDF for 5 GHz radio inside ALFA Network AP120C-AC [0].
In case of 2.4 GHz radio, BDF used by the vendor firmware is the same as
the one already embedded in the upstream board-2.bin file:
root@AP120C-AC:/# dmesg | grep -i board
[ 32.198686] Board extended Data
you mentioned yesterday that the called should own the right lock.
doesnt that apply to ath10k as well? i dont see a lock here and you
still calling txq_return
Sebastian
Am 22.01.2019 um 15:20 schrieb Toke Høiland-Jørgensen:
From: Toke Høiland-Jørgensen
ath10k maintains common txqs list
Toke Høiland-Jørgensen writes:
> Since we reworked ieee80211_return_txq() so it assumes that the caller
> takes care of logging, we need another function that can be called without
> holding any locks. Introduce ieee80211_schedule_txq() which serves this
> purpose.
Hmm, messed up the version
From: Toke Høiland-Jørgensen
This moves the ath9k driver to use the mac80211 TXQ scheduling and
airtime accounting APIs, removing the corresponding state tracking
inside the driver.
Signed-off-by: Toke Høiland-Jørgensen
[rmano...@codeaurora.org: fixed checkpatch error and warnings]
From: Toke Høiland-Jørgensen
ath10k maintains common txqs list for all stations. This txq
management can be removed by migrating to mac80211 txq APIs
and let mac80211 handle txqs reordering based on reported airtime.
By doing this, txq fairness maintained in ath10k i.e processing
N frames per
From: Kan Yan
Transmit airtime will be estimated from last tx rate used.
Firmware report tx rate by peer stats. Airtime is computed
on tx path and the same will be reported to mac80211 upon
tx completion.
This change is based on Kan's orginal commit in Chromium tree
("CHROMIUM: ath10k:
This is an updated resend of the driver part of the previous patch set
that moves airtime fairness scheduling into mac80211 and enables it for
ath10k as well.
This version is just a refresh of the driver code, along with a small
fix for the issue I noticed yesterday where ath9k was calling
