Hi Felix,
On Sat, Mar 3, 2012 at 7:47 PM, Felix Fietkau <nbd@xxxxxxxxxxx> wrote:
> Cold reset is more reliable for getting the hardware out of some specific
> stuck states.
>
> Signed-off-by: Felix Fietkau <nbd@xxxxxxxxxxx>
> ---
> drivers/net/wireless/ath/ath9k/hw.c | 14 ++++++++++----
> 1 files changed, 10 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath9k/hw.c b/drivers/net/wireless/ath/ath9k/hw.c
> index 8c840ca..d582cf7 100644
> --- a/drivers/net/wireless/ath/ath9k/hw.c
> +++ b/drivers/net/wireless/ath/ath9k/hw.c
> @@ -1386,10 +1386,16 @@ static bool ath9k_hw_set_reset_reg(struct ath_hw *ah, u32 type)
> static bool ath9k_hw_chip_reset(struct ath_hw *ah,
> struct ath9k_channel *chan)
> {
> - if (AR_SREV_9280(ah) && ah->eep_ops->get_eeprom(ah, EEP_OL_PWRCTRL)) {
> - if (!ath9k_hw_set_reset_reg(ah, ATH9K_RESET_POWER_ON))
> - return false;
> - } else if (!ath9k_hw_set_reset_reg(ah, ATH9K_RESET_WARM))
> + int reset_type = ATH9K_RESET_WARM;
> +
> + if (AR_SREV_9280(ah)) {
> + if (ah->eep_ops->get_eeprom(ah, EEP_OL_PWRCTRL))
> + reset_type = ATH9K_RESET_POWER_ON;
> + else
> + reset_type = ATH9K_RESET_COLD;
> + }
cold reset seems to be applicable for older chip sets like AR9100,
should this be applicable to AR9280. won't there be any problem if we
perform cold reset in STA mode.
> +
> + if (!ath9k_hw_set_reset_reg(ah, reset_type))
> return false;
>
> if (!ath9k_hw_setpower(ah, ATH9K_PM_AWAKE))
> --
> 1.7.3.2
>
> --
> 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
--
thanks,
shafi
--
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
