From: Matti Laakso <malaakso@elisanet.fi>
To: ath10k@lists.infradead.org
Subject: Re: Re: fetching calibration data from flash
Date: Tue, 10 Jun 2014 10:36:42 +0200 [thread overview]
Message-ID: <5396C39A.9080402@elisanet.fi> (raw)
In-Reply-To: <5396B9F9.2070107@stackframe.org>
> Hi List,
>
> currently ath10k fetches calibration data from the board.bin file
> via request_firmware(). Usually HW manufactures are using one
> flash partition for the calibration data (see ath9k for example).
> So we would end up reading the file from flash, and writing it into
> a ramdisk so that ath10k can fetch it.
>
> I would prefer to add support to ath10k to fetch that data directly from
> flash. IMHO there are two options to do so:
>
> a) Use platform data, like ath9k does.
>
> b) add a module option to ath10k, and let ath10k fetch the files via mtd
> API.
> Has the downside of requiring MTD (maybe add a config option to
> disable that?),
> but i like that more than the ath9k way of reading an arbitrary
> memory region and
> circumventing the MTD layer.
>
> Any thoughts? I can prepare a patch if needed.
>
> Sven
There's yet another method: Use platform data to provide only a file
name and then use request_firmware to load it from a file under
/lib/firmware. Then it is up to the platform support code to get the
data there. This is used in OpenWrt by rt2x00 drivers.
Matti
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-06-10 8:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 7:55 fetching calibration data from flash Sven Schnelle
2014-06-10 8:28 ` Kalle Valo
2014-06-10 8:32 ` Sven Schnelle
2014-06-10 8:36 ` Matti Laakso [this message]
2014-06-10 8:54 ` Kalle Valo
2014-06-10 8:59 ` Matti Laakso
2014-06-10 9:03 ` Kalle Valo
2014-06-10 15:56 ` Ben Greear
2014-06-11 8:38 ` Kalle Valo
2014-06-11 13:40 ` Ben Greear
2014-06-16 12:24 ` Kalle Valo
2014-06-16 14:53 ` Ben Greear
2014-06-16 15:28 ` Kalle Valo
2014-06-16 15:58 ` Ben Greear
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=5396C39A.9080402@elisanet.fi \
--to=malaakso@elisanet.fi \
--cc=ath10k@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.