Need to re-associate firmware peer when SMPS_CHANGED is set?

[Adrian Chadd]

Hm! Well, iirc what we did in the rate control code for 11n chips was
just to limit the transmit rate control selection to MCS0-7 even
though we were in 2- or 3- stream modes.

What else is it causing to change?


-a


On 13 September 2015 at 21:58, Ben Greear <greearb at candelatech.com> wrote:
> While digging in 10.1 firmware, I notice that setting WMI_PEER_SMPS_STATE
> can cause
> the chainmask to change.  And, that in turn can change all sorts of things
> related to
> available rates and such.
>
> Maybe we should do a re-assoc when we notice SMPS_CHANGED, similar to how it
> is done for NSS_CHANGED?
>
> Thanks,
> Ben
>
> --
> Ben Greear <greearb at candelatech.com>
> Candela Technologies Inc  http://www.candelatech.com
>
>
> _______________________________________________
> ath10k mailing list
> ath10k at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k