Hi Andrew, On Fri, Oct 26, 2018 at 12:44 AM Andrew Lunn <andrew@xxxxxxx> wrote: > Out of tree is important here. To some degree, mainline does not care > about out of tree drivers. Putting in a bandaid for them does not help > get them fixed. > > I would drop this bandaid. If the Android community decides to move > wireguard from mainline into their fork, they can put the bandaid back > in again, or get the driver fixed. No out-of-tree is really not important here, and sorry if mentioning that in my explanation was distracting and caused you to misunderstand. The issue isn't the crazy wireless driver; the issue is that suspend on Android happens all the time, and the entire Android way of using Linux is centered around non-stop suspending, with triggers to wake up (wifi drivers, for example, like the out-of-tree qcacld one, but presumably in tree ones too), and ways of controlling when it goes to sleep (screen blanking, wakelocks, etc). The Android model of Linux revolves around this, and hence the suspend semantics for WireGuard respect this model and adjust accordingly, using the appropriate CONFIG_ANDROID to determine which model we're operating under. This is not a bandaid, and it doesn't have to do with forks of the Linux kernel. Jason
