From: Brian Norris <briannorris@chromium.org>
To: Ben Greear <greearb@candelatech.com>
Cc: ath10k@lists.infradead.org
Subject: Re: ath10k: antenna bitmask support?
Date: Tue, 7 Aug 2018 10:52:57 -0700 [thread overview]
Message-ID: <20180807175255.GA163107@ban.mtv.corp.google.com> (raw)
In-Reply-To: <6dbb4086-f5bd-2ece-e3f3-9ac7cd5b4d9c@candelatech.com>
Hi Ben,
On Tue, Aug 07, 2018 at 06:19:22AM -0700, Ben Greear wrote:
> On 08/06/2018 07:08 PM, Brian Norris wrote:
> > Hi all,
> >
> > I'm looking at ancient changes like this:
> >
> > commit 5572a95b4b5768187652a346356e39e7542ca6e0
> > Author: Ben Greear <greearb@candelatech.com>
> > Date: Mon Nov 24 16:22:10 2014 +0200
> >
> > ath10k: apply chainmask settings to vdev on creation
> >
> > since I see that some firmwares seem to crash a lot if you apply certain
> > chainmask settings (e.g., 0x2).
> >
> > Is it really expected that you can set gaps in the chainmask or not? I
> > ask because I've been trying to use this for doing some antenna
> > configuration verification (e.g., disable all but one antenna and see
> > what happens), and this works as expected on APs I have running IPQ8064
> > (QCA988X?), but it crashes the firmware on IPQ4019.
>
> I don't think you can even directly set the chainmask in the firmware,
Well, I guess the WMI interface is a bit strange then: it appears to
take a raw mask -- e.g.:
ret = ath10k_wmi_pdev_set_param(ar, ar->wmi.pdev_param->tx_chain_mask,
tx_ant);
but I guess that doesn't mean it *really* accepts a mask? You have to
presuppose what values it will accept?
> and from my previous looking at the firmware, it is not designed to support
> gaps.
OK, thanks for the info.
> If you want to determine if an antenna is working, you can look at the per-chain
> RSSI stats when receiving frames using all available antenna (ie, 3x3 rates for a 3x3 NIC).
That's not quite the same as verifying each antenna separately, but it
might be good enough. I suppose this wasn't really considered when some
of the test frameworks I'm using were written, seeing as per-chain
signal reports weren't even available in ath10k until relatively
recently:
commit 8241253d03fe9098e98315a4d66027ae31ab65c5
Author: Norik Dzhandzhapanyan <norikd@gmail.com>
Date: Mon Jun 12 18:03:34 2017 +0300
ath10k: add per chain RSSI reporting
Thanks,
Brian
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2018-08-07 17:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 2:08 ath10k: antenna bitmask support? Brian Norris
2018-08-07 4:11 ` Sebastian Gottschall
2018-08-07 5:01 ` Brian Norris
2018-08-07 7:22 ` Sebastian Gottschall
2018-08-07 18:01 ` Brian Norris
2018-08-07 13:19 ` Ben Greear
2018-08-07 17:52 ` Brian Norris [this message]
2018-08-07 18:18 ` Ben Greear
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=20180807175255.GA163107@ban.mtv.corp.google.com \
--to=briannorris@chromium.org \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.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