On Thu, Apr 05, 2018 at 10:07:04AM +0200, Arend van Spriel wrote: > On 4/5/2018 9:59 AM, Johannes Berg wrote: > >There's the "any" trigger that might be appropriate for that, or a > >"disconnect" trigger. > > > >But I'm basically thinking the same as Steve - if you're never going to > >wake up the host, there's not really much point in keeping the > >connection, and if you only suspend briefly like e.g. on Android then > >you probably *do* want to wake up the host for pretty much everything > >that's going on (hence the "any" trigger). > > Agree, which is why I suggested to look at wowlan triggers. If we already > have an appropriate "any" trigger even better ;-)
The "any" trigger sounds like a reasonable thing to use, 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"? For example, wpa_supplicant does not currently set any trigger configuration unless explicitly asked to do so. This in combination with the kernel default (disconnect) does not seem to result in desired behavior in number of Android cases. And if the default behavior should be changed, should that behavior change be done in the kernel or user space (wpa_supplicant)? -- Jouni Malinen PGP id EFC895FA
