From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend.vanspriel@broadcom.com>,
Steve deRosier <derosier@gmail.com>,
Sunil Dutt Undekari <usdutt@qti.qualcomm.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Jouni Malinen <jouni@qca.qualcomm.com>,
Amarnath Hullur Subramanyam <amarnath@qti.qualcomm.com>,
Rajesh Chauhan <rajeshc@qti.qualcomm.com>
Subject: Re: Wi-Fi Disconnection on Suspend for no wowlan triggers
Date: Thu, 05 Apr 2018 09:59:32 +0200 [thread overview]
Message-ID: <1522915172.7140.1.camel@sipsolutions.net> (raw)
In-Reply-To: <5AC5D33F.4090100@broadcom.com> (sfid-20180405_094200_504747_90E0C585)
On Thu, 2018-04-05 at 09:41 +0200, Arend van Spriel wrote:
>
> So for a full-mac device or a mac80211 device with certain offloads
> (that we may already have, eg. 4way-hs offloads) you could keep up the
> connection for a while, but if it is receiving data it probably wants to
> wake-up the host at some point. So if such a device has means to do a
> host wake-up you could keep the connection upon suspend. You could
> consider such behavior a wowlan trigger as well and extend that.
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).
johannes
next prev parent reply other threads:[~2018-04-05 7:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 12:39 Wi-Fi Disconnection on Suspend for no wowlan triggers Sunil Dutt Undekari
2018-04-03 16:55 ` Steve deRosier
2018-04-04 6:11 ` Kalle Valo
2018-04-05 7:41 ` Arend van Spriel
2018-04-05 7:59 ` Johannes Berg [this message]
2018-04-05 8:07 ` Arend van Spriel
2018-04-05 11:24 ` Jouni Malinen
2018-04-05 12:42 ` Johannes Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1522915172.7140.1.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=amarnath@qti.qualcomm.com \
--cc=arend.vanspriel@broadcom.com \
--cc=derosier@gmail.com \
--cc=jouni@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rajeshc@qti.qualcomm.com \
--cc=usdutt@qti.qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.