It is possible that BDF name with board-id+chip-id+variant combination is not found in the board-2.bin. Such cases can cause wlan probe to fail and completely break wifi. In such case there can be an optional property to define a default BDF name to search for in the board-2.bin file when none of the combinations (board-id,chip-id,variant) match. To address the above concern provide an optional proptery: qcom,ath10k-default-bdf Signed-off-by: Abhishek Kumar <kuabhs@xxxxxxxxxxxx> --- Changes in v2: - Changes in v2: none .../devicetree/bindings/net/wireless/qcom,ath10k.txt | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt b/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt index b61c2d5a0ff7..d76d1392863d 100644 --- a/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt +++ b/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt @@ -63,6 +63,10 @@ Optional properties: hw versions. - qcom,ath10k-pre-calibration-data : pre calibration data as an array, the length can vary between hw versions. +- qcom,ath10k-default-bdf : default board data file name to be searched in + board-2.bin. This is searched if no BDF is found + in board-2.bin that matches, chip-id, board-id and + variant combination - <supply-name>-supply: handle to the regulator device tree node optional "supply-name" are "vdd-0.8-cx-mx", "vdd-1.8-xo", "vdd-1.3-rfa", "vdd-3.3-ch0", -- 2.34.1.575.g55b058a8bb-goog