Rakesh Pillai <pillair@xxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxx>
> Signed-off-by: Kalle Valo <kvalo@xxxxxxxxxxxxxx>
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
