[PATCH 2/2] arm64: dts: allwinner: h616: Add Sipeed Longan SoM 3H and Pi 3H board support
Jisheng Zhang
jszhang at kernel.org
Sat Feb 3 04:29:46 PST 2024
On Fri, Dec 29, 2023 at 11:55:43PM +0000, Andre Przywara wrote:
> On Thu, 28 Dec 2023 22:56:47 +0800
> Jisheng Zhang <jszhang at kernel.org> wrote:
>
> Hi,
>
> > The Sipeed Longan SoM 3H is a system on module based on the Allwinner
> > H618 SoC. The SoM features:
> >
> > - Four ARM Cortex-A53 cores, Mali-G31 MP2 GPU
> > - 2/4 GiB LPDDR4 DRAM SoMs
> > - AXP313a PMIC
> > - eMMC
> >
> > The Sipeed Longan PI 3H is a development board based on the above SoM.
> > The board features:
> > - Longan SoM 3H
> > - Raspberry-Pi-1 compatible GPIO header
> > - 2 USB 2.0 host port
> > - 1 USB 2.0 type C port (power supply + OTG)
> > - MicroSD slot
> > - 1Gbps Ethernet port (via RTL8211 PHY)
> > - HDMI port
> > - WiFi/BT chip
> >
> > Add the devicetree file describing the currently supported features,
> > namely PMIC, LEDs, UART, SD card, eMMC, USB and Ethernet.
> >
> > Signed-off-by: Jisheng Zhang <jszhang at kernel.org>
> > ---
> > arch/arm64/boot/dts/allwinner/Makefile | 1 +
> > .../sun50i-h618-longan-module-3h.dtsi | 82 +++++++++++
> > .../dts/allwinner/sun50i-h618-longanpi-3h.dts | 133 ++++++++++++++++++
> > 3 files changed, 216 insertions(+)
> > create mode 100644 arch/arm64/boot/dts/allwinner/sun50i-h618-longan-module-3h.dtsi
> > create mode 100644 arch/arm64/boot/dts/allwinner/sun50i-h618-longanpi-3h.dts
> >
> > diff --git a/arch/arm64/boot/dts/allwinner/Makefile b/arch/arm64/boot/dts/allwinner/Makefile
> > index 3aca6787a167..00db504a9b8c 100644
> > --- a/arch/arm64/boot/dts/allwinner/Makefile
> > +++ b/arch/arm64/boot/dts/allwinner/Makefile
> > @@ -42,4 +42,5 @@ dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h616-bigtreetech-cb1-manta.dtb
> > dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h616-bigtreetech-pi.dtb
> > dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h616-orangepi-zero2.dtb
> > dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h616-x96-mate.dtb
> > +dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h618-longanpi-3h.dtb
> > dtb-$(CONFIG_ARCH_SUNXI) += sun50i-h618-orangepi-zero3.dtb
> > diff --git a/arch/arm64/boot/dts/allwinner/sun50i-h618-longan-module-3h.dtsi b/arch/arm64/boot/dts/allwinner/sun50i-h618-longan-module-3h.dtsi
> > new file mode 100644
> > index 000000000000..88a7d287b73c
> > --- /dev/null
> > +++ b/arch/arm64/boot/dts/allwinner/sun50i-h618-longan-module-3h.dtsi
> > @@ -0,0 +1,82 @@
> > +// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
> > +/*
> > + * Copyright (C) Jisheng Zhang <jszhang at kernel.org>
> > + */
> > +
> > +/dts-v1/;
>
> I don't see how the SoM could be used on its own, without a hosting
> board. So we don't need the dts version tag in the .dtsi, that would
> just be double when we are going to compile any actual .dtb.
>
> > +
> > +#include "sun50i-h616.dtsi"
> > +
> > +/ {
> > + model = "Sipeed Longan Module 3H";
> > + compatible = "sipeed,longan-module-3h", "allwinner,sun50i-h618";
>
> Same here, any model or compatible string would only be overwritten by
> the board versions, so you don't need those two in the SoM .dtsi.
> Compare the SoPine and BTT CB1 .dtsi files.
>
> > +};
> > +
> > +&mmc2 {
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&mmc2_pins>;
>
> Can you please add the DS pin here? At the moment the sunxi Linux
> driver doesn't support HS-400, but that can a) change and b) doesn't
> affect the DT anyway, since that describes the hardware. The connection
> is definitely there, according to the schematics.
Hi Andre,
Thank you so much for the review and comments, could you please review?
Except DS pin, other comments are adopted and updated in v2.
DS pin is already there, IIUC, PC0 is emmc DS pin
Thanks
>
> > + vmmc-supply = <®_dldo1>;
> > + vqmmc-supply = <®_aldo1>;
> > + bus-width = <8>;
> > + non-removable;
> > + cap-mmc-hw-reset;
> > + mmc-ddr-1_8v;
> > + mmc-hs200-1_8v;
> > + status = "okay";
> > +};
> > +
> > +&r_i2c {
> > + status = "okay";
> > +
> > + axp313: pmic at 36 {
> > + compatible = "x-powers,axp313a";
>
> According to the bindings you need:
>
> interrupt-controller;
> #interrupt-cells = <1>;
>
> Even without the IRQ line connected. dt-validate complains about that.
>
> Actually, do you know of any reason why it is not connected? I see it on
> the SoM pins, is the idea that any *board* could dedicate a GPIO pin for
> it, if needed?
>
> > + reg = <0x36>;
> > +
> > + regulators {
> > + /* Supplies VCC-PLL, so needs to be always on. */
> > + reg_aldo1: aldo1 {
> > + regulator-always-on;
> > + regulator-min-microvolt = <1800000>;
> > + regulator-max-microvolt = <1800000>;
> > + regulator-name = "vcc1v8";
>
> Can you please use "vcc-1v8-pll" instead? Then you don't need the
> comment.
>
> > + };
> > +
> > + /* Supplies VCC-IO, so needs to be always on. */
> > + reg_dldo1: dldo1 {
> > + regulator-always-on;
> > + regulator-min-microvolt = <3300000>;
> > + regulator-max-microvolt = <3300000>;
> > + regulator-name = "vcc3v3";
>
> Same here, "vcc-3v3-io" is the name we used lately, to avoid the
> comment.
>
> > + };
> > +
> > + reg_dcdc1: dcdc1 {
> > + regulator-always-on;
> > + regulator-min-microvolt = <810000>;
> > + regulator-max-microvolt = <990000>;
> > + regulator-name = "vdd-gpu-sys";
> > + };
> > +
> > + reg_dcdc2: dcdc2 {
> > + regulator-always-on;
> > + regulator-min-microvolt = <810000>;
> > + regulator-max-microvolt = <1100000>;
> > + regulator-name = "vdd-cpu";
> > + };
> > +
> > + reg_dcdc3: dcdc3 {
> > + regulator-always-on;
> > + regulator-min-microvolt = <1100000>;
> > + regulator-max-microvolt = <1100000>;
> > + regulator-name = "vdd-dram";
> > + };
> > + };
> > + };
> > +};
> > +
> > +&pio {
> > + vcc-pc-supply = <®_dldo1>;
> > + vcc-pf-supply = <®_dldo1>;
> > + vcc-pg-supply = <®_aldo1>;
> > + vcc-ph-supply = <®_dldo1>;
> > + vcc-pi-supply = <®_dldo1>;
> > +};
> > diff --git a/arch/arm64/boot/dts/allwinner/sun50i-h618-longanpi-3h.dts b/arch/arm64/boot/dts/allwinner/sun50i-h618-longanpi-3h.dts
> > new file mode 100644
> > index 000000000000..245583881549
> > --- /dev/null
> > +++ b/arch/arm64/boot/dts/allwinner/sun50i-h618-longanpi-3h.dts
> > @@ -0,0 +1,133 @@
> > +// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
> > +/*
> > + * Copyright (C) Jisheng Zhang <jszhang at kernel.org>
> > + */
> > +
> > +/dts-v1/;
> > +
> > +#include "sun50i-h618-longan-module-3h.dtsi"
> > +
> > +#include <dt-bindings/gpio/gpio.h>
> > +#include <dt-bindings/interrupt-controller/arm-gic.h>
> > +#include <dt-bindings/leds/common.h>
> > +
> > +/ {
> > + model = "Sipeed Longan Pi 3H";
> > + compatible = "sipeed,longan-pi-3h", "sipeed,longan-module-3h", "allwinner,sun50i-h618";
> > +
> > + aliases {
> > + ethernet0 = &emac0;
> > + serial0 = &uart0;
> > + };
> > +
> > + chosen {
> > + stdout-path = "serial0:115200n8";
> > + };
> > +
> > + leds {
> > + compatible = "gpio-leds";
> > +
> > + led-0 {
> > + color = <LED_COLOR_ID_ORANGE>;
> > + function = LED_FUNCTION_INDICATOR;
> > + function-enumerator = <0>;
> > + gpios = <&pio 6 2 GPIO_ACTIVE_LOW>; /* PG2 */
> > + };
> > +
> > + led-1 {
> > + color = <LED_COLOR_ID_ORANGE>;
> > + function = LED_FUNCTION_INDICATOR;
> > + function-enumerator = <1>;
> > + gpios = <&pio 6 4 GPIO_ACTIVE_LOW>; /* PG4 */
> > + };
> > + };
> > +
> > + reg_vcc5v: vcc5v {
> > + /* board wide 5V supply directly from the USB-C socket */
> > + compatible = "regulator-fixed";
> > + regulator-name = "vcc-5v";
> > + regulator-min-microvolt = <5000000>;
> > + regulator-max-microvolt = <5000000>;
> > + regulator-always-on;
> > + };
>
> According to the schematic, there is a discrete 5V->3.3V regulator, can
> you please describe this here as well?
>
> > +};
> > +
> > +&axp313 {
> > + vin1-supply = <®_vcc5v>;
> > + vin2-supply = <®_vcc5v>;
> > + vin3-supply = <®_vcc5v>;
> > +};
> > +
> > +&ehci1 {
> > + status = "okay";
> > +};
> > +
> > +&ohci1 {
> > + status = "okay";
> > +};
> > +
> > +&ehci2 {
> > + status = "okay";
> > +};
> > +
> > +&ohci2 {
> > + status = "okay";
> > +};
> > +
>
> Maybe worth adding a comment here that there is a USB WiFi chip
> connected to those pins.
>
> > +&ehci3 {
> > + status = "okay";
> > +};
> > +
> > +&ohci3 {
> > + status = "okay";
> > +};
> > +
> > +&emac0 {
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&ext_rgmii_pins>;
> > + phy-mode = "rgmii";
> > + phy-handle = <&ext_rgmii_phy>;
> > + allwinner,rx-delay-ps = <3100>;
> > + allwinner,tx-delay-ps = <700>;
> > + phy-supply = <®_dldo1>;
>
> If I get the schematic correctly, the PHY is powered from the discrete
> 3.3V regulator? In fact, the 3V3-DLDO-OUT/1V8-ALDO-OUT pins on the SoM
> do not seem to be connected, so anything using 3.3V or 1.8V on the
> board needs to be fed from this regulator, and everything on the SoM is
> supplied by the AXP?
>
> > + status = "okay";
> > +};
> > +
> > +&mdio0 {
> > + ext_rgmii_phy: ethernet-phy at 1 {
> > + compatible = "ethernet-phy-ieee802.3-c22";
> > + reg = <1>;
> > + };
> > +};
> > +
> > +&mmc0 {
> > + bus-width = <4>;
> > + cd-gpios = <&pio 5 6 GPIO_ACTIVE_HIGH>; /* PF6 */
> > + vmmc-supply = <®_dldo1>;
>
> According to the schematic, the SD card is supplied by the discrete
> 3.3V regulator on the board.
>
> > + status = "okay";
> > +};
> > +
> > +&uart0 {
> > + status = "okay";
> > +};
> > +
> > +&usbotg {
> > + /*
> > + * PHY0 pins are connected to a USB-C socket, but a role switch
> > + * is not implemented: both CC pins are pulled to GND.
> > + * The VBUS pins power the device, so a fixed peripheral mode
> > + * is the best choice.
> > + * The board can be powered via GPIOs, in this case port0 *can*
> > + * act as a host (with a cable/adapter ignoring CC), as VBUS is
> > + * then provided by the GPIOs. Any user of this setup would
> > + * need to adjust the DT accordingly: dr_mode set to "host",
> > + * enabling OHCI0 and EHCI0.
> > + */
> > + dr_mode = "peripheral";
> > + status = "okay";
> > +};
> > +
> > +&usbphy {
> > + usb1_vbus-supply = <®_vcc5v>;
>
> The same seems to be true for USB2 as well, and the WiFi chip on USB3 is
> powered by the discrete 3.3V regulator. But I think we don't need these
> properties at all if it's directly connected to the input and so always
> powered. Or maybe we should do this anyway, and be it to make it clear
> where the bus power is coming from?
>
> Cheers,
> Andre
>
> P.S. I saw some U-Boot patches on some github. Most of them are
> merged, but feel free to post the DT (same ones as here) and the
> defconfig to the U-Boot list as well. You can use "make savedefconfig"
> when you have configured the board, this will create a file "defconfig"
> in the build directory that contains the minimal items, this can be
> directly used as a defconfig.
>
> > + status = "okay";
> > +};
>
More information about the linux-arm-kernel
mailing list