From: Ben Greear <greearb@candelatech.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: c_mpubbi@qti.qualcomm.com,
linux-wireless <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCH] ath10k: new debugfs interface to enable adaptive CCA
Date: Thu, 04 Jun 2015 15:11:59 -0700 [thread overview]
Message-ID: <5570CD2F.4040604@candelatech.com> (raw)
In-Reply-To: <CA+BoTQ=480Wg4WmL0eBZ7CS9aVHjH8Lt-2x-FzAuGwsAuNA8-w@mail.gmail.com>
Is there any way to make this work on a 10.1 firmware, even if that means
manually poking registers through debugfs?
I have a user of CT firmware that would really like Adaptive CCA to
work, so if I can just get some clues as to what needs setting,
I can write up an API that works with my 10.1 firmware...
Thanks,
Ben
On 05/10/2015 11:05 PM, Michal Kazior wrote:
> On 8 May 2015 at 16:01, <c_mpubbi@qti.qualcomm.com> wrote:
>> From: Manikanta Pubbisetty <c_mpubbi@qti.qualcomm.com>
>>
>> For devices working in 2.4 GHz to be ETSI compliant,
>> it is required to support adaptive CCA. Some firmwares
>> support adaptive CCA and is disabled by default.
>>
>> The patch is an attempt to add a new debugfs interface to enable
>> adaptive cca on supported firmwares. Support for this feature is
>> advertised with a new firmware feature flag.
>
> I guess this should be configured automatically depending on DFS
> domain. You can't expect users to configure their devices via debugfs,
> can you? This should just work.
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
WARNING: multiple messages have this Message-ID (diff)
From: Ben Greear <greearb@candelatech.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: c_mpubbi@qti.qualcomm.com,
linux-wireless <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCH] ath10k: new debugfs interface to enable adaptive CCA
Date: Thu, 04 Jun 2015 15:11:59 -0700 [thread overview]
Message-ID: <5570CD2F.4040604@candelatech.com> (raw)
In-Reply-To: <CA+BoTQ=480Wg4WmL0eBZ7CS9aVHjH8Lt-2x-FzAuGwsAuNA8-w@mail.gmail.com>
Is there any way to make this work on a 10.1 firmware, even if that means
manually poking registers through debugfs?
I have a user of CT firmware that would really like Adaptive CCA to
work, so if I can just get some clues as to what needs setting,
I can write up an API that works with my 10.1 firmware...
Thanks,
Ben
On 05/10/2015 11:05 PM, Michal Kazior wrote:
> On 8 May 2015 at 16:01, <c_mpubbi@qti.qualcomm.com> wrote:
>> From: Manikanta Pubbisetty <c_mpubbi@qti.qualcomm.com>
>>
>> For devices working in 2.4 GHz to be ETSI compliant,
>> it is required to support adaptive CCA. Some firmwares
>> support adaptive CCA and is disabled by default.
>>
>> The patch is an attempt to add a new debugfs interface to enable
>> adaptive cca on supported firmwares. Support for this feature is
>> advertised with a new firmware feature flag.
>
> I guess this should be configured automatically depending on DFS
> domain. You can't expect users to configure their devices via debugfs,
> can you? This should just work.
--
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
next prev parent reply other threads:[~2015-06-04 22:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 14:01 [PATCH] ath10k: new debugfs interface to enable adaptive CCA c_mpubbi
2015-05-08 14:01 ` c_mpubbi
2015-05-11 6:05 ` Michal Kazior
2015-05-11 6:05 ` Michal Kazior
2015-06-04 22:11 ` Ben Greear [this message]
2015-06-04 22:11 ` Ben Greear
2015-06-08 21:18 ` Ben Greear
2015-06-08 21:18 ` Ben Greear
2015-06-01 23:19 Harvey, Nicholas
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=5570CD2F.4040604@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=c_mpubbi@qti.qualcomm.com \
--cc=linux-wireless@vger.kernel.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 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.