[PATCH v2] ath10k: fetch (pre-)calibration data via nvmem subsystem

Kalle Valo kvalo at codeaurora.org
Thu Oct 28 01:58:13 PDT 2021

Christian Lamparter <chunkeey at gmail.com> writes:

> ATH10K chips are used it wide range of routers,
> accesspoints, range extenders, network appliances.
> On these embedded devices, calibration data is often
> stored on the main system's flash and was out of reach
> for the driver.
> To bridge this gap, ath10k is getting extended to pull
> the (pre-)calibration data through nvmem subsystem.
> To do this, a nvmem-cell containing the information can
> either be specified in the platform data or via device-tree.
> Tested with:
>         Netgear EX6150v2 (IPQ4018 - pre-calibration method)
>         TP-Link Archer C7 v2 (QCA9880v2 - old calibration method)
> Cc: Robert Marko <robimarko at gmail.com>
> Cc: Thibaut VARÈNE <hacks at slashdirt.org>
> Signed-off-by: Christian Lamparter <chunkeey at gmail.com>
> ---
> v1 -> v2:
> 	- use %zu and %u in the format string for size_t
>           and u32 types (catched by the "kernel test robot").
> 	- reworded commit message + successfully tested on QCA9880v2
> I placed the nvmem code in front of the current "file" method
> (firmware_request). Reason is that this makes it easier for me
> to test it. If needed it can be moved to a different place.

Looks good to me. Before I apply this, I want to mention to that I have
had a long in my deferred queue related two patchsets:



Christian, we don't need those anymore, right? Expect the first patch



More information about the ath10k mailing list