On 05/25/2012 10:44 PM, Seth Forshee wrote: > Before. I printed the value from bcma_host_pci_resume(). > > I can easily make a patch that fixes the chipctl register up as needed > during resume to fix my problem. But based on the fact that other fields > in the register are also changing value, I'm wondering if more thorough > handling is needed for the register. Ok. I dived into b43 and it does disable the wireless core in the .stop() callback. So I believe it does reinitialize the device when .start() callback is being called after resume. So I think you should check the chipctl register at the end of the .start() callback. > And I'm also a little fuzzy on > exactly who should be responsible for what in the relationship between > b43 and the wireless drivers. I assume you mean bcma instead of b43, right? I admit it is a bit shady, because bcma is more than just a bus driver. It also contains drivers for the chipcommon and pcie cores on the device. Gr. AvS -- 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
