summaryrefslogtreecommitdiff
path: root/Documentation/devicetree/bindings/net/wireless/qcom,ath11k.yaml
diff options
context:
space:
mode:
authorSven Eckelmann <sven@narfation.org>2020-10-15 15:15:00 +0200
committerKalle Valo <kvalo@codeaurora.org>2020-11-07 10:00:54 +0200
commit77581df8639faf28ae52fea170e48cdf9870468a (patch)
tree530f19c4bfadba103444ae0e80576bd5a62d003e /Documentation/devicetree/bindings/net/wireless/qcom,ath11k.yaml
parentbafdbd79aae4c91f38caa43e5fb7abfd911f5bf6 (diff)
dt: bindings: add new dt entry for ath11k calibration variant
The bus + qmi-chip-id + qmi-board-id is not enough to identify the correct board data file on IPQ6018 based devices. Multiple different boards share the same values. Only the original reference designs can currently be identified and loaded from the board-2.bin. But these will not result in the correct calibration data when combined with the pre-calibration data from the device. An additional "variant" information has to be provided to select the correct board data for a design which was modified by an ODM. This follows the same approach as ath10k. Signed-off-by: Sven Eckelmann <sven@narfation.org> Reviewed-by: Rob Herring <robh@kernel.org> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> Link: https://lore.kernel.org/r/20201015131501.1939685-1-sven@narfation.org
Diffstat (limited to 'Documentation/devicetree/bindings/net/wireless/qcom,ath11k.yaml')
-rw-r--r--Documentation/devicetree/bindings/net/wireless/qcom,ath11k.yaml6
1 files changed, 6 insertions, 0 deletions
diff --git a/Documentation/devicetree/bindings/net/wireless/qcom,ath11k.yaml b/Documentation/devicetree/bindings/net/wireless/qcom,ath11k.yaml
index 4b365c9d9378..6af999191559 100644
--- a/Documentation/devicetree/bindings/net/wireless/qcom,ath11k.yaml
+++ b/Documentation/devicetree/bindings/net/wireless/qcom,ath11k.yaml
@@ -144,6 +144,12 @@ properties:
* reg
* reg-names
+ qcom,ath11k-calibration-variant:
+ $ref: /schemas/types.yaml#/definitions/string
+ description:
+ string to uniquely identify variant of the calibration data in the
+ board-2.bin for designs with colliding bus and device specific ids
+
required:
- compatible
- reg