On 2012-09-13 6:51 PM, Simon Wunderlich wrote: > ath9k fellows, > > as it seems no one could find the cause for this problem so far. I'd therefore > like to create a workaround by checking one/some registers for 0xdeadbeef and > reset the chip if this is found. > > Can anyone recommend a register which should never go 0xdeadbeef in a normal case? > > From what i've seen, AR_CFG (0x0014) might be a good choice. My regdumps say: > > bad regdump: 0x000014 0xdeadbeef > good regdump: 0x000014 0x0008010a > > Unfortunately I don't have documentation to find out if this register can ever > go deadbeef in a normal case. :) > > What do you think? (of course, a proper solution is still appreciated ...) If ah->power_mode == ATH9K_PM_AWAKE, then no regularly used register may return 0xdeadbeef. You can use a combination of the register and the power mode as an indicator. - Felix -- 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
