After taking some to checkout the SDIO code code, I see what you're referring to as far as lack of support for suspend/resume. Seems like a pretty big hole to me.
So I'm wondering, does this mean we need to remove the driver prior to suspend and then re-insert it on resume? Otherwise, I don't see how the driver will properly reset itself ( ie. association state, scan tables, RX buffers, etc... ).
Also, since turning on CONFIG_ENABLE_PM causes the driver to fail to build, don't you think we should remove this code?
After taking some to checkout the SDIO code code, I see what you're referring to as far as lack of support for suspend/resume. Seems like a pretty big hole to me.
So I'm wondering, does this mean we need to remove the driver prior to suspend and then re-insert it on resume? Otherwise, I don't see how the driver will properly reset itself ( ie. association state, scan tables, RX buffers, etc... ).
Also, since turning on CONFIG_ENABLE_PM causes the driver to fail to build, don't you think we should remove this code?