635f111148
In ath79, for several SoCs the console bootargs are defined to the very same value in every device's DTS. Consolidate these definitions in the SoC dtsi files and drop further redundant definitions elsewhere. The only device without any bootargs set has been OpenMesh OM5P-AC V2. This will now inherit the setting from qca955x.dtsi Note that while this tidies up master a lot, it might develop into a frequent pitfall for backports. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
183 lines
3.1 KiB
Plaintext
183 lines
3.1 KiB
Plaintext
// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
|
|
/dts-v1/;
|
|
|
|
#include <dt-bindings/gpio/gpio.h>
|
|
#include <dt-bindings/input/input.h>
|
|
|
|
#include "ar7100.dtsi"
|
|
|
|
/ {
|
|
compatible = "siemens,ws-ap3610", "qca,ar7161";
|
|
model = "Siemens WS-AP3610";
|
|
|
|
aliases {
|
|
led-boot = &led_power_green;
|
|
led-failsafe = &led_power_red;
|
|
led-running = &led_power_green;
|
|
led-upgrade = &led_power_red;
|
|
label-mac-device = ð0;
|
|
};
|
|
|
|
extosc: ref {
|
|
compatible = "fixed-clock";
|
|
#clock-cells = <0>;
|
|
clock-output-names = "ref";
|
|
clock-frequency = <40000000>;
|
|
};
|
|
|
|
leds {
|
|
compatible = "gpio-leds";
|
|
|
|
led_power_green: led_power_green {
|
|
label = "ws-ap3610:green:power";
|
|
gpios = <&gpio 7 GPIO_ACTIVE_LOW>;
|
|
};
|
|
|
|
led_power_red: led_power_red {
|
|
label = "ws-ap3610:red:power";
|
|
gpios = <&gpio 8 GPIO_ACTIVE_LOW>;
|
|
};
|
|
|
|
led_wlan5_blue {
|
|
label = "ws-ap3610:blue:wlan5";
|
|
gpios = <&gpio 2 GPIO_ACTIVE_LOW>;
|
|
linux,default-trigger = "phy0tpt";
|
|
};
|
|
|
|
led_wlan5_green {
|
|
label = "ws-ap3610:green:wlan5";
|
|
gpios = <&gpio 3 GPIO_ACTIVE_LOW>;
|
|
};
|
|
|
|
led_wlan2_blue {
|
|
label = "ws-ap3610:blue:wlan2";
|
|
gpios = <&gpio 4 GPIO_ACTIVE_LOW>;
|
|
linux,default-trigger = "phy1tpt";
|
|
};
|
|
|
|
led_wlan2_green {
|
|
label = "ws-ap3610:green:wlan2";
|
|
gpios = <&gpio 5 GPIO_ACTIVE_LOW>;
|
|
};
|
|
};
|
|
|
|
keys {
|
|
compatible = "gpio-keys";
|
|
|
|
reset {
|
|
label = "reset";
|
|
linux,code = <KEY_RESTART>;
|
|
gpios = <&gpio 11 GPIO_ACTIVE_LOW>;
|
|
};
|
|
};
|
|
};
|
|
|
|
&pcie0 {
|
|
status = "okay";
|
|
};
|
|
|
|
&uart {
|
|
status = "okay";
|
|
};
|
|
|
|
&mdio0 {
|
|
status = "okay";
|
|
|
|
phy0: ethernet-phy@0 {
|
|
/*
|
|
* When the compatible-is missing, PHY autodetection
|
|
* is performed, but the PHY-ID reads all 0xff.
|
|
*
|
|
* Linux does not create the device in this case,
|
|
* and the reset is never even de-asserted.
|
|
*/
|
|
compatible = "ethernet-phy-id0143.bca2",
|
|
"ethernet-phy-ieee802.3-c22";
|
|
reg = <0>;
|
|
|
|
resets = <&rst 8>;
|
|
reset-names = "phy";
|
|
reset-assert-us = <10000>;
|
|
reset-deassert-us = <10000>;
|
|
};
|
|
};
|
|
|
|
ð0 {
|
|
status = "okay";
|
|
|
|
phy-mode = "rgmii-id";
|
|
phy-handle = <&phy0>;
|
|
};
|
|
|
|
&spi {
|
|
status = "okay";
|
|
|
|
num-cs = <1>;
|
|
|
|
flash@0 {
|
|
compatible = "jedec,spi-nor";
|
|
reg = <0>;
|
|
spi-max-frequency = <25000000>;
|
|
|
|
partitions {
|
|
compatible = "fixed-partitions";
|
|
#address-cells = <1>;
|
|
#size-cells = <1>;
|
|
|
|
partition@0 {
|
|
label = "u-boot";
|
|
reg = <0x0 0x40000>;
|
|
read-only;
|
|
};
|
|
|
|
partition@40000 {
|
|
label = "u-boot-bak";
|
|
reg = <0x40000 0x40000>;
|
|
read-only;
|
|
};
|
|
|
|
partition@80000 {
|
|
compatible = "denx,uimage";
|
|
label = "firmware";
|
|
reg = <0x80000 0xe00000>;
|
|
};
|
|
|
|
partition@e80000 {
|
|
label = "cfg1";
|
|
reg = <0xe80000 0x40000>;
|
|
read-only;
|
|
};
|
|
|
|
partition@ec0000 {
|
|
label = "cfg2";
|
|
reg = <0xec0000 0x40000>;
|
|
read-only;
|
|
};
|
|
|
|
partition@f00000 {
|
|
label = "nvram1";
|
|
reg = <0xf00000 0x40000>;
|
|
read-only;
|
|
};
|
|
|
|
partition@f40000 {
|
|
label = "nvram2";
|
|
reg = <0xf40000 0x40000>;
|
|
read-only;
|
|
};
|
|
|
|
partition@f80000 {
|
|
label = "rsvd1";
|
|
reg = <0xf80000 0x40000>;
|
|
read-only;
|
|
};
|
|
|
|
partition@fc0000 {
|
|
label = "rsvd2";
|
|
reg = <0xfc0000 0x40000>;
|
|
read-only;
|
|
};
|
|
};
|
|
};
|
|
};
|