From: Kalle Valo <kvalo@codeaurora.org>
To: Rakesh Pillai <pillair@codeaurora.org>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org,
Rakesh Pillai <pillair@codeaurora.org>
Subject: Re: [PATCH v2] ath10k: Use bdf calibration variant for snoc targets
Date: Tue, 22 Sep 2020 07:21:41 +0000 (UTC) [thread overview]
Message-ID: <20200922072141.D65AAC433C8@smtp.codeaurora.org> (raw)
In-Reply-To: <1600157948-2042-1-git-send-email-pillair@codeaurora.org>
Rakesh Pillai <pillair@codeaurora.org> wrote:
> Board Data File (BDF) is loaded upon driver boot-up procedure.
> The right board data file is identified using bus and qmi-board-id.
>
> The problem, however, can occur when the (default) board data
> file cannot fulfill with the vendor requirements and it is
> necessary to use a different board data file.
>
> Also using the chip_id for identifying the board data helps
> in dealing with different variants of the board data file based
> on the RF card. If the chip_id is not programmed, a default value
> of 0xff will be used for parsing the board data file.
>
> Add the support to get the variant field from DTSI and
> use this information along with the chip_id to load the vendor
> specific BDF.
>
> The device tree requires addition strings to define the variant name
>
> wifi@a000000 {
> status = "okay";
> qcom,ath10k-calibration-variant = "xyz-v2";
> };
>
> wifi@a800000 {
> status = "okay";
> qcom,ath10k-calibration-variant = "xyz-v1";
> };
>
> This would create the boarddata identifiers for the board-2.bin search
>
> * bus=snoc,qmi-board-id=16,qmi-chip-id=0,variant=xyz-v1
> * bus=snoc,qmi-board-id=17,qmi-chip-id=0,variant=xyz-v2
>
> Tested-on: WCN3990 hw1.0 SNOC WLAN.HL.3.1-01040-QCAHLSWMTPLZ-1
>
> Signed-off-by: Rakesh Pillai <pillair@codeaurora.org>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Patch applied to ath-next branch of ath.git, thanks.
4e9381056547 ath10k: Use bdf calibration variant for snoc targets
--
https://patchwork.kernel.org/patch/11775827/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2020-09-22 7:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 8:19 [PATCH v2] ath10k: Use bdf calibration variant for snoc targets Rakesh Pillai
2020-09-22 7:21 ` Kalle Valo [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=20200922072141.D65AAC433C8@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pillair@codeaurora.org \
/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