From: Johannes Berg <johannes@sipsolutions.net>
To: Bob Copeland <me@bobcopeland.com>
Cc: Dan Williams <dcbw@redhat.com>,
Marcel Holtmann <marcel@holtmann.org>,
linux-wireless@vger.kernel.org, mabbaswireless@gmail.com
Subject: Re: [PATCH v2 0/3] mac80211 suspend/resume
Date: Tue, 06 Jan 2009 19:16:20 +0100 [thread overview]
Message-ID: <1231265780.3654.13.camel@johannes> (raw)
In-Reply-To: <20090106174830.M95524@bobcopeland.com> (sfid-20090106_190313_967720_5D5E0C7C)
[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]
On Tue, 2009-01-06 at 13:01 -0500, Bob Copeland wrote:
> On Tue, 06 Jan 2009 18:43:22 +0100, Johannes Berg wrote
> > We should probably take the rtnl anyway though to be prepared for when
> > userspace is not suspended.. Need to think about that more though, and
> > possibly add a new "suspended" flag that makes it block all
> > configuration attempts.
>
> Well, luckily we do take the rtnl already, wiphy_suspend() and _resume()
> do that around the cfg ops.
Good point.
> IMHO a suspended flag would be extra complexity that we should just
> hold off on until the freezer really is getting removed.
Well, kinda a chicken-and-egg problem here, can't remove the freezer
without looking at all this, but yeah, we can defer that and put it on
the todo list.
> For now is there anything besides driver support we need to do for this
> patchset? I guess that the drivers will actually be OK as-is too unless
> there are any that do release_firmware in ->stop(), but it will be nice
> to clean them up.
I don't see anything, drivers need to do at all. They should all be fine
with suspending when hw is stopped anyway. We can remove some driver
code though.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-01-06 18:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 3:50 [PATCH v2 0/3] mac80211 suspend/resume Bob Copeland
2008-12-15 10:14 ` Johannes Berg
2008-12-15 15:22 ` Dan Williams
2008-12-15 9:28 ` Luis R. Rodriguez
2008-12-17 18:21 ` Bob Copeland
2008-12-23 20:30 ` Johannes Berg
2008-12-24 5:49 ` Bob Copeland
2008-12-24 7:16 ` Marcel Holtmann
2009-01-06 16:45 ` Dan Williams
2009-01-06 17:07 ` Bob Copeland
2009-01-06 17:14 ` Johannes Berg
2009-01-06 17:35 ` Bob Copeland
2009-01-06 17:43 ` Johannes Berg
2009-01-06 18:01 ` Bob Copeland
2009-01-06 18:16 ` Johannes Berg [this message]
2009-01-06 17:12 ` Marcel Holtmann
2009-01-06 18:52 ` Dan Williams
2009-01-06 19:36 ` Marcel Holtmann
2009-01-06 20:05 ` Johannes Berg
2009-01-09 23:53 ` Tomas Winkler
2009-01-10 9:27 ` Johannes Berg
2009-01-11 11:11 ` Tomas Winkler
2009-01-11 14:40 ` Bob Copeland
2009-01-08 16:39 ` Dan Williams
2009-01-09 7:55 ` Kalle Valo
2009-01-09 16:35 ` Dan Williams
2009-01-09 16:44 ` Kalle Valo
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=1231265780.3654.13.camel@johannes \
--to=johannes@sipsolutions.net \
--cc=dcbw@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mabbaswireless@gmail.com \
--cc=marcel@holtmann.org \
--cc=me@bobcopeland.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).