From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jun Yan <jerrysteve1101@gmail.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
heiko@sntech.de, quentin.schulz@cherry.de, dsimic@manjaro.org,
naoki@radxa.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH 3/3] arm64: dts: rockchip: Add OneThing Cloud OEC turbo
Date: Mon, 14 Jul 2025 08:02:35 +0200 [thread overview]
Message-ID: <20250714-wise-tall-parrot-3e4347@krzk-bin> (raw)
In-Reply-To: <20250713163255.163669-4-jerrysteve1101@gmail.com>
On Mon, Jul 14, 2025 at 12:32:55AM +0800, Jun Yan wrote:
> +#include <dt-bindings/gpio/gpio.h>
> +#include <dt-bindings/leds/common.h>
> +#include <dt-bindings/pinctrl/rockchip.h>
> +#include "rk3566.dtsi"
> +
> +/ {
> + model = "OneThing Cloud OEC turbo";
> + compatible = "onething,cloud-oec-turbo", "rockchip,rk3566";
> +
> + aliases {
> + ethernet0 = &gmac1;
> + mmc0 = &sdhci;
> + };
> +
> + chosen: chosen {
> + stdout-path = "serial2:1500000n8";
> + };
> +
> + /* No hardware video output port */
> + /delete-node/ display-subsystem;
Nodes should be disabled, not removed. What does it mean it is being
removed? You physically take it out from the hardware? How could it
exist in the first place in the SoC if it is not present on the board?
> +
> + gmac1_clkin: external-gmac1-clock {
> + compatible = "fixed-clock";
> + clock-frequency = <125000000>;
> + clock-output-names = "gmac1_clkin";
> + #clock-cells = <0>;
> + };
> +
> + leds {
> + compatible = "gpio-leds";
> +
> + rgb_led_r: rgb-led-r {
led-0
Node names should be generic. See also an explanation and list of
examples (not exhaustive) in DT specification:
https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation
> + color = <LED_COLOR_ID_RED>;
> + default-state = "off";
> + function = LED_FUNCTION_STATUS;
> + gpios = <&gpio0 RK_PC3 GPIO_ACTIVE_LOW>;
> + };
...
> +
> +&gmac1 {
> + assigned-clocks = <&cru SCLK_GMAC1_RX_TX>, <&cru SCLK_GMAC1>;
> + assigned-clock-parents = <&cru SCLK_GMAC1_RGMII_SPEED>, <&gmac1_clkin>;
> + phy-mode = "rgmii";
> + clock_in_out = "input";
> + pinctrl-names = "default";
> + pinctrl-0 = <&gmac1m1_miim
> + &gmac1m1_tx_bus2
> + &gmac1m1_rx_bus2
> + &gmac1m1_rgmii_clk
> + &gmac1m1_rgmii_bus
> + &gmac1m1_clkinout>;
> + snps,reset-gpio = <&gpio4 RK_PC2 GPIO_ACTIVE_LOW>;
> + snps,reset-active-low;
> + /* Reset time is 20ms, 100ms for rtl8211f */
> + snps,reset-delays-us = <0 20000 100000>;
> +
> + tx_delay = <0x4f>;
> + rx_delay = <0x2d>;
> + phy-handle = <&rgmii_phy1>;
> + status = "okay";
> +};
> +
> +&gpu {
> + status = "okay";
> +};
> +
> +&mdio1 {
> + rgmii_phy1: ethernet-phy@1 {
> + compatible = "ethernet-phy-ieee802.3-c22";
> + reg = <0x1>;
> + };
> +};
> +
> +&pinctrl {
> + usb {
> + vcc5v0_usb_host_en: vcc5v0_usb_host_en {
Follow DTS coding style.
> + rockchip,pins = <0 RK_PC6 RK_FUNC_GPIO &pcfg_pull_none>;
> + };
> + };
> +};
Best regards,
Krzysztof
prev parent reply other threads:[~2025-07-14 6:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-13 16:32 [PATCH 0/3] board: rockchip: add OneThing Cloud OEC turbo Jun Yan
2025-07-13 16:32 ` [PATCH 1/3] dt-bindings: vendor-prefixes: Add Shenzhen OneThing Technologies Co., Ltd Jun Yan
2025-07-13 17:28 ` Rob Herring (Arm)
2025-07-13 18:57 ` Heiko Stübner
2025-07-13 16:32 ` [PATCH 2/3] dt-bindings: arm: rockchip: Add OneThing Cloud OEC turbo Jun Yan
2025-07-15 3:33 ` Rob Herring (Arm)
2025-07-13 16:32 ` [PATCH 3/3] arm64: dts: " Jun Yan
2025-07-13 16:48 ` Andrew Lunn
2025-07-14 6:02 ` Krzysztof Kozlowski [this message]
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=20250714-wise-tall-parrot-3e4347@krzk-bin \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=heiko@sntech.de \
--cc=jerrysteve1101@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=naoki@radxa.com \
--cc=quentin.schulz@cherry.de \
--cc=robh@kernel.org \
/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