From: Kalle Valo <kvalo@codeaurora.org>
To: Christian Lamparter <chunkeey@gmail.com>
Cc: linux-wireless@vger.kernel.org, ath9k-devel@qca.qualcomm.com
Subject: Re: [PATCH v1 1/2] ath9k: fetch calibration data via nvmem subsystem
Date: Thu, 16 Sep 2021 08:08:14 +0000 (UTC) [thread overview]
Message-ID: <20210916080814.00CDBC4360C@smtp.codeaurora.org> (raw)
In-Reply-To: <f9b732b50a3453fadf3923cc75d365bae3505fe7.1630157099.git.chunkeey@gmail.com>
Christian Lamparter <chunkeey@gmail.com> wrote:
> 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>
2 patches applied to ath-next branch of ath.git, thanks.
eb3a97a69be8 ath9k: fetch calibration data via nvmem subsystem
ef7bc2a76342 ath9k: owl-loader: fetch pci init values through nvmem
--
https://patchwork.kernel.org/project/linux-wireless/patch/f9b732b50a3453fadf3923cc75d365bae3505fe7.1630157099.git.chunkeey@gmail.com/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2021-09-16 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-28 13:27 [PATCH v1 1/2] ath9k: fetch calibration data via nvmem subsystem Christian Lamparter
2021-08-28 13:27 ` [PATCH v1 2/2] ath9k: owl-loader: fetch pci init values through nvmem Christian Lamparter
2021-09-16 8:08 ` 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=20210916080814.00CDBC4360C@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=chunkeey@gmail.com \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).