ath10k: calibration data through Device Tree?
luto at amacapital.net
Thu Oct 2 12:35:09 PDT 2014
On Thu, Oct 2, 2014 at 12:28 PM, Adrian Chadd <adrian at freebsd.org> wrote:
> On 2 October 2014 12:05, Andy Lutomirski <luto at amacapital.net> wrote:
>> On 10/02/2014 06:44 AM, Kalle Valo wrote:
>>> Hi Mark,
>>> Mark Rutland <mark.rutland-5wv7dgnIgG8 at public.gmane.org> writes:
>>>>> ath10k is a wireless driver for Qualcomm Atheros 802.11ac hardware and
>>>>> located in drivers/net/wireless/ath/ath10k/. Currently it only supports
>>>>> PCI devices.
>>>>> Some of the devices store the calibration data to the host flash and the
>>>>> bootloader reads the data from the flash. And now we need a method to
>>>>> deliver the calibration data from bootloader to ath10k.
>>>> What does this calibration data consist of?
>>> From ath10k point of view it's just a binary blob which we push to the
>>> firmware before we start it. ath10k does not parse it in any way.
>>>> What happens if you don't have the calibration data? Is it a critical
>>>> requirement for the use of the device, or does its absence simply result
>>>> in degraded performance?
>>> From my point of view the device should not be used if it doesn't
>>> contain the correct calibration data. I guess it could work somehow but
>>> there's no guarantee about the perfomance.
>>>> What do you do on non-DT systems? Where does the information come from
>>>> in that case?
>>> Currently ath10k only supports having the calibration data in the OTP
>>> area inside the QCA98XX chip. But some manufacturers want to store it on
>>> the host file, I assume because of the flexibility it provides. And
>>> that's why we have the need for Device Tree support.
>> To give an actual concrete example that might be what Kalle is talking
>> I have a TP-Link Archer C7, which has a mips cpu and an ath10k minipcie
>> device. For whatever reason (I honestly have no clue whatsoever why the
>> hardware works this way), the calibration data is on a host flash
>> partition, not on the minipcie device's ROM or flash or whatever it is.
> The hardware works this way because it's what's being chosen at
> manufacturing time.
> It _used_ to be this way because then the manufacturers could choose
> whether to put the serial EEPROM on the wireless card or on board - or
> just save that particular component and load in the same data from the
> existing SPI flash chip that holds the firmware.
> With OTP they'd have to include writing OTP data out to the chip as
> part of the manufacturing process, rather than just "load in data via
> JTAG or uboot".
I always assumed that vendors like TP-Link bought pre-calibrated
minipcie cards from someone else. I guess I was wrong :)
> It also means they can re-do the calibration or configuration space
> for the device rather than the "One Time Programmable" bits which (a)
> will eventually run out of space for programming, (b) occasionally may
> error during programming, or (c) may end up writing the wrong data
> during programming time, making a chip or a whole batch of chips
>> Needless to say, the mainline ath10k driver won't load on it. (An old
>> version used to load without calibration data. It didn't work very well.)
> I'm surprised it worked at all. :)
My gf's Macbook didn't think it worked. My supremely crappy old Intel
card thought it did, at least as well as it thought that anything
worked. Go figure.
Perhaps unsurprisingly, the OpenWRT patch that enables it to work for
real (by shoving a file into /lib/firmware that's contains a copy of
data read from flash) hasn't made it upstream. I assume that the
purpose of this discussion is to settle on a real solution.
More information about the ath10k