On Thu, 2018-04-05 at 11:24 +0000, Jouni Malinen wrote: > > The "any" trigger sounds like a reasonable thing to use, It really depends what you're after. The "any" trigger means you want to wake up on all kinds of things, basically everything that would normally give you an interrupt in regular operation. > so the question > really is on what the default behavior should be if the driver has > capability of doing this and there is no explicit configuration in user > space. Currently, the default behavior seems to be to force > disconnection. Would it make sense to allow drivers to indicate that > they rather use "any" trigger by default? Or make that the default > behavior is the driver supports "any"? I don't think that makes sense, TBH. Imagine how dire that situation would be if you were to have that on your laptop, e.g. with iwlwifi which in certain configurations can support "any" - you'd basically never be able to suspend your system properly unless you disconnected from wifi first! > For example, wpa_supplicant does not currently set any trigger > configuration unless explicitly asked to do so. Which, again, I think is best really. > This in combination with > the kernel default (disconnect) does not seem to result in desired > behavior in number of Android cases. So yeah, I guess I could see how on *Android* in particular you'd want a different configuration - but there are enough ways to configure that on Android systems in particular, whether by changing the wpa_supplicant configuration (if it can do this) or by using libwifihal or similar mechanisms. Basically, I don't think changing it would make sense for a general purpose default configuration - it's always a special case that you do want to wake up on all kinds of wifi things happening. johannes
