dt-bindings: ath10k: Add wifi-firmware subnode for wifi node
Add a wifi-firmware subnode for the wifi node. This wifi-firmware subnode is needed for the targets which do not support TrustZone. Signed-off-by: Rakesh Pillai <pillair@codeaurora.org> Acked-by: Rob Herring <robh@kernel.org> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> Link: https://lore.kernel.org/r/1586971906-20985-2-git-send-email-pillair@codeaurora.org
This commit is contained in:
parent
d431f8939c
commit
85325c24d5
|
@ -96,6 +96,17 @@ Optional properties:
|
||||||
- qcom,coexist-gpio-pin : gpio pin number information to support coex
|
- qcom,coexist-gpio-pin : gpio pin number information to support coex
|
||||||
which will be used by wifi firmware.
|
which will be used by wifi firmware.
|
||||||
|
|
||||||
|
* Subnodes
|
||||||
|
The ath10k wifi node can contain one optional firmware subnode.
|
||||||
|
Firmware subnode is needed when the platform does not have TustZone.
|
||||||
|
The firmware subnode must have:
|
||||||
|
|
||||||
|
- iommus:
|
||||||
|
Usage: required
|
||||||
|
Value type: <prop-encoded-array>
|
||||||
|
Definition: A list of phandle and IOMMU specifier pairs.
|
||||||
|
|
||||||
|
|
||||||
Example (to supply PCI based wifi block details):
|
Example (to supply PCI based wifi block details):
|
||||||
|
|
||||||
In this example, the node is defined as child node of the PCI controller.
|
In this example, the node is defined as child node of the PCI controller.
|
||||||
|
@ -196,4 +207,7 @@ wifi@18000000 {
|
||||||
memory-region = <&wifi_msa_mem>;
|
memory-region = <&wifi_msa_mem>;
|
||||||
iommus = <&apps_smmu 0x0040 0x1>;
|
iommus = <&apps_smmu 0x0040 0x1>;
|
||||||
qcom,msa-fixed-perm;
|
qcom,msa-fixed-perm;
|
||||||
|
wifi-firmware {
|
||||||
|
iommus = <&apps_iommu 0xc22 0x1>;
|
||||||
|
};
|
||||||
};
|
};
|
||||||
|
|
Loading…
Reference in New Issue