Felix Fietkau wrote:
> ar9002_hw_pa_cal(ah, true);
> + ath9k_hw_start_nfcal(ah, true);
>
> if (ah->caldata)
> set_bit(NFCAL_PENDING, &ah->caldata->cal_flags);
> diff --git a/drivers/net/wireless/ath/ath9k/hw.c b/drivers/net/wireless/ath/ath9k/hw.c
> index 8be4b14..85a7817 100644
> --- a/drivers/net/wireless/ath/ath9k/hw.c
> +++ b/drivers/net/wireless/ath/ath9k/hw.c
> @@ -1953,8 +1953,10 @@ int ath9k_hw_reset(struct ath_hw *ah, struct ath9k_channel *chan,
> if (ath9k_hw_mci_is_enabled(ah))
> ar9003_mci_check_bt(ah);
>
> - ath9k_hw_loadnf(ah, chan);
> - ath9k_hw_start_nfcal(ah, true);
> + if (AR_SREV_9300_20_OR_LATER(ah)) {
> + ath9k_hw_loadnf(ah, chan);
> + ath9k_hw_start_nfcal(ah, true);
> + }
This doesn't seem to load the NF registers for AR9002 ?
If a chip reset is done for some reason when the driver is
operational, don't we have to load the history values ?
Sujith
--
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
