Re: ath10k: calibration data through Device Tree?
From: Kalle Valo <hidden>
Date: 2014-10-02 13:47:48
Arnd Bergmann [off-list ref] writes:
On Thursday 02 October 2014 16:14:43 Kalle Valo wrote:quoted
Hi Device Tree gurus, 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. Basically our requirements are: * ath10k must support any number of radios (one radio per PCI device). * The calibration data is now 2116 bytes, in the future it might be longer. The data is unique for each radio and is created at the factory. * ath10k must be able to reliably map the PCI device (=radio) to the correct calibration data. Maybe with using PCI bus and slot numbers? We have been trying to find similar cases from other drivers but no luck. Basically my question is how to do this properly with Device Tree? Especially how to map the calibration data to correct PCI device? Are there any examples which would help us to implement this?When you know the PCI bus/device/function ID of the device, you can put a device node in the dts file that corresponds to the PCI dev, and you can find the of_node pointer from pci_dev->dev.of_node.
For me that's easier said than done as I'm a total newbie with Device Tree :) Can you give any pointers or examples how to do that in practise, please? Especially "node in the dts file that corresponds to the PCI dev" part is puzzling me.
2116 is probably ok to put into a DT property of that device directly.
Ok, that's good. -- Kalle Valo -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html