diff options
| author |   Christian Lamparter <chunkeey@gmail.com> | 2021-09-13 15:40:35 +0300 |
|---|---|---|
| committer |   Kalle Valo <kvalo@codeaurora.org> | 2021-09-16 11:07:41 +0300 |
| commit | eb3a97a69be83ea961bf4a164c54e1c989a57850 (patch) | |
| tree | 131094e75bd6c6091a312ff1754c2bfd2945a681 /drivers/net/wireless/ath/ath9k/hw.h | |
| parent | Linux 5.15-rc1 (diff) | |
| download | linux-dev-eb3a97a69be83ea961bf4a164c54e1c989a57850.tar.xz linux-dev-eb3a97a69be83ea961bf4a164c54e1c989a57850.zip | |
ath9k: fetch calibration data via nvmem subsystem
On most embedded ath9k devices (like range extenders,
routers, accesspoints, ...) the calibration data is
stored in a MTD partitions named "ART", or "caldata"/
"calibration".
Since commit 4b361cfa8624 ("mtd: core: add OTP nvmem provider support"):
All MTD partitions are all automatically available through
the nvmem subsystem.
This feature - together with an nvmem cell definition either
in the platform data or via device-tree allows drivers to get
the data necessary for initializing the WIFI, without having
to wait around for the filesystem and userspace to do
the extractions.
Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Link: https://lore.kernel.org/r/f9b732b50a3453fadf3923cc75d365bae3505fe7.1630157099.git.chunkeey@gmail.com
Diffstat (limited to 'drivers/net/wireless/ath/ath9k/hw.h')
| -rw-r--r-- | drivers/net/wireless/ath/ath9k/hw.h | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/drivers/net/wireless/ath/ath9k/hw.h b/drivers/net/wireless/ath/ath9k/hw.h index b7b65b1c90e8..096a206f49ed 100644 --- a/drivers/net/wireless/ath/ath9k/hw.h +++ b/drivers/net/wireless/ath/ath9k/hw.h @@ -977,6 +977,8 @@ struct ath_hw { bool disable_5ghz; const struct firmware *eeprom_blob; + u16 *nvmem_blob; /* devres managed */ + size_t nvmem_blob_len; struct ath_dynack dynack; |