From: Sven Eckelmann <sven.eckelmann@openmesh.com>
To: ath10k@lists.infradead.org
Cc: Dongming Han <workspace4hdm@gmail.com>
Subject: Re: ath10k-firmware: QCA4019 hw1.0: Add GL.iNet GL-B1300 specific BDFs
Date: Tue, 27 Mar 2018 09:19:19 +0200 [thread overview]
Message-ID: <2037513.gUX94vxXhd@bentobox> (raw)
In-Reply-To: <CAEYLdSij6gAAmG2+MQmfGD-m4tOi3O-h0HNmQutwrdQb_iG3Gg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 866 bytes --]
On Dienstag, 27. März 2018 14:48:05 CEST Dongming Han wrote:
> I think the ART data is made based on BDF. Maybe the antCtrlCommon logic
> and target power parameter is passed to driver by ART but not BDF?
> That way we're all happier no need to mantain these change. Please advise.
The antCtrlCommon is part of biModalHeader and this one is taken from the BDF
and not from the pre-cal data (ART). Same is true for the target power limits.
I am only aware of following things which are taken from the pre-cal data
(ART):
* mac
* hal_cal version info
* custData
* regDmn
* txrxMask
* calFreqPier*
* calPierData*
* rxGainCalTbl
* param_for_tuning_caps*
Of course, also the bmi ids are taken from the ART before you load the correct
BDF from the board-2.bin (otherwise, the chip would not know what it actually
is).
Kind regards,
Sven
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 146 bytes --]
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2018-03-27 7:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 6:48 ath10k-firmware: QCA4019 hw1.0: Add GL.iNet GL-B1300 specific BDFs Dongming Han
2018-03-27 7:19 ` Sven Eckelmann [this message]
2018-03-28 6:23 ` Sebastian Gottschall
2018-03-28 7:42 ` Sven Eckelmann
2018-04-19 14:40 ` Kalle Valo
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=2037513.gUX94vxXhd@bentobox \
--to=sven.eckelmann@openmesh.com \
--cc=ath10k@lists.infradead.org \
--cc=workspace4hdm@gmail.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