Until now it was okay to use a very generic board data since OTP was supposed to fill in the blanks (except some cases in which a complete cal data is provided via cal-pci-xxx or device tree). However since qca6174 this has changed. It is now necessary to load specific board file for different designs in driver. The OTP must still be run. Some devices with different subsystem vendor/device ids may share the same board file. Driver could maintain a subsystem vendor/device id to design id however I prefer to just leave this to userspace (e.g. symlinks). Thoughts? Michal Kazior (2): ath10k: share board file loading code across FW APIs ath10k: allow loading device specific board files drivers/net/wireless/ath/ath10k/core.c | 109 +++++++++++++++++++++----------- drivers/net/wireless/ath/ath10k/core.h | 3 + drivers/net/wireless/ath/ath10k/debug.c | 6 +- drivers/net/wireless/ath/ath10k/pci.c | 5 ++ 4 files changed, 84 insertions(+), 39 deletions(-) -- 2.1.4 -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
