aboutsummaryrefslogtreecommitdiffstats
path: root/package/base-files
diff options
context:
space:
mode:
authorSven Eckelmann <sven.eckelmann@open-mesh.com>2017-11-30 14:30:06 +0100
committerMathias Kresin <dev@kresin.me>2018-01-13 07:58:19 +0100
commitf39fc67c8e975d064616ea3e3e25dea77ca68c80 (patch)
treec0b6489cb4bbcb690f0cfc29f6f71e038a745002 /package/base-files
parent7293499f719d73ffaeb61011d077e84d309b0f25 (diff)
downloadupstream-f39fc67c8e975d064616ea3e3e25dea77ca68c80.tar.gz
upstream-f39fc67c8e975d064616ea3e3e25dea77ca68c80.tar.bz2
upstream-f39fc67c8e975d064616ea3e3e25dea77ca68c80.zip
mac80211: ath10k: search DT for BDF variant info
Board Data File (BDF) is loaded upon driver boot-up procedure. The right board data file is identified on QCA4019 using bus, bmi-chip-id and bmi-board-id. The problem, however, can occur when the (default) board data file cannot fulfill the vendor requirements and it is necessary to use a different board data file. This problem was solved for SMBIOS by adding a special SMBIOS type 0xF8. Something similar has to be provided for systems without SMBIOS but with device trees. No solution was specified by QCA and therefore a new one has to be found for ath10k. The device tree requires addition strings to define the variant name wifi@a000000 { status = "okay"; qcom,ath10k-calibration-variant = "RT-AC58U"; }; wifi@a800000 { status = "okay"; qcom,ath10k-calibration-variant = "RT-AC58U"; }; This would create the boarddata identifiers for the board-2.bin search * bus=ahb,bmi-chip-id=0,bmi-board-id=16,variant=RT-AC58U * bus=ahb,bmi-chip-id=0,bmi-board-id=17,variant=RT-AC58U Signed-off-by: Sven Eckelmann <sven.eckelmann@open-mesh.com>
Diffstat (limited to 'package/base-files')
0 files changed, 0 insertions, 0 deletions