From: "Arınç ÜNAL" <arinc.unal@arinc9.com>
To: Liviu Dudau <liviu@dudau.co.uk>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Paul Burton <paulburton@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Sergio Paracuellos <sergio.paracuellos@gmail.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH] mips: dts: ralink: Add support for TP-Link HC220 G5 v1 board.
Date: Thu, 11 May 2023 15:41:30 +0200 [thread overview]
Message-ID: <43301707-8763-2a9f-956d-1ea0ae004a56@arinc9.com> (raw)
In-Reply-To: <20230509200125.309026-1-liviu@dudau.co.uk>
On 9.05.2023 22:01, Liviu Dudau wrote:
> This WiFi AP is based on a MT7621 SoC with 128MiB RAM, 128MiB NAND,
> a MT7603 2.4GHz WiFi and a MT7663 5GHz WiFi chips integrated on the board,
> connected to the main SoC over PCIe.
>
> The GMAC1 on the SoC is connected to PHY0 on the GSW and can be used to
> improve routing bandwidth.
>
> The device uses NMBM over NAND, which is not currently supported in the
> mainline, so NAND node is skipped in this revision.
>
> Signed-off-by: Liviu Dudau <liviu@dudau.co.uk>
This is great to see. I'm going to mainline all the MT7621 devicetrees
on OpenWrt at some point, this is a good step for this.
> ---
> arch/mips/boot/dts/ralink/Makefile | 3 +-
> .../dts/ralink/mt7621-tplink-hc220_g5.dts | 126 ++++++++++++++++++
> 2 files changed, 128 insertions(+), 1 deletion(-)
> create mode 100644 arch/mips/boot/dts/ralink/mt7621-tplink-hc220_g5.dts
>
> diff --git a/arch/mips/boot/dts/ralink/Makefile b/arch/mips/boot/dts/ralink/Makefile
> index 11732b8c8163a..c57a2b40876b4 100644
> --- a/arch/mips/boot/dts/ralink/Makefile
> +++ b/arch/mips/boot/dts/ralink/Makefile
> @@ -8,6 +8,7 @@ dtb-$(CONFIG_DTB_VOCORE2) += vocore2.dtb
>
> dtb-$(CONFIG_SOC_MT7621) += \
> mt7621-gnubee-gb-pc1.dtb \
> - mt7621-gnubee-gb-pc2.dtb
> + mt7621-gnubee-gb-pc2.dtb \
> + mt7621-tplink-hc220_g5.dtb
>
> obj-$(CONFIG_BUILTIN_DTB) += $(addsuffix .o, $(dtb-y))
> diff --git a/arch/mips/boot/dts/ralink/mt7621-tplink-hc220_g5.dts b/arch/mips/boot/dts/ralink/mt7621-tplink-hc220_g5.dts
> new file mode 100644
> index 0000000000000..83d15711907d0
> --- /dev/null
> +++ b/arch/mips/boot/dts/ralink/mt7621-tplink-hc220_g5.dts
> @@ -0,0 +1,126 @@
> +// SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +/dts-v1/;
> +
> +#include "mt7621.dtsi"
> +
> +#include <dt-bindings/gpio/gpio.h>
> +#include <dt-bindings/input/input.h>
> +#include <dt-bindings/leds/common.h>
> +
> +/ {
> + compatible = "tplink,hc220-g5", "mediatek,mt7621-soc";
tplink,hc220-g5-v1 should fit better. Also please make another patch to
add the compatible string under Boards with Mediatek/Ralink MT7621 SoC
on Documentation/devicetree/bindings/mips/ralink.yaml.
> + model = "TP-Link HC220 G5 v1.0";
"TP-Link HC220 G5 v1" should be enough.
> +
> + memory@0 {
> + device_type = "memory";
> + reg = <0x0 0x0 0x0 0x8000000>;
> + };
> +
> + chosen {
> + /* bootargs = "earlycon=uart8260,mmio32,0x1e000c00 root=/dev/ram0 kgdboc=ttyS0,115200 ip=192.168.88.1:192.168.88.2:::hc220:eth1:none kgdbcon console=ttyS0,115200"; */
> + /* bootargs = "console=ttyS0,115200 earlycon=uart8260,mmio32,0x1e000c00 root=/dev/ram0"; */
> + bootargs = "console=ttyS0,115200 root=/dev/nfs ip=192.168.88.2:192.168.88.5::255.255.255.0:hc220_g5:eth1:none nfsroot=192.168.88.5:/mips,vers=4,sec=sys ro rootwait";
> + };
> +
> + gpio-keys {
> + compatible = "gpio-keys";
> +
> + key-reset {
> + label = "reset";
> + gpios = <&gpio 8 GPIO_ACTIVE_LOW>;
> + linux,code = <KEY_RESTART>;
> + };
> +
> + key-wps {
> + label = "wps";
> + gpios = <&gpio 16 GPIO_ACTIVE_LOW>;
> + linux,code = <KEY_WPS_BUTTON>;
> + };
> + };
> +
> + leds {
> + compatible = "gpio-leds";
> +
> + red {
> + color = <LED_COLOR_ID_RED>;
> + function = LED_FUNCTION_FAULT;
> + gpios = <&gpio 13 GPIO_ACTIVE_HIGH>;
> + };
> +
> + green {
> + color = <LED_COLOR_ID_GREEN>;
> + function = LED_FUNCTION_POWER;
> + gpios = <&gpio 14 GPIO_ACTIVE_HIGH>;
> + linux,default-trigger = "default-on";
> + };
> +
> + blue {
> + color = <LED_COLOR_ID_BLUE>;
> + function = LED_FUNCTION_WPS;
> + gpios = <&gpio 15 GPIO_ACTIVE_HIGH>;
> + };
> + };
> +
> + resetc: reset-controller {
> + compatible = "ralink,rt2880-reset";
> + #reset-cells = <1>;
> + };
> +
> + mtd {
> + compatible = "mediatek,mt7622-nfc";
> + };
> +};
> +
> +&i2c {
> + status = "okay";
> +};
> +
> +&pcie {
> + status = "okay";
> +};
> +
> +&spi0 {
> + status = "okay";
> +
> + flash@0 {
> + #address-cells = <1>;
> + #size-cells = <1>;
> + compatible = "jedec,spi-nor";
> + reg = <0>;
> + spi-max-frequency = <50000000>;
> + };
> +};
> +
> +/* gmac1 connected to MT7530's phy0 */
> +&gmac1 {
> + status = "okay";
> + phy-handle = <ðphy0>;
> +};
> +
> +&mdio {
> + /* MT7530's phy0 */
> + ethphy0: ethernet-phy@0 {
> + reg = <0>;
> + phy-mode = "rgmii";
> + };
> +};
These are partially wrong, check the mt7621.dtsi on mainline. Or better,
don't do it. I'm very close to adding support for changing the DSA
conduit for user ports. I suggest you just add port@0 to the DSA switch
node below.
> +
> +&switch0 {
> + /* #gpio-cells = <2>;
> + gpio-controller; */
> +
> + ports {
> + /* phy0 is muxed to gmac1 */
> + /delete-node/ port@0;
> +
> + port@1 {
> + status = "okay";
> + label = "lan1";
> + };
> +
> + port@2 {
> + status = "okay";
> + label = "wan";
> + };
> + };
> +};
Arınç
next prev parent reply other threads:[~2023-05-11 13:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 20:01 Liviu Dudau
2023-05-11 13:41 ` Arınç ÜNAL [this message]
2023-05-11 16:03 ` Liviu Dudau
2023-05-12 6:40 ` Arınç ÜNAL
2023-05-29 15:08 ` [PATCH v2 0/2] " Liviu Dudau
2023-05-29 15:08 ` [PATCH v2 1/2] " Liviu Dudau
2023-05-29 15:55 ` Liviu Dudau
2023-06-03 12:06 ` Arınç ÜNAL
2023-06-04 21:30 ` Liviu Dudau
2023-06-05 7:28 ` Arınç ÜNAL
2023-06-03 12:10 ` Arınç ÜNAL
2023-05-29 15:08 ` [PATCH v2 2/2] dt-bindings: mips: Add bindings " Liviu Dudau
2023-05-29 21:00 ` Conor Dooley
2023-05-29 21:53 ` Liviu Dudau
2023-05-29 22:08 ` Conor Dooley
2023-05-30 3:35 ` Sergio Paracuellos
2023-05-11 13:43 ` [PATCH] mips: dts: ralink: Add support " Arınç ÜNAL
2023-05-11 13:59 ` Arınç ÜNAL
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43301707-8763-2a9f-956d-1ea0ae004a56@arinc9.com \
--to=arinc.unal@arinc9.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=liviu@dudau.co.uk \
--cc=paulburton@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sergio.paracuellos@gmail.com \
--cc=tsbogend@alpha.franken.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®