openwrtv3/target/linux/ramips/dts/AWM002.dtsi
John Crispin 1a392636a5 ramips: use consistent naming scheme for LEDs
The upstream LED naming convention is "device:color:led-name", but it seems that many of supported boards in OpenWrt don't follow this approach.
The following patch fixes this inconsistency in dts{,i} files and updates base-files scripts for ramips target:
 * fixes wrong indentation
 * keeps case statements structure in same convention as in other scripts (no empty line after ";;", no indentation for case...esac body)
 * fixes wrong LED names for some of boards (makes them the same as in dts{,i} files)
 * combines boards with same configuration (ex. set_wifi_led "rt2800pci-phy0::radio" in 01_leds)

Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>

SVN-Revision: 46664
2015-08-17 06:24:34 +00:00

77 lines
1.1 KiB
Text

/include/ "rt5350.dtsi"
/ {
compatible = "AWM002", "ralink,rt5350-soc";
model = "AsiaRF AWM002";
palmbus@10000000 {
spi@b00 {
status = "okay";
m25p80@0 {
#address-cells = <1>;
#size-cells = <1>;
reg = <0 0>;
spi-max-frequency = <10000000>;
partition@0 {
label = "u-boot";
reg = <0x0 0x30000>;
read-only;
};
partition@30000 {
label = "u-boot-env";
reg = <0x30000 0x10000>;
read-only;
};
factory: partition@40000 {
label = "factory";
reg = <0x40000 0x10000>;
read-only;
};
partition@50000 {
label = "firmware";
reg = <0x50000 0x1fb0000>;
};
};
};
};
pinctrl {
state_default: pinctrl0 {
gpio {
ralink,group = "i2c", "jtag";
ralink,function = "gpio";
};
};
};
esw@10110000 {
ralink,portmap = <0x3f>;
};
ehci@101c0000 {
status = "okay";
};
ohci@101c1000 {
status = "okay";
};
gpio-leds {
compatible = "gpio-leds";
ld1 {
label = "awm002:green:ld1";
gpios = <&gpio0 0 1>;
};
ld2 {
label = "awm002:green:ld2";
gpios = <&gpio0 1 1>;
};
};
};