2022-03-20 15:42:37 +00:00
|
|
|
// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
|
|
|
|
|
|
|
|
#include "mt7621.dtsi"
|
|
|
|
|
|
|
|
#include <dt-bindings/gpio/gpio.h>
|
|
|
|
#include <dt-bindings/input/input.h>
|
|
|
|
#include <dt-bindings/leds/common.h>
|
|
|
|
|
|
|
|
/ {
|
|
|
|
aliases {
|
|
|
|
led-boot = &led_status_amber;
|
|
|
|
led-failsafe = &led_status_green;
|
|
|
|
led-running = &led_status_green;
|
|
|
|
led-upgrade = &led_status_amber;
|
|
|
|
};
|
|
|
|
|
|
|
|
chosen {
|
|
|
|
bootargs = "console=ttyS0,115200";
|
2022-12-12 11:18:41 +00:00
|
|
|
bootargs-override = "console=ttyS0,115200";
|
2022-03-20 15:42:37 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
keys {
|
|
|
|
compatible = "gpio-keys";
|
|
|
|
|
|
|
|
reset {
|
|
|
|
label = "reset";
|
|
|
|
gpios = <&gpio 13 GPIO_ACTIVE_LOW>;
|
|
|
|
linux,code = <KEY_RESTART>;
|
|
|
|
};
|
|
|
|
|
|
|
|
wps {
|
|
|
|
label = "wps";
|
|
|
|
gpios = <&gpio 14 GPIO_ACTIVE_LOW>;
|
|
|
|
linux,code = <KEY_WPS_BUTTON>;
|
|
|
|
};
|
|
|
|
};
|
|
|
|
|
|
|
|
leds {
|
|
|
|
compatible = "gpio-leds";
|
|
|
|
|
|
|
|
led_status_amber: led-0 {
|
|
|
|
color = <LED_COLOR_ID_AMBER>;
|
|
|
|
function = LED_FUNCTION_STATUS;
|
|
|
|
gpios = <&gpio 15 GPIO_ACTIVE_LOW>;
|
|
|
|
};
|
|
|
|
|
|
|
|
led_status_green: led-1 {
|
|
|
|
color = <LED_COLOR_ID_GREEN>;
|
|
|
|
function = LED_FUNCTION_STATUS;
|
|
|
|
gpios = <&gpio 16 GPIO_ACTIVE_LOW>;
|
|
|
|
};
|
|
|
|
};
|
|
|
|
};
|
|
|
|
|
|
|
|
&gmac1 {
|
|
|
|
status = "okay";
|
|
|
|
label = "wan";
|
|
|
|
phy-handle = <ðphy4>;
|
|
|
|
};
|
|
|
|
|
ramips: mt7621-dts: describe switch PHYs and adjust PHY muxing
Currently, the MT7530 DSA subdriver configures the MT7530 switch to provide
direct access to switch PHYs, meaning, the switch PHYs listen on the MDIO
bus the switch listens on. The PHY muxing feature makes use of this.
This is problematic as the PHY may be attached before the switch is
initialised, in which case, the PHY will fail to be attached.
Since commit 91374ba537bd ("net: dsa: mt7530: support OF-based registration
of switch MDIO bus") on mainline Linux, we can describe the switch PHYs on
the MDIO bus of the switch on the device tree.
When the PHY is described this way, the switch will be initialised first,
then the switch MDIO bus will be registered. Only after these steps, the
PHY will be attached.
Describe the switch PHYs on mt7621.dtsi and remove defining the switch PHY
on the SoC's mdio bus node. When the PHY muxing is in use, the interrupts
for the muxed PHY won't work, therefore delete the "interrupts" property on
the devices where the PHY muxing feature is in use.
Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>
2024-04-28 19:52:51 +00:00
|
|
|
ðphy4 {
|
|
|
|
/delete-property/ interrupts;
|
2022-03-20 15:42:37 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
&nand {
|
|
|
|
status = "okay";
|
|
|
|
|
|
|
|
mediatek,nmbm;
|
|
|
|
mediatek,bmt-max-ratio = <1>;
|
|
|
|
mediatek,bmt-max-reserved-blocks = <64>;
|
|
|
|
mediatek,bmt-remap-range = <0x0000000 0x0a00000>;
|
|
|
|
|
|
|
|
partitions {
|
|
|
|
compatible = "fixed-partitions";
|
|
|
|
#address-cells = <1>;
|
|
|
|
#size-cells = <1>;
|
|
|
|
|
|
|
|
partition@0 {
|
|
|
|
label = "u-boot";
|
|
|
|
reg = <0x0000000 0x0080000>;
|
|
|
|
read-only;
|
|
|
|
};
|
|
|
|
|
|
|
|
partition@80000 {
|
|
|
|
label = "u-boot-env";
|
|
|
|
reg = <0x0080000 0x0080000>;
|
|
|
|
};
|
|
|
|
|
|
|
|
partition@100000 {
|
|
|
|
label = "exp";
|
|
|
|
reg = <0x0100000 0x0080000>;
|
|
|
|
read-only;
|
|
|
|
};
|
|
|
|
|
2024-02-17 14:10:10 +00:00
|
|
|
partition@180000 {
|
2022-03-20 15:42:37 +00:00
|
|
|
label = "factory";
|
|
|
|
reg = <0x0180000 0x0080000>;
|
|
|
|
read-only;
|
2023-10-02 02:12:02 +00:00
|
|
|
|
2023-11-07 23:55:58 +00:00
|
|
|
nvmem-layout {
|
|
|
|
compatible = "fixed-layout";
|
|
|
|
#address-cells = <1>;
|
|
|
|
#size-cells = <1>;
|
|
|
|
|
|
|
|
eeprom_factory_0: eeprom@0 {
|
|
|
|
reg = <0x0 0xe00>;
|
|
|
|
};
|
2023-10-02 02:12:02 +00:00
|
|
|
};
|
2022-03-20 15:42:37 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
partition@200000 {
|
|
|
|
label = "firmware";
|
|
|
|
reg = <0x0200000 0x7600000>;
|
|
|
|
|
|
|
|
compatible = "fixed-partitions";
|
|
|
|
#address-cells = <1>;
|
|
|
|
#size-cells = <1>;
|
|
|
|
|
|
|
|
partition@0 {
|
|
|
|
label = "kernel";
|
|
|
|
reg = <0x0000000 0x0800000>;
|
|
|
|
};
|
|
|
|
|
|
|
|
partition@800000 {
|
|
|
|
label = "ubi";
|
|
|
|
reg = <0x0800000 0x6e00000>;
|
|
|
|
};
|
|
|
|
};
|
|
|
|
|
|
|
|
/* last 8 MiB is reserved for NMBM bad block table */
|
|
|
|
};
|
|
|
|
};
|
|
|
|
|
|
|
|
&pcie {
|
|
|
|
status = "okay";
|
|
|
|
};
|
|
|
|
|
|
|
|
&pcie1 {
|
|
|
|
wifi@0,0 {
|
|
|
|
compatible = "mediatek,mt76";
|
|
|
|
reg = <0x0000 0 0 0 0>;
|
2023-10-02 02:12:02 +00:00
|
|
|
nvmem-cells = <&eeprom_factory_0>;
|
|
|
|
nvmem-cell-names = "eeprom";
|
2022-03-20 15:42:37 +00:00
|
|
|
mediatek,disable-radar-background;
|
|
|
|
};
|
|
|
|
};
|
|
|
|
|
2022-12-12 11:18:41 +00:00
|
|
|
&state_default {
|
|
|
|
gpio {
|
|
|
|
groups = "jtag";
|
|
|
|
function = "gpio";
|
|
|
|
};
|
|
|
|
};
|
|
|
|
|
2022-03-20 15:42:37 +00:00
|
|
|
&switch0 {
|
|
|
|
ports {
|
|
|
|
port@1 {
|
|
|
|
status = "okay";
|
|
|
|
label = "lan1";
|
|
|
|
};
|
|
|
|
|
|
|
|
port@2 {
|
|
|
|
status = "okay";
|
|
|
|
label = "lan2";
|
|
|
|
};
|
|
|
|
|
|
|
|
port@3 {
|
|
|
|
status = "okay";
|
|
|
|
label = "lan3";
|
|
|
|
};
|
|
|
|
};
|
|
|
|
};
|
|
|
|
|
|
|
|
&xhci {
|
|
|
|
status = "disabled";
|
|
|
|
};
|