Add documentation how devicetree can be used to configure ath9k based devices.
Signed-off-by: Martin Blumenstingl <martin.blumensti...@googlemail.com> --- .../devicetree/bindings/net/wireless/ath,ath9k.txt | 40 ++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 Documentation/devicetree/bindings/net/wireless/ath,ath9k.txt diff --git a/Documentation/devicetree/bindings/net/wireless/ath,ath9k.txt b/Documentation/devicetree/bindings/net/wireless/ath,ath9k.txt new file mode 100644 index 0000000..d6f5471 --- /dev/null +++ b/Documentation/devicetree/bindings/net/wireless/ath,ath9k.txt @@ -0,0 +1,40 @@ +* Atheros ath9k wireless devices + +This node provides properties for configuring the ath9k wireless device. The +node is expected to be specified as a child node of the PCI controller to +which the wireless chip is connected. + +Required properties: +- compatible: Should be "ath,ath9k" + +Optional properties: +- reg: Address and length of the register set for the device. +- ath,gpio-mask: The GPIO mask +- ath,gpio-val: The GPIO value +- ath,led-pin: The GPIO number to which the LED is connected +- ath,led-active-high: The LED is active when the GPIO is HIGH +- ath,clk-25mhz: Defines that at 25MHz clock is used +- ath,eeprom-name: The name of the file which contains the EEPROM data (which + will be loaded via request_firmware) +- ath,check-eeprom-endianness: Allow checking the EEPROM endianness and + swapping of the EEPROM data if required +- ath,disable-2ghz: Disables the 2.4GHz band, even if enabled in the EEPROM +- ath,disable-5ghz: Disables the 5GHz band, even if enabled in the EEPROM + +In this example, the node is defined as child node of the PCI controller. + +pci { + pcie@0 { + reg = <0 0 0 0 0>; + #interrupt-cells = <1>; + #size-cells = <2>; + #address-cells = <3>; + device_type = "pci"; + + ath9k@0,0 { + reg = <0 0 0 0 0>; + device_type = "pci"; + ath,disable-5ghz; + }; + }; +}; -- 2.9.0 -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html