2020-02-02 16:09:50 +00:00
|
|
|
// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
|
|
|
|
|
|
2020-04-28 17:19:48 +00:00
|
|
|
#include "ar9344_teltonika_rut9xx.dtsi"
|
2020-02-02 16:09:50 +00:00
|
|
|
|
|
|
|
|
/ {
|
|
|
|
|
model = "Teltonika RUT955";
|
2020-04-28 17:19:48 +00:00
|
|
|
compatible = "teltonika,rut955", "teltonika,rut9xx", "qca,ar9344";
|
2020-02-02 16:09:50 +00:00
|
|
|
|
|
|
|
|
aliases {
|
|
|
|
|
led-boot = &led_system_green;
|
|
|
|
|
led-failsafe = &led_system_red;
|
|
|
|
|
led-running = &led_system_green;
|
|
|
|
|
led-upgrade = &led_system_red;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
leds {
|
|
|
|
|
compatible = "gpio-leds";
|
|
|
|
|
|
2020-04-28 17:19:48 +00:00
|
|
|
signal0 {
|
ath79: remove model name from LED labels
Currently, we request LED labels in OpenWrt to follow the scheme
modelname:color:function
However, specifying the modelname at the beginning is actually
entirely useless for the devices we support in OpenWrt. On the
contrary, having this part actually introduces inconvenience in
several aspects:
- We need to ensure/check consistency with the DTS compatible
- We have various exceptions where not the model name is used,
but the vendor name (like tp-link), which is hard to track
and justify even for core-developers
- Having model-based components will not allow to share
identical LED definitions in DTSI files
- The inconsistency in what's used for the model part complicates
several scripts, e.g. board.d/01_leds or LED migrations from
ar71xx where this was even more messy
Apart from our needs, upstream has deprecated the label property
entirely and introduced new properties to specify color and
function properties separately. However, the implementation does
not appear to be ready and probably won't become ready and/or
match our requirements in the foreseeable future.
However, the limitation of generic LEDs to color and function
properties follows the same idea pointed out above. Generic LEDs
will get names like "green:status" or "red:indicator" then, and
if a "devicename" is prepended, it will be the one of an internal
device, like "phy1:amber:status".
With this patch, we move into the same direction, and just drop
the boardname from the LED labels. This allows to consolidate
a few definitions in DTSI files (will be much more on ramips),
and to drop a few migrations compared to ar71xx that just changed
the boardname. But mainly, it will liberate us from a completely
useless subject to take care of for device support review and
maintenance.
To also drop the boardname from existing configurations, a simple
migration routine is added unconditionally.
Although this seems unfamiliar at first look, a quick check in kernel
for the arm/arm64 dts files revealed that while 1033 lines have
labels with three parts *:*:*, still 284 actually use a two-part
labelling *:*, and thus is also acceptable and not even rare there.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-09-26 15:31:17 +00:00
|
|
|
label = "green:signal0";
|
2020-04-28 17:19:48 +00:00
|
|
|
gpios = <&gpio_ext 0 GPIO_ACTIVE_HIGH>;
|
|
|
|
|
};
|
|
|
|
|
|
2020-02-02 16:09:50 +00:00
|
|
|
signal1 {
|
ath79: remove model name from LED labels
Currently, we request LED labels in OpenWrt to follow the scheme
modelname:color:function
However, specifying the modelname at the beginning is actually
entirely useless for the devices we support in OpenWrt. On the
contrary, having this part actually introduces inconvenience in
several aspects:
- We need to ensure/check consistency with the DTS compatible
- We have various exceptions where not the model name is used,
but the vendor name (like tp-link), which is hard to track
and justify even for core-developers
- Having model-based components will not allow to share
identical LED definitions in DTSI files
- The inconsistency in what's used for the model part complicates
several scripts, e.g. board.d/01_leds or LED migrations from
ar71xx where this was even more messy
Apart from our needs, upstream has deprecated the label property
entirely and introduced new properties to specify color and
function properties separately. However, the implementation does
not appear to be ready and probably won't become ready and/or
match our requirements in the foreseeable future.
However, the limitation of generic LEDs to color and function
properties follows the same idea pointed out above. Generic LEDs
will get names like "green:status" or "red:indicator" then, and
if a "devicename" is prepended, it will be the one of an internal
device, like "phy1:amber:status".
With this patch, we move into the same direction, and just drop
the boardname from the LED labels. This allows to consolidate
a few definitions in DTSI files (will be much more on ramips),
and to drop a few migrations compared to ar71xx that just changed
the boardname. But mainly, it will liberate us from a completely
useless subject to take care of for device support review and
maintenance.
To also drop the boardname from existing configurations, a simple
migration routine is added unconditionally.
Although this seems unfamiliar at first look, a quick check in kernel
for the arm/arm64 dts files revealed that while 1033 lines have
labels with three parts *:*:*, still 284 actually use a two-part
labelling *:*, and thus is also acceptable and not even rare there.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-09-26 15:31:17 +00:00
|
|
|
label = "green:signal1";
|
2020-04-28 17:19:48 +00:00
|
|
|
gpios = <&gpio_ext 1 GPIO_ACTIVE_HIGH>;
|
2020-02-02 16:09:50 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
signal2 {
|
ath79: remove model name from LED labels
Currently, we request LED labels in OpenWrt to follow the scheme
modelname:color:function
However, specifying the modelname at the beginning is actually
entirely useless for the devices we support in OpenWrt. On the
contrary, having this part actually introduces inconvenience in
several aspects:
- We need to ensure/check consistency with the DTS compatible
- We have various exceptions where not the model name is used,
but the vendor name (like tp-link), which is hard to track
and justify even for core-developers
- Having model-based components will not allow to share
identical LED definitions in DTSI files
- The inconsistency in what's used for the model part complicates
several scripts, e.g. board.d/01_leds or LED migrations from
ar71xx where this was even more messy
Apart from our needs, upstream has deprecated the label property
entirely and introduced new properties to specify color and
function properties separately. However, the implementation does
not appear to be ready and probably won't become ready and/or
match our requirements in the foreseeable future.
However, the limitation of generic LEDs to color and function
properties follows the same idea pointed out above. Generic LEDs
will get names like "green:status" or "red:indicator" then, and
if a "devicename" is prepended, it will be the one of an internal
device, like "phy1:amber:status".
With this patch, we move into the same direction, and just drop
the boardname from the LED labels. This allows to consolidate
a few definitions in DTSI files (will be much more on ramips),
and to drop a few migrations compared to ar71xx that just changed
the boardname. But mainly, it will liberate us from a completely
useless subject to take care of for device support review and
maintenance.
To also drop the boardname from existing configurations, a simple
migration routine is added unconditionally.
Although this seems unfamiliar at first look, a quick check in kernel
for the arm/arm64 dts files revealed that while 1033 lines have
labels with three parts *:*:*, still 284 actually use a two-part
labelling *:*, and thus is also acceptable and not even rare there.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-09-26 15:31:17 +00:00
|
|
|
label = "green:signal2";
|
2020-04-28 17:19:48 +00:00
|
|
|
gpios = <&gpio_ext 2 GPIO_ACTIVE_HIGH>;
|
2020-02-02 16:09:50 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
signal3 {
|
ath79: remove model name from LED labels
Currently, we request LED labels in OpenWrt to follow the scheme
modelname:color:function
However, specifying the modelname at the beginning is actually
entirely useless for the devices we support in OpenWrt. On the
contrary, having this part actually introduces inconvenience in
several aspects:
- We need to ensure/check consistency with the DTS compatible
- We have various exceptions where not the model name is used,
but the vendor name (like tp-link), which is hard to track
and justify even for core-developers
- Having model-based components will not allow to share
identical LED definitions in DTSI files
- The inconsistency in what's used for the model part complicates
several scripts, e.g. board.d/01_leds or LED migrations from
ar71xx where this was even more messy
Apart from our needs, upstream has deprecated the label property
entirely and introduced new properties to specify color and
function properties separately. However, the implementation does
not appear to be ready and probably won't become ready and/or
match our requirements in the foreseeable future.
However, the limitation of generic LEDs to color and function
properties follows the same idea pointed out above. Generic LEDs
will get names like "green:status" or "red:indicator" then, and
if a "devicename" is prepended, it will be the one of an internal
device, like "phy1:amber:status".
With this patch, we move into the same direction, and just drop
the boardname from the LED labels. This allows to consolidate
a few definitions in DTSI files (will be much more on ramips),
and to drop a few migrations compared to ar71xx that just changed
the boardname. But mainly, it will liberate us from a completely
useless subject to take care of for device support review and
maintenance.
To also drop the boardname from existing configurations, a simple
migration routine is added unconditionally.
Although this seems unfamiliar at first look, a quick check in kernel
for the arm/arm64 dts files revealed that while 1033 lines have
labels with three parts *:*:*, still 284 actually use a two-part
labelling *:*, and thus is also acceptable and not even rare there.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-09-26 15:31:17 +00:00
|
|
|
label = "green:signal3";
|
2020-04-28 17:19:48 +00:00
|
|
|
gpios = <&gpio_ext 3 GPIO_ACTIVE_HIGH>;
|
2020-02-02 16:09:50 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
signal4 {
|
ath79: remove model name from LED labels
Currently, we request LED labels in OpenWrt to follow the scheme
modelname:color:function
However, specifying the modelname at the beginning is actually
entirely useless for the devices we support in OpenWrt. On the
contrary, having this part actually introduces inconvenience in
several aspects:
- We need to ensure/check consistency with the DTS compatible
- We have various exceptions where not the model name is used,
but the vendor name (like tp-link), which is hard to track
and justify even for core-developers
- Having model-based components will not allow to share
identical LED definitions in DTSI files
- The inconsistency in what's used for the model part complicates
several scripts, e.g. board.d/01_leds or LED migrations from
ar71xx where this was even more messy
Apart from our needs, upstream has deprecated the label property
entirely and introduced new properties to specify color and
function properties separately. However, the implementation does
not appear to be ready and probably won't become ready and/or
match our requirements in the foreseeable future.
However, the limitation of generic LEDs to color and function
properties follows the same idea pointed out above. Generic LEDs
will get names like "green:status" or "red:indicator" then, and
if a "devicename" is prepended, it will be the one of an internal
device, like "phy1:amber:status".
With this patch, we move into the same direction, and just drop
the boardname from the LED labels. This allows to consolidate
a few definitions in DTSI files (will be much more on ramips),
and to drop a few migrations compared to ar71xx that just changed
the boardname. But mainly, it will liberate us from a completely
useless subject to take care of for device support review and
maintenance.
To also drop the boardname from existing configurations, a simple
migration routine is added unconditionally.
Although this seems unfamiliar at first look, a quick check in kernel
for the arm/arm64 dts files revealed that while 1033 lines have
labels with three parts *:*:*, still 284 actually use a two-part
labelling *:*, and thus is also acceptable and not even rare there.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-09-26 15:31:17 +00:00
|
|
|
label = "green:signal4";
|
2020-02-02 16:09:50 +00:00
|
|
|
gpios = <&gpio_ext 4 GPIO_ACTIVE_HIGH>;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
led_system_red: system_red {
|
ath79: remove model name from LED labels
Currently, we request LED labels in OpenWrt to follow the scheme
modelname:color:function
However, specifying the modelname at the beginning is actually
entirely useless for the devices we support in OpenWrt. On the
contrary, having this part actually introduces inconvenience in
several aspects:
- We need to ensure/check consistency with the DTS compatible
- We have various exceptions where not the model name is used,
but the vendor name (like tp-link), which is hard to track
and justify even for core-developers
- Having model-based components will not allow to share
identical LED definitions in DTSI files
- The inconsistency in what's used for the model part complicates
several scripts, e.g. board.d/01_leds or LED migrations from
ar71xx where this was even more messy
Apart from our needs, upstream has deprecated the label property
entirely and introduced new properties to specify color and
function properties separately. However, the implementation does
not appear to be ready and probably won't become ready and/or
match our requirements in the foreseeable future.
However, the limitation of generic LEDs to color and function
properties follows the same idea pointed out above. Generic LEDs
will get names like "green:status" or "red:indicator" then, and
if a "devicename" is prepended, it will be the one of an internal
device, like "phy1:amber:status".
With this patch, we move into the same direction, and just drop
the boardname from the LED labels. This allows to consolidate
a few definitions in DTSI files (will be much more on ramips),
and to drop a few migrations compared to ar71xx that just changed
the boardname. But mainly, it will liberate us from a completely
useless subject to take care of for device support review and
maintenance.
To also drop the boardname from existing configurations, a simple
migration routine is added unconditionally.
Although this seems unfamiliar at first look, a quick check in kernel
for the arm/arm64 dts files revealed that while 1033 lines have
labels with three parts *:*:*, still 284 actually use a two-part
labelling *:*, and thus is also acceptable and not even rare there.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-09-26 15:31:17 +00:00
|
|
|
label = "red:system";
|
2020-02-02 16:09:50 +00:00
|
|
|
gpios = <&gpio_ext 5 GPIO_ACTIVE_HIGH>;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
led_system_green: system_green {
|
ath79: remove model name from LED labels
Currently, we request LED labels in OpenWrt to follow the scheme
modelname:color:function
However, specifying the modelname at the beginning is actually
entirely useless for the devices we support in OpenWrt. On the
contrary, having this part actually introduces inconvenience in
several aspects:
- We need to ensure/check consistency with the DTS compatible
- We have various exceptions where not the model name is used,
but the vendor name (like tp-link), which is hard to track
and justify even for core-developers
- Having model-based components will not allow to share
identical LED definitions in DTSI files
- The inconsistency in what's used for the model part complicates
several scripts, e.g. board.d/01_leds or LED migrations from
ar71xx where this was even more messy
Apart from our needs, upstream has deprecated the label property
entirely and introduced new properties to specify color and
function properties separately. However, the implementation does
not appear to be ready and probably won't become ready and/or
match our requirements in the foreseeable future.
However, the limitation of generic LEDs to color and function
properties follows the same idea pointed out above. Generic LEDs
will get names like "green:status" or "red:indicator" then, and
if a "devicename" is prepended, it will be the one of an internal
device, like "phy1:amber:status".
With this patch, we move into the same direction, and just drop
the boardname from the LED labels. This allows to consolidate
a few definitions in DTSI files (will be much more on ramips),
and to drop a few migrations compared to ar71xx that just changed
the boardname. But mainly, it will liberate us from a completely
useless subject to take care of for device support review and
maintenance.
To also drop the boardname from existing configurations, a simple
migration routine is added unconditionally.
Although this seems unfamiliar at first look, a quick check in kernel
for the arm/arm64 dts files revealed that while 1033 lines have
labels with three parts *:*:*, still 284 actually use a two-part
labelling *:*, and thus is also acceptable and not even rare there.
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-09-26 15:31:17 +00:00
|
|
|
label = "green:system";
|
2020-02-02 16:09:50 +00:00
|
|
|
gpios = <&gpio_ext 6 GPIO_ACTIVE_HIGH>;
|
|
|
|
|
default-state = "on";
|
|
|
|
|
};
|
|
|
|
|
};
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
&gpio {
|
|
|
|
|
pinctrl-names = "default";
|
|
|
|
|
pinctrl-0 = <&jtag_disable_pins>;
|
|
|
|
|
|
|
|
|
|
gpio-line-names = "RS485_D", "led_wan", "DIN3", "mmc_cs",
|
|
|
|
|
"ext_sck", "", "", "",
|
|
|
|
|
"", "", "", "",
|
|
|
|
|
"ext_mosi", "led_lan2", "led_lan1", "",
|
|
|
|
|
"i2c_scl", "i2c_sda", "", "DIN2",
|
|
|
|
|
"ext_cs", "DIN1", "led_lan3", "",
|
|
|
|
|
"", "", "", "",
|
|
|
|
|
"", "", "", "";
|
|
|
|
|
|
|
|
|
|
ext_sck {
|
|
|
|
|
gpio-hog;
|
|
|
|
|
gpios = <4 GPIO_ACTIVE_HIGH>;
|
|
|
|
|
output-high;
|
|
|
|
|
line-name = "rut955:ext:sck";
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
ext_mosi {
|
|
|
|
|
gpio-hog;
|
|
|
|
|
gpios = <12 GPIO_ACTIVE_HIGH>;
|
|
|
|
|
output-high;
|
|
|
|
|
line-name = "rut955:ext:mosi";
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
ext_cs {
|
|
|
|
|
gpio-hog;
|
|
|
|
|
gpios = <20 GPIO_ACTIVE_HIGH>;
|
|
|
|
|
output-low;
|
|
|
|
|
line-name = "rut955:ext:cs";
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
mmc_cs {
|
|
|
|
|
gpio-hog;
|
|
|
|
|
gpios = <3 GPIO_ACTIVE_HIGH>;
|
|
|
|
|
output-high;
|
|
|
|
|
line-name = "rut955:mmc:cs";
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
uart1_td {
|
|
|
|
|
gpio-hog;
|
|
|
|
|
gpios = <18 GPIO_ACTIVE_HIGH>;
|
|
|
|
|
output-high;
|
|
|
|
|
line-name = "rut955:uart1:td";
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
uart1_rd {
|
|
|
|
|
gpio-hog;
|
|
|
|
|
gpios = <11 GPIO_ACTIVE_LOW>;
|
|
|
|
|
input;
|
|
|
|
|
line-name = "rut955:uart1:rd";
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
led_wan {
|
|
|
|
|
gpio-hog;
|
|
|
|
|
gpios = <1 GPIO_ACTIVE_HIGH>;
|
|
|
|
|
output-high;
|
|
|
|
|
line-name = "rut955:led:wan";
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
led_lan2 {
|
|
|
|
|
gpio-hog;
|
|
|
|
|
gpios = <13 GPIO_ACTIVE_HIGH>;
|
|
|
|
|
output-high;
|
|
|
|
|
line-name = "rut955:led:lan2";
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
led_lan1 {
|
|
|
|
|
gpio-hog;
|
|
|
|
|
gpios = <14 GPIO_ACTIVE_HIGH>;
|
|
|
|
|
output-high;
|
|
|
|
|
line-name = "rut955:led:lan1";
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
led_lan3 {
|
|
|
|
|
gpio-hog;
|
|
|
|
|
gpios = <22 GPIO_ACTIVE_HIGH>;
|
|
|
|
|
output-high;
|
|
|
|
|
line-name = "rut955:led:lan3";
|
|
|
|
|
};
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
&spi {
|
|
|
|
|
status = "okay";
|
|
|
|
|
|
|
|
|
|
pinctrl-names = "default";
|
2020-04-28 17:19:48 +00:00
|
|
|
pinctrl-0 = <&pmx_spi>, <&pmx_spi_ext>;
|
2020-02-02 16:09:50 +00:00
|
|
|
|
|
|
|
|
gpio_ext: gpio_ext@2 {
|
|
|
|
|
compatible = "fairchild,74hc595";
|
|
|
|
|
reg = <2>;
|
|
|
|
|
gpio-controller;
|
|
|
|
|
#gpio-cells = <2>;
|
|
|
|
|
registers-number = <2>;
|
|
|
|
|
spi-max-frequency = <10000000>;
|
2020-04-28 17:19:48 +00:00
|
|
|
gpio-line-names = "signal_bar0", "signal_bar1", "signal_bar2", "signal_bar3",
|
|
|
|
|
"signal_bar4", "status_red", "status_green", "sim_sel",
|
2020-02-02 16:09:50 +00:00
|
|
|
"DOUT1", "DOUT2", "modem_vbus", "modem_rst",
|
|
|
|
|
"DOUT3", "RS485_R", "SDCS", "HWRST";
|
|
|
|
|
};
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
ð0 {
|
|
|
|
|
status = "okay";
|
|
|
|
|
|
|
|
|
|
phy-handle = <&swphy4>;
|
|
|
|
|
|
|
|
|
|
mtd-mac-address = <&config 0x0>;
|
2021-07-12 19:42:41 +00:00
|
|
|
mac-address-increment = <1>;
|
2020-02-02 16:09:50 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
ð1 {
|
|
|
|
|
status = "okay";
|
|
|
|
|
|
|
|
|
|
mtd-mac-address = <&config 0x0>;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
&builtin_switch {
|
|
|
|
|
pinctrl-names = "default";
|
|
|
|
|
pinctrl-0 = <&pmx_leds_switch>;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
&pinmux {
|
2020-04-28 17:19:48 +00:00
|
|
|
pmx_spi_ext: spi_ext {
|
|
|
|
|
// 2nd SCK on GPIO 4, 2nd MOSI on GPIO 12, SPI_CS2 on GPIO 20
|
|
|
|
|
pinctrl-single,bits = <0x4 0x0a 0xff>,
|
2020-02-02 16:09:50 +00:00
|
|
|
<0xc 0x0b 0xff>,
|
|
|
|
|
<0x14 0x08 0xff>;
|
|
|
|
|
};
|
|
|
|
|
};
|
