Hi Greg, Kalle Valo <kvalo@xxxxxxxxxxxxxxxx> writes: > The current suspend code in ath6kl is not working properly. Most of the > time during response there are sdio errors and sdio stack reloads the > driver. > > I was pondering different options how to fix this and decided to take > the simplest route. First remove all the existing suspend/resume code > which was complicated and replace it with code which will leave > the chip powered on but will put it to deep sleep state. Now suspend > works much faster and realiably, the cost being that power consumption > will increase a bit during suspend. With ath6kl-cleanup we missed the 3.1 deadline for the wireless code so the staging version of ath6kl will be still in 3.1. Because of this I need to send few critical fixes for 3.1, this suspend fix being one of them. There are might few others as well, but the patches are not ready yet. I'm doing the big mistake of sending new code and going for a trip the next day and not have internet access for 10 days. If there are any issues my collagues will jump in. -- Kalle Valo -- 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
