I applied these and some other related patches to my hacked-upon 4.0.4, but I am seeing some inconsistencies between how ath10k and ath9k reports survey info. I am using my CT firmware based on 10.1. ath9k reports ever-increasing counters for the channel time and busy time. With ath10k, it reports the same values until I do a scan again, and even then, it is not additive. First, should the value only update when we do a scan? And second, should ath10k report ever increasing totals to match ath9k behaviour? Thanks, Ben On 05/05/2015 05:30 AM, Vasanthakumar Thiagarajan wrote: > Rx clear count reported in wmi_chan_info_event is actually channel_busy_count > not rx_frame_count. Send rx_clear_count through time_busy of survey_info > and set SURVEY_INFO_TIME_BUSY in filled. > > iw wlan0 survey dump > > urvey data from wlan0 > frequency: 5180 MHz [in use] > noise: -103 dBm > channel active time: 150 ms > channel busy time: 22 ms > Survey data from wlan0 > frequency: 5200 MHz > noise: -102 dBm > channel active time: 146 ms > channel busy time: 0 ms > > Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@xxxxxxxxxxxxxxxx> > --- > drivers/net/wireless/ath/ath10k/wmi.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/drivers/net/wireless/ath/ath10k/wmi.c b/drivers/net/wireless/ath/ath10k/wmi.c > index ebaa096..0fabe68 100644 > --- a/drivers/net/wireless/ath/ath10k/wmi.c > +++ b/drivers/net/wireless/ath/ath10k/wmi.c > @@ -1645,10 +1645,10 @@ void ath10k_wmi_event_chan_info(struct ath10k *ar, struct sk_buff *skb) > > survey = &ar->survey[idx]; > survey->time = WMI_CHAN_INFO_MSEC(cycle_count); > - survey->time_rx = WMI_CHAN_INFO_MSEC(rx_clear_count); > + survey->time_busy = WMI_CHAN_INFO_MSEC(rx_clear_count); > survey->noise = noise_floor; > survey->filled = SURVEY_INFO_TIME | > - SURVEY_INFO_TIME_RX | > + SURVEY_INFO_TIME_BUSY | > SURVEY_INFO_NOISE_DBM; > } > > -- Ben Greear <greearb@xxxxxxxxxxxxxxx> Candela Technologies Inc http://www.candelatech.com -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
