fetching calibration data from flash

Sven Schnelle svens at stackframe.org
Tue Jun 10 01:32:25 PDT 2014

Am 10.06.2014 10:28, schrieb Kalle Valo:
> Sven Schnelle <svens at stackframe.org> writes:
>> 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.
> I prefer this option.
>> 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?)
> This sounds like a hack to me. How to specify the exact location? Are we
> sure devices will only use MTD to store the calibration data?
>> but i like that more than the ath9k way of reading an arbitrary memory
>> region and circumventing the MTD layer.
> Sorry, I didn't quite understand this comment. What do you mean exactly
> with an arbitrary region? The memory location should be defined by the
> platform data from which ath10k just copies data to the target.

Ok, let's do the first option. Ignore that comment - i'm fine with using 
platform data.


More information about the ath10k mailing list