Christian Lamparter <chunkeey@xxxxxxxxx> 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@xxxxxxxxx> > Cc: Thibaut VARÈNE <hacks@xxxxxxxxxxxxx> > Signed-off-by: Christian Lamparter <chunkeey@xxxxxxxxx> > --- > > 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: https://patchwork.kernel.org/project/linux-wireless/patch/20200927192515.86-1-ansuelsmth@xxxxxxxxx/ https://patchwork.kernel.org/project/linux-wireless/patch/20200927192515.86-2-ansuelsmth@xxxxxxxxx/ https://patchwork.kernel.org/project/linux-wireless/patch/20200918181104.98-1-ansuelsmth@xxxxxxxxx/ https://patchwork.kernel.org/project/linux-wireless/patch/20200918181104.98-2-ansuelsmth@xxxxxxxxx/ Christian, we don't need those anymore, right? Expect the first patch maybe. -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
