On Tue, Oct 12, 2010 at 12:36 PM, Nicolas Pitre <nico@xxxxxxxxxxx> wrote: > On Tue, 12 Oct 2010, Dmitry Shmidt wrote: > >> On Tue, Oct 12, 2010 at 11:13 AM, Nicolas Pitre <nico@xxxxxxxxxxx> wrote: >> > On Tue, 12 Oct 2010, Dmitry Shmidt wrote: >> > >> >> On Tue, Oct 12, 2010 at 10:50 AM, Nicolas Pitre <nico@xxxxxxxxxxx> wrote: >> >> >> 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. >> > >> > I simply don't see why you'd want to suspend while a VoIP session is >> > active then. Those methods you want to inhibit are meant for long term >> > deep suspending, not for inter-packet power saving during a call. >> >> You are right - there are other ways to resolve some issues. I just >> wanted to add another option >> that will be kernel-related and not application-related. > > Even for a kernel related solution, I don't think what you propose is > the right thing to do. I am open for suggestions. > > 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
