On Tue, Oct 12, 2010 at 10:50 AM, Nicolas Pitre <nico@xxxxxxxxxxx> wrote: > On Tue, 12 Oct 2010, Dmitry Shmidt wrote: > >> MMC_PM_KEEP_POWER is mostly related to mmc host controller - keeping >> or not keeping power on suspend/resume. > > It is not "mostly related", it is _totally_ related and actually its > purpose for existing. Sorry, I tried to be polite... :) > >> MMC_PM_WAKE_SDIO_IRQ is not related to anything right now. Also in >> most of the cases sdio irq can not be a wake source of the application >> processor. > > Why not? I know about at least 2 host controllers which can be > configured so a transition on DAT3 would wake up the host. Sorry, that I was not clear - wake source is not related to the topic. > >> Imagine your device is keeping connection during suspend. You got packet - >> wlan will wake application processor >> through external irq line and linux starts resume. You can not find wlan >> card again - it is too slow. > > What? I'm not following you anymore. > > The Libertas firmware can be configured to filter incoming packets and > only assert the IRQ signal only when a specific packet comes in, just > like wake-on-LAN for Ethernet devices. This is not an issue of the ability to handle packets, but to handle them quickly. This is important for VoIP for example. If you need to recognize device each time you are coming from suspend - it is not a good idea sometimes. >> Again, for mmc card it totally makes sense - mmc card is NOT an active >> device. > > But MMC cards still have operating states. You cannot simply write to > them after a power disconnect, and leaving them powered on suspend is > not very efficient either. Agree 100% > PS: common netiquette is not to top-post. > > > Nicolas > Thanks, Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
