From: Ben Greear <greearb@candelatech.com>
To: Peter Oh <poh@codeaurora.org>,
'Seowoo Jang' <swjang@netlab.snu.ac.kr>,
ath10k@lists.infradead.org
Subject: Re: How to access the CCA related operation
Date: Mon, 24 Aug 2015 11:20:23 -0700 [thread overview]
Message-ID: <55DB6067.6080900@candelatech.com> (raw)
In-Reply-To: <000001d0de92$a6028980$f2079c80$@codeaurora.org>
On 08/24/2015 10:31 AM, Peter Oh wrote:
> There is WMI_10_x_SET_CCA_PARAMS_CMDID which to enable adaptive CCA in
> firmware supported since 10.2.4 and all the actual operations are done in
> firmware with registers as Ben addressed.
> But I'm not clear how much register doc or firmware doc are opened to public
> legally.
We have found no upstream firmware that actually seems to support that SET_CCA_PARAMS,
and I have no idea what that feature actually does since I have no firmware source
that supports that feature.
Thanks,
Ben
>
> Thanks,
> Peter
>
> -----Original Message-----
> From: ath10k [mailto:ath10k-bounces@lists.infradead.org] On Behalf Of Ben
> Greear
> Sent: Monday, August 24, 2015 9:33 AM
> To: Seowoo Jang; ath10k@lists.infradead.org
> Subject: Re: How to access the CCA related operation
>
> It is in firmware, and you cannot reliably poke it through the driver
> read/write register API because each time the radio resets (channel change,
> etc), it is liable to re-write the CCA registers back to default values.
>
> There is a large list of registers with 'CCA' in the name, but I don't know
> what they really mean, and I had hard time getting that info out of QCA. If
> you have any better luck, please post whatever you can share.
>
> Thanks,
> Ben
>
>
> On 08/23/2015 11:21 PM, Seowoo Jang wrote:
>> Hello,
>>
>> We are trying to evaluate our idea on 802.11ac protocol with Atheros
>> qca9880 / ath10k driver.
>>
>> We would like to be able to access/know the result of the CCA (clear
>> channel
>> assessment) operation
>> or the level of interference on the carrier when we need.
>>
>> We have dug into the driver files and concluded that the CCA related
>> values are likely in the firmware or on the registers of the hardware.
>>
>> And please correct us if we are thinking wrong.
>>
>> We would appreciate the help if someone can give us some starting
>> points, such as the address of the register that stores the carrier
>> sensing values (CCA values) or the result of it (whether the carrier
>> is busy or idle), to investigate.
>>
>> The chipset we are using is compex WLE900VX-7AA.
>>
>> We are currently using Ubuntu 14.04.03 with kernel version 4.1.5, but
>> we can use any versions of OS and kernel if they support 802.11ac
>> bandwidth.
>>
>> Thank you for help in advance.
>>
>> -------------------------------
>> Seowoo Jang, Ph.D.
>> Ubiquitous Network Laboratory
>> EECS, Seoul National University
>>
>> CEL +82-10-3723-3401
>> E-mail swjang@netlab.snu.ac.kr
>> -------------------------------
>>
>>
>> _______________________________________________
>> ath10k mailing list
>> ath10k@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/ath10k
>>
>
> --
> 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
>
--
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
prev parent reply other threads:[~2015-08-24 18:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 6:21 How to access the CCA related operation Seowoo Jang
2015-08-24 16:32 ` Ben Greear
2015-08-24 16:35 ` Adrian Chadd
2015-08-24 17:31 ` Peter Oh
2015-08-24 18:20 ` Ben Greear [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=55DB6067.6080900@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=poh@codeaurora.org \
--cc=swjang@netlab.snu.ac.kr \
/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