All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Sujith Manoharan <sujith@msujith.org>, Adrian Chadd <adrian@freebsd.org>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: Question on beacon-miss handling.
Date: Sun, 06 Jul 2014 01:54:09 -0700	[thread overview]
Message-ID: <53B90EB1.8020305@candelatech.com> (raw)
In-Reply-To: <21432.58953.39322.640936@gargle.gargle.HOWL>

On 07/05/2014 11:01 PM, Sujith Manoharan wrote:
> Adrian Chadd wrote:
>> Think about it in terms of "minimising how much the host is woken up."
>>
>> That's what the target market of the STA firmware for this chip is
>> thinking about.
>
> I don't think beacon filtering is enabled for ath10k, which means
> all beacons are sent to mac80211 anyway. HW/FW connection monitoring
> (in STA mode) is also not enabled in ath10k, so mac80211's beacon loss/miss
> infrastructure is already used, no ?

Maybe the driver should make this 0 instead of 2 then?

hw.h:#define TARGET_10X_BMISS_OFFLOAD_MAX_VDEV	2

That would save resources in the firmware.

Thanks,
Ben

>
> Sujith
>


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  parent reply	other threads:[~2014-07-06  8:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-05 14:16 Question on beacon-miss handling Ben Greear
2014-07-06  2:14 ` Adrian Chadd
2014-07-06  3:39   ` Ben Greear
2014-07-06  4:39     ` Adrian Chadd
2014-07-06  6:01       ` Sujith Manoharan
2014-07-06  7:18         ` Adrian Chadd
2014-07-06  8:54         ` Ben Greear [this message]
2014-07-07  3:37           ` Sujith Manoharan
2014-07-07  4:35             ` Ben Greear
2014-07-07  6:57             ` Bartosz Markowski

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=53B90EB1.8020305@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=adrian@freebsd.org \
    --cc=ath10k@lists.infradead.org \
    --cc=sujith@msujith.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 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.