From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: ath10k <ath10k@lists.infradead.org>, Avery Pennarun <apenwarr@gmail.com>
Subject: Re: Support for scan while in AP mode, and offchannel while in AP mode
Date: Tue, 19 Aug 2014 09:30:42 +0300 [thread overview]
Message-ID: <87siktat4d.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CA+BoTQ=Qcrrutt6ZUtbrgKzx0Mo9186SRuV7dc97FnOxwn3Jxg@mail.gmail.com> (Michal Kazior's message of "Tue, 19 Aug 2014 08:24:03 +0200")
Michal Kazior <michal.kazior@tieto.com> writes:
> On 19 August 2014 08:07, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>> Avery Pennarun <apenwarr@gmail.com> writes:
>>
>>>>> Are there any plans to implement this feature? It's important in
>>>>> order to implement automatic channel change in case of changes in the
>>>>> interference environment.
>>>>
>>>> No plans at the moment. Does anyone know how much work would it be to
>>>> change mac80211 to support this with hw_scan?
>>>
>>> Is there any particular reason it can't just resort to a sw_scan for
>>> this use case? What's the benefit of hw_scan? I'm surprised there
>>> would be any particular CPU time taken for such a thing.
>>
>> For mobile devices hw_scan is important because the ability to allow the
>> host CPU to sleep while scanning. For others I'm not that sure, maybe
>> firmware can do timing better (less intrusive) than host based sw
>> scanning?
>
> sw_scan requires a driver to be able to "just change the channel".
> Some device firmwares have no direct control over programmed hw
> channel. Instead they have start/join/connect commands that implicitly
> setup hw channel. ath10k is actually like that, isn't it (vdev start)?
Yes, my understanding as well is that the ath10k firmware is like that.
But I'm no firmware expert :)
I assume that the 10.x firmware does support hw_scan when in AP mode and
we would need to "just" change mac80211 to support that. But no idea how
big task that actually is.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-08-19 6:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 2:26 Support for scan while in AP mode, and offchannel while in AP mode Avery Pennarun
2014-08-19 5:50 ` Kalle Valo
2014-08-19 5:56 ` Avery Pennarun
2014-08-19 6:07 ` Kalle Valo
2014-08-19 6:24 ` Michal Kazior
2014-08-19 6:30 ` Kalle Valo [this message]
2014-08-19 7:01 ` Michal Kazior
2014-08-27 6:46 ` Avery Pennarun
2014-08-27 6:55 ` Michal Kazior
2014-08-27 7:41 ` Avery Pennarun
2014-08-19 15:23 ` Adrian Chadd
2014-08-19 21:46 ` Avery Pennarun
2014-08-19 21:56 ` Adrian Chadd
2014-08-19 22:01 ` Avery Pennarun
2014-08-19 6:19 ` Michal Kazior
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=87siktat4d.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=apenwarr@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=michal.kazior@tieto.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