Re: [RFC v4 2/2] ath10k: report tx rate using ieee80211_tx_rate_update()

2018-09-28 Thread Peter Oh
On 09/28/2018 12:10 PM, Peter Oh wrote: > > On 09/24/2018 12:10 AM, Anilkumar Kolli wrote: >> diff --git a/drivers/net/wireless/ath/ath10k/htt_rx.c >> b/drivers/net/wireless/ath/ath10k/htt_rx.c >> index f2405258a6d3..355c39a0486c 100644 >> --- a/drivers/net/wireless/ath/ath10k/htt_rx.c >> +++

Re: [RFC v4 2/2] ath10k: report tx rate using ieee80211_tx_rate_update()

2018-09-28 Thread Peter Oh
On 09/24/2018 12:10 AM, Anilkumar Kolli wrote: > diff --git a/drivers/net/wireless/ath/ath10k/htt_rx.c > b/drivers/net/wireless/ath/ath10k/htt_rx.c > index f2405258a6d3..355c39a0486c 100644 > --- a/drivers/net/wireless/ath/ath10k/htt_rx.c > +++ b/drivers/net/wireless/ath/ath10k/htt_rx.c > @@

[RFC v4 2/2] ath10k: report tx rate using ieee80211_tx_rate_update()

2018-09-24 Thread Anilkumar Kolli
Mesh path metric needs tx rate information from ieee80211_tx_status() call but in ath10k there is no mechanism to report tx rate information via ieee80211_tx_status(), the tx rate is only accessible via sta_statiscs() op. Per peer tx stats has tx rate info available, Tx rate is available to