From: yanhong wang <yanhong.wang@starfivetech.com>
To: Sean Anderson <seanga2@gmail.com>, <u-boot@lists.denx.de>,
Rick Chen <rick@andestech.com>, Leo <ycliang@andestech.com>,
Lukasz Majewski <lukma@denx.de>
Cc: Lee Kuan Lim <kuanlim.lee@starfivetech.com>,
Jianlong Huang <jianlong.huang@starfivetech.com>,
Emil Renner Berthing <kernel@esmil.dk>
Subject: Re: [PATCH v2 16/17] riscv: dts: jh7110: Add initial StarFive VisionFive v2 board device tree
Date: Thu, 16 Feb 2023 14:20:12 +0800 [thread overview]
Message-ID: <59b46469-7e31-3a4c-dcfd-e3d4519662cf@starfivetech.com> (raw)
In-Reply-To: <ace5e586-f536-c0e2-5fe2-30d924d3ddfa@gmail.com>
On 2023/1/22 2:46, Sean Anderson wrote:
> On 1/18/23 03:11, Yanhong Wang wrote:
>> Add initial device tree for StarFive VisionFive v2 board.
>>
>> Signed-off-by: Yanhong Wang <yanhong.wang@starfivetech.com>
>> ---
>> arch/riscv/dts/Makefile | 2 +-
>> .../dts/starfive_visionfive2-u-boot.dtsi | 84 +++++++
>> arch/riscv/dts/starfive_visionfive2.dts | 234 ++++++++++++++++++
>> 3 files changed, 319 insertions(+), 1 deletion(-)
>> create mode 100644 arch/riscv/dts/starfive_visionfive2-u-boot.dtsi
>> create mode 100644 arch/riscv/dts/starfive_visionfive2.dts
>>
>> diff --git a/arch/riscv/dts/Makefile b/arch/riscv/dts/Makefile
>> index 5c15a0f303..0351cc0c38 100644
>> --- a/arch/riscv/dts/Makefile
>> +++ b/arch/riscv/dts/Makefile
>> @@ -7,7 +7,7 @@ dtb-$(CONFIG_TARGET_OPENPITON_RISCV64) += openpiton-riscv64.dtb
>> dtb-$(CONFIG_TARGET_SIFIVE_UNLEASHED) += hifive-unleashed-a00.dtb
>> dtb-$(CONFIG_TARGET_SIFIVE_UNMATCHED) += hifive-unmatched-a00.dtb
>> dtb-$(CONFIG_TARGET_SIPEED_MAIX) += k210-maix-bit.dtb
>> -
>> +dtb-$(CONFIG_TARGET_STARFIVE_VISIONFIVE2) += starfive_visionfive2.dtb
>> include $(srctree)/scripts/Makefile.dts
>> targets += $(dtb-y)
>> diff --git a/arch/riscv/dts/starfive_visionfive2-u-boot.dtsi b/arch/riscv/dts/starfive_visionfive2-u-boot.dtsi
>> new file mode 100644
>> index 0000000000..1b4e3392ab
>> --- /dev/null
>> +++ b/arch/riscv/dts/starfive_visionfive2-u-boot.dtsi
>> @@ -0,0 +1,84 @@
>> +// SPDX-License-Identifier: GPL-2.0 OR MIT
>> +/*
>> + * Copyright (C) 2022 StarFive Technology Co., Ltd.
>> + */
>> +
>> +#include "binman.dtsi"
>> +#include "jh7110-u-boot.dtsi"
>> +/ {
>> + chosen {
>> + u-boot,dm-spl;
>> + };
>> +
>> + firmware {
>> + spi0 = &qspi;
>> + u-boot,dm-spl;
>> + };
>> +
>> + config {
>> + u-boot,dm-spl;
>> + u-boot,spl-payload-offset = <0x100000>;
>> + };
>> +
>> + memory@40000000 {
>> + u-boot,dm-spl;
>> + };
>> +
>> + soc {
>> + u-boot,dm-spl;
>> +
>> + dmc: dmc@15700000 {
>> + u-boot,dm-spl;
>> + compatible = "starfive,jh7110-dmc";
>> + reg = <0x0 0x15700000 0x0 0x10000>,
>> + <0x0 0x13000000 0x0 0x10000>;
>> + resets = <&syscrg JH7110_SYSRST_DDR_AXI>,
>> + <&syscrg JH7110_SYSRST_DDR_OSC>,
>> + <&syscrg JH7110_SYSRST_DDR_APB>;
>> + reset-names = "axi", "osc", "apb";
>> + clocks = <&syscrg JH7110_SYSCLK_PLL1_OUT>;
>> + clock-names = "pll1";
>> + clock-frequency = <2133>;
>> + };
>
> Again, needs to go in SoC dtsi.
>
Thanks. I will move the dmc node to jh7110-u-boot.dtsi in the next version.
> Here are the rules for where something should go:
>
> - If it is part of the chip, it goes in the SoC dtsi, even if it is not always
> used! You can disable it by default (status = "disabled") if this is the case.
> - If it is on the board, it goes in the board dts.
> - If it is a property which is added to a node to support a board peripheral,
> it goes in the board dts.
> - If it is a U-Boot-specific property, it goes in the -u-boot.dts[i]
>
> --Sean
>
>> + };
>> +};
>> +
>> +&sys_syscon {
>> + u-boot,dm-spl;
>> +};
>> +
>> +&uart0 {
>> + u-boot,dm-spl;
>> +};
>> +
>> +&sdio0 {
>> + u-boot,dm-spl;
>> +};
>> +
>> +&sdio1 {
>> + u-boot,dm-spl;
>> +};
>> +
>> +&qspi {
>> + u-boot,dm-spl;
>> +
>> + nor-flash@0 {
>> + u-boot,dm-spl;
>> + };
>> +};
>> +
>> +&osc {
>> + u-boot,dm-spl;
>> +};
>> +
>> +&aoncrg {
>> + u-boot,dm-spl;
>> +};
>> +
>> +&syscrg {
>> + u-boot,dm-spl;
>> +};
>> +
>> +&stgcrg {
>> + u-boot,dm-spl;
>> +};
>> diff --git a/arch/riscv/dts/starfive_visionfive2.dts b/arch/riscv/dts/starfive_visionfive2.dts
>> new file mode 100644
>> index 0000000000..52b31546da
>> --- /dev/null
>> +++ b/arch/riscv/dts/starfive_visionfive2.dts
>> @@ -0,0 +1,234 @@
>> +// SPDX-License-Identifier: GPL-2.0 OR MIT
>> +/*
>> + * Copyright (C) 2022 StarFive Technology Co., Ltd.
>> + */
>> +
>> +/dts-v1/;
>> +
>> +#include "jh7110.dtsi"
>> +#include <dt-bindings/pinctrl/pinctrl-starfive-jh7110.h>
>> +/ {
>> + #address-cells = <2>;
>> + #size-cells = <2>;
>> + model = "StarFive VisionFive V2";
>> + compatible = "starfive,jh7110";
>> +
>> + aliases {
>> + spi0 = &qspi;
>> + mmc0 = &sdio0;
>> + mmc1 = &sdio1;
>> + };
>> +
>> + chosen {
>> + stdout-path = "/soc/serial@10000000:115200";
>> + };
>> +
>> + cpus {
>> + timebase-frequency = <4000000>;
>> + };
>> +
>> + memory@40000000 {
>> + device_type = "memory";
>> + reg = <0x0 0x40000000 0x1 0x0>;
>> + };
>> +
>> + soc {
>> + sys_syscon: sys_syscon@13030000 {
>> + compatible = "syscon";
>> + reg = <0x0 0x13030000 0x0 0x1000>;
>> + };
>> + };
>
> ditto
>
I will move sys_syscon node to jh7110.dtsi
>> +};
>> +
>> +&S76_0 {
>> + status = "okay";
>> +};
>> +
>> +&osc {
>> + clock-frequency = <24000000>;
>> +};
>> +
>> +&clk_rtc {
>> + clock-frequency = <32768>;
>> +};
>> +
>> +&gmac0_rmii_refin {
>> + clock-frequency = <50000000>;
>> +};
>> +
>> +&gmac0_rgmii_rxin {
>> + clock-frequency = <125000000>;
>> +};
>> +
>> +&gmac1_rmii_refin {
>> + clock-frequency = <50000000>;
>> +};
>> +
>> +&gmac1_rgmii_rxin {
>> + clock-frequency = <125000000>;
>> +};
>> +
>> +&i2stx_bclk_ext {
>> + clock-frequency = <12288000>;
>> +};
>> +
>> +&i2stx_lrck_ext {
>> + clock-frequency = <192000>;
>> +};
>> +
>> +&i2srx_bclk_ext {
>> + clock-frequency = <12288000>;
>> +};
>> +
>> +&i2srx_lrck_ext {
>> + clock-frequency = <192000>;
>> +};
>> +
>> +&tdm_ext {
>> + clock-frequency = <49152000>;
>> +};
>> +
>> +&mclk_ext {
>> + clock-frequency = <12288000>;
>> +};
>> +
>> +&gpio {
>> + status = "okay";
>> + uart0_pins: uart0-0 {
>> + tx-pins {
>> + pinmux = <GPIOMUX(5, GPOUT_SYS_UART0_TX,
>> + GPOEN_ENABLE, GPI_NONE)>;
>> + bias-disable;
>> + drive-strength = <12>;
>> + input-disable;
>> + input-schmitt-disable;
>> + slew-rate = <0>;
>> + };
>> +
>> + rx-pins {
>> + pinmux = <GPIOMUX(6, GPOUT_LOW,
>> + GPOEN_DISABLE, GPI_SYS_UART0_RX)>;
>> + bias-pull-up;
>> + drive-strength = <2>;
>> + input-enable;
>> + input-schmitt-enable;
>> + slew-rate = <0>;
>> + };
>> + };
>> +
>> + mmc0_pins: mmc0-pins {
>> + mmc0-pins-rest {
>> + pinmux = <GPIOMUX(62, GPOUT_SYS_SDIO0_RST,
>> + GPOEN_ENABLE, GPI_NONE)>;
>> + bias-pull-up;
>> + drive-strength = <12>;
>> + input-disable;
>> + input-schmitt-disable;
>> + slew-rate = <0>;
>> + };
>> + };
>> +
>> + sdcard1_pins: sdcard1-pins {
>> + sdcard1-pins0 {
>> + pinmux = <GPIOMUX(10, GPOUT_SYS_SDIO1_CLK,
>> + GPOEN_ENABLE, GPI_NONE)>;
>> + bias-pull-up;
>> + drive-strength = <12>;
>> + input-disable;
>> + input-schmitt-disable;
>> + slew-rate = <0>;
>> + };
>> +
>> + sdcard1-pins1 {
>> + pinmux = <GPIOMUX(9, GPOUT_SYS_SDIO1_CMD,
>> + GPOEN_SYS_SDIO1_CMD, GPI_SYS_SDIO1_CMD)>;
>> + bias-pull-up;
>> + drive-strength = <12>;
>> + input-enable;
>> + input-schmitt-enable;
>> + slew-rate = <0>;
>> + };
>> +
>> + sdcard1-pins2 {
>> + pinmux = <GPIOMUX(11, GPOUT_SYS_SDIO1_DATA0,
>> + GPOEN_SYS_SDIO1_DATA0, GPI_SYS_SDIO1_DATA0)>;
>> + bias-pull-up;
>> + drive-strength = <12>;
>> + input-enable;
>> + input-schmitt-enable;
>> + slew-rate = <0>;
>> + };
>> +
>> + sdcard1-pins3 {
>> + pinmux = <GPIOMUX(12, GPOUT_SYS_SDIO1_DATA1,
>> + GPOEN_SYS_SDIO1_DATA1, GPI_SYS_SDIO1_DATA1)>;
>> + bias-pull-up;
>> + drive-strength = <12>;
>> + input-enable;
>> + input-schmitt-enable;
>> + slew-rate = <0>;
>> + };
>> +
>> + sdcard1-pins4 {
>> + pinmux = <GPIOMUX(7, GPOUT_SYS_SDIO1_DATA2,
>> + GPOEN_SYS_SDIO1_DATA2, GPI_SYS_SDIO1_DATA2)>;
>> + bias-pull-up;
>> + drive-strength = <12>;
>> + input-enable;
>> + input-schmitt-enable;
>> + slew-rate = <0>;
>> + };
>> +
>> + sdcard1-pins5 {
>> + pinmux = <GPIOMUX(8, GPOUT_SYS_SDIO1_DATA3,
>> + GPOEN_SYS_SDIO1_DATA3, GPI_SYS_SDIO1_DATA3)>;
>> + bias-pull-up;
>> + drive-strength = <12>;
>> + input-enable;
>> + input-schmitt-enable;
>> + slew-rate = <0>;
>> + };
>> + };
>> +};
>> +
>> +&sdio0 {
>> + bus-width = <8>;
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&mmc0_pins>;
>> + status = "okay";
>> +};
>> +
>> +&sdio1 {
>> + bus-width = <4>;
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&sdcard1_pins>;
>> + status = "okay";
>> +};
>> +
>> +&uart0 {
>> + reg-offset = <0>;
>> + current-speed = <115200>;
>> + clock-frequency = <24000000>;
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&uart0_pins>;
>> + status = "okay";
>> +};
>> +
>> +&qspi {
>> + spi-max-frequency = <250000000>;
>> + status = "okay";
>> +
>> + nor-flash@0 {
>> + compatible = "jedec,spi-nor";
>> + reg=<0>;
>> + spi-max-frequency = <100000000>;
>> + cdns,tshsl-ns = <1>;
>> + cdns,tsd2d-ns = <1>;
>> + cdns,tchsh-ns = <1>;
>> + cdns,tslch-ns = <1>;
>> + };
>> +};
>> +
>> +&syscrg {
>> + starfive,sys-syscon = <&sys_syscon>;
>> +};
>
> ditto
I will move it to jh7110.dtsi
next prev parent reply other threads:[~2023-02-16 6:20 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 8:11 [PATCH v2 00/17] Basic StarFive JH7110 RISC-V SoC support Yanhong Wang
2023-01-18 8:11 ` [PATCH v2 01/17] riscv: cpu: jh7110: Add support for jh7110 SoC Yanhong Wang
2023-01-18 8:11 ` [PATCH v2 02/17] cache: starfive: Add StarFive JH7110 support Yanhong Wang
2023-01-18 8:11 ` [PATCH v2 03/17] dt-bindings: reset: Add StarFive JH7110 reset definitions Yanhong Wang
2023-01-18 8:11 ` [PATCH v2 04/17] reset: starfive: jh7110: Add reset driver for StarFive JH7110 SoC Yanhong Wang
2023-01-18 8:11 ` [PATCH v2 05/17] dt-bindings: clock: Add StarFive JH7110 clock definitions Yanhong Wang
2023-01-21 18:37 ` Sean Anderson
2023-01-18 8:11 ` [PATCH v2 06/17] clk: starfive: Add StarFive JH7110 clock driver Yanhong Wang
2023-01-21 18:56 ` Sean Anderson
2023-02-16 3:16 ` yanhong wang
2023-01-18 8:11 ` [PATCH v2 07/17] dt-bindings: pinctrl: Add StarFive JH7110 pinctrl definitions Yanhong Wang
2023-01-18 8:11 ` [PATCH v2 08/17] pinctrl: starfive: Add StarFive JH7110 driver Yanhong Wang
2023-01-18 8:11 ` [PATCH v2 09/17] ram: starfive: add ddr driver Yanhong Wang
2023-01-18 8:11 ` [PATCH v2 10/17] board: starfive: add StarFive VisionFive v2 board support Yanhong Wang
2023-01-21 17:38 ` Sean Anderson
2023-01-18 8:11 ` [PATCH v2 11/17] riscv: cpu: jh7110: Add Kconfig for StarFive JH7110 SoC Yanhong Wang
2023-01-18 8:11 ` [PATCH v2 13/17] board: starfive: Add TARGET_STARFIVE_VISIONFIVE2 to Kconfig Yanhong Wang
2023-01-18 8:11 ` [PATCH v2 14/17] riscv: dts: jh7110: Add initial StarFive JH7110 device tree Yanhong Wang
2023-01-19 6:18 ` David Abdurachmanov
2023-01-19 6:26 ` Sean Anderson
2023-01-19 18:30 ` Conor Dooley
2023-01-19 19:16 ` Sean Anderson
2023-01-19 19:25 ` Conor Dooley
2023-01-20 1:37 ` Sean Anderson
2023-02-16 5:50 ` yanhong wang
2023-01-18 8:11 ` [PATCH v2 15/17] riscv: dts: jh7110: Add initial u-boot " Yanhong Wang
2023-01-18 8:11 ` [PATCH v2 16/17] riscv: dts: jh7110: Add initial StarFive VisionFive v2 board " Yanhong Wang
2023-01-21 18:46 ` Sean Anderson
2023-02-16 6:20 ` yanhong wang [this message]
2023-01-18 8:11 ` [PATCH v2 17/17] configs: starfive: add starfive_visionfive2_defconfig Yanhong Wang
2023-01-23 14:53 ` Andreas Schwab
2023-02-16 7:28 ` yanhong wang
2023-02-16 14:17 ` Heinrich Schuchardt
2023-01-21 21:36 ` [PATCH v2 00/17] Basic StarFive JH7110 RISC-V SoC support Conor Dooley
2023-01-21 21:56 ` Sean Anderson
2023-01-21 22:05 ` Conor Dooley
2023-01-22 18:42 ` Conor Dooley
2023-02-10 17:41 ` Conor Dooley
2023-02-16 7:39 ` yanhong wang
2023-01-24 0:28 ` Heinrich Schuchardt
2023-02-16 9:01 ` yanhong wang
2023-01-24 14:46 ` Andreas Schwab
2023-02-06 7:38 ` Jan Kiszka
2023-02-07 15:46 ` Bin Meng
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=59b46469-7e31-3a4c-dcfd-e3d4519662cf@starfivetech.com \
--to=yanhong.wang@starfivetech.com \
--cc=jianlong.huang@starfivetech.com \
--cc=kernel@esmil.dk \
--cc=kuanlim.lee@starfivetech.com \
--cc=lukma@denx.de \
--cc=rick@andestech.com \
--cc=seanga2@gmail.com \
--cc=u-boot@lists.denx.de \
--cc=ycliang@andestech.com \
/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