From: Johannes Berg <johannes@sipsolutions.net>
To: Paul Stewart <pstew@chromium.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Luca Coelho <luca@coelho.fi>
Subject: Re: [PATCHv2] nl80211: Provide TDLS link state
Date: Thu, 22 May 2014 08:56:48 +0200 [thread overview]
Message-ID: <1400741808.4174.5.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CAMcMvsh-zKuNgMSyo73VmsEUkM9YnhVtkg_Vigdter0QarJ6_g@mail.gmail.com> (sfid-20140521_221907_003160_C6CF738D)
On Wed, 2014-05-21 at 13:19 -0700, Paul Stewart wrote:
> > Is it really that bad to demand the firmware notify the host? It's not
> > like this is a very frequent event, and if querying is supported then
> > notification can't be all that much more difficult.
>
> I think firmware vendors are coming to the point of view that they
> must minimize host processor wakeups. They may argue from that
> perspective that the firmware should divulge such information only on
> request.
That's reasonable, but the request could also be "list all TDLS peers
please", right? Then you could still implement it very easily. It
doesn't have to be an event.
johannes
prev parent reply other threads:[~2014-05-22 6:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 20:27 [PATCH] nl80211: Provide TDLS link state Paul Stewart
2014-05-20 21:54 ` Luca Coelho
2014-05-20 20:27 ` [PATCHv2] " Paul Stewart
2014-05-21 10:41 ` Johannes Berg
2014-05-21 16:17 ` Paul Stewart
2014-05-21 19:59 ` Johannes Berg
2014-05-21 20:19 ` Paul Stewart
2014-05-22 6:56 ` Johannes Berg [this message]
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=1400741808.4174.5.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=luca@coelho.fi \
--cc=pstew@chromium.org \
/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