[PATCH 1/2] ath10k: introduce rx_status htt template

[Janusz Dziedzic]

On 24 March 2014 11:06, Kalle Valo <kvalo at qca.qualcomm.com> wrote:
> Janusz Dziedzic <janusz.dziedzic at tieto.com> writes:
>
>> Introduce rx_status htt template instead of
>> stack version.
>>
>> Signed-off-by: Janusz Dziedzic <janusz.dziedzic at tieto.com>
>
> Why? What's the benefit from doing this?
>
This is the must in case we would like to report rssi + rates correctly.
I describe this in 2/2 - maybe squash them?
Currently during heavy traffic we could have:
> 10 packets with START_VALID - correct RSSI + rates
> 10 packets with END_VALID
> 10 packets with START_VALID - correct RSSI + rates
> 10 packets with END_VALID -
...

Because of that we have to store rssi + rates for case when END_VALID only.
In other case when using monitor we will see:
- 10 packets with correct rssi/rates
- 10 packets with rssi=-95/rate=6Mbps

BR
Janusz