aboutsummaryrefslogtreecommitdiffstats
path: root/target
diff options
context:
space:
mode:
authorSven Eckelmann <sven.eckelmann@open-mesh.com>2017-11-30 14:30:06 +0100
committerMatthias Schiffer <mschiffer@universe-factory.net>2018-07-08 23:22:17 +0200
commit6258c965a04498a69e44b9c2173aa98b5ba21283 (patch)
tree392f4b97820abf372a78b93579c7cdb57f5c6f90 /target
parent585208a356849839c3fa2263d82c7087ab1617a3 (diff)
downloadupstream-6258c965a04498a69e44b9c2173aa98b5ba21283.tar.gz
upstream-6258c965a04498a69e44b9c2173aa98b5ba21283.tar.bz2
upstream-6258c965a04498a69e44b9c2173aa98b5ba21283.zip
ath10k-ct: 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> (cherry picked from commit 1c01e02575bd2af96741ba79ed12004fdfb15544)
Diffstat (limited to 'target')
0 files changed, 0 insertions, 0 deletions