Arnd Bergmann <arnd@xxxxxxxx> writes: > On Thursday 27 November 2014 14:08:56 Kalle Valo wrote: >> diff --git a/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt b/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt >> new file mode 100644 >> index 000000000000..edefc26c6204 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt >> @@ -0,0 +1,30 @@ >> +* Qualcomm Atheros ath10k wireless devices >> + >> +For ath10k devices the calibration data can be provided through Device >> +Tree. The node is a child node of the PCI controller. >> + >> +Required properties: >> +-compatible : Should be "qcom,ath10k" >> + >> +Optional properties: >> +- qcom,ath10k-calibration-data : calibration data as an array, the >> + length can vary between hw versions >> + > > Does the device always have a valid mac address in hardware? If not, > how about listing that as well using the mac-address property? Right now ath10k does not support that, but in the future we might want to add mac address as well. We need to do some testing with the firmware to make sure that we can safely change the "main" address from ath10k. And because of Virtual AP (mBSSID) feature we actually would need to provide multiple addresses, not just one. Maybe with addr_mask like struct wiphy has? * @perm_addr: permanent MAC address of this device * @addr_mask: If the device supports multiple MAC addresses by masking, * set this to a mask with variable bits set to 1, e.g. if the last * four bits are variable then set it to 00-00-00-00-00-0f. The actual * variable bits shall be determined by the interfaces added, with * interfaces not matching the mask being rejected to be brought up. /* permanent MAC address(es) */ u8 perm_addr[ETH_ALEN]; u8 addr_mask[ETH_ALEN]; -- Kalle Valo -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
