From: Matthias Brugger <mbrugger@suse.com>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
Hal Feng <hal.feng@starfivetech.com>,
Minda Chen <minda.chen@starfivetech.com>
Cc: Rick Chen <rick@andestech.com>, Leo <ycliang@andestech.com>,
E Shattow <e@freeshell.de>, Sumit Garg <sumit.garg@kernel.org>,
H Bell <dmoo_dv@protonmail.com>, Simon Glass <sjg@chromium.org>,
Andreas Schwab <schwab@suse.de>,
u-boot@lists.denx.de, Sumit Garg <sumit.garg@linaro.org>
Subject: Re: [PATCH v3 2/8] riscv: dts: jh7110: add DeepComputing FML13V01 device-tree
Date: Wed, 9 Apr 2025 12:27:36 +0200 [thread overview]
Message-ID: <17c7d897-6275-4f75-91c9-13c40b7ffc1c@suse.com> (raw)
In-Reply-To: <20250409071836.26629-3-heinrich.schuchardt@canonical.com>
On 09/04/2025 09:18, Heinrich Schuchardt wrote:
> Add the u-boot device-tree include needed to support the
> DeepComputing Framework motherboard (FML13V01).
>
> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
> Reviewed-by: Sumit Garg <sumit.garg@linaro.org>
> Reviewed-by: Hal Feng <hal.feng@starfivetech.com>
Reviewed-by: Matthias Brugger <mbrugger@suse.com>
> ---
> v3:
> no change
> v2:
> no change
> ---
> arch/riscv/dts/jh7110-deepcomputing-fml13v01-u-boot.dtsi | 7 +++++++
> 1 file changed, 7 insertions(+)
> create mode 100644 arch/riscv/dts/jh7110-deepcomputing-fml13v01-u-boot.dtsi
>
> diff --git a/arch/riscv/dts/jh7110-deepcomputing-fml13v01-u-boot.dtsi b/arch/riscv/dts/jh7110-deepcomputing-fml13v01-u-boot.dtsi
> new file mode 100644
> index 00000000000..ab882d07f6f
> --- /dev/null
> +++ b/arch/riscv/dts/jh7110-deepcomputing-fml13v01-u-boot.dtsi
> @@ -0,0 +1,7 @@
> +// SPDX-License-Identifier: GPL-2.0 OR MIT
> +/*
> + * Copyright (C) 2024 StarFive Technology Co., Ltd.
> + */
> +
> +#include "jh7110-common-u-boot.dtsi"
> +#include "starfive-visionfive2-binman.dtsi"
next prev parent reply other threads:[~2025-04-09 10:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 7:18 [PATCH v3 0/8] board: starfive: DeepComputing FML13V01 Heinrich Schuchardt
2025-04-09 7:18 ` [PATCH v3 1/8] configs: add jh7110-deepcomputing-fml13v01 to VF2 defconfig Heinrich Schuchardt
2025-04-09 10:27 ` Matthias Brugger
2025-04-09 7:18 ` [PATCH v3 2/8] riscv: dts: jh7110: add DeepComputing FML13V01 device-tree Heinrich Schuchardt
2025-04-09 10:27 ` Matthias Brugger [this message]
2025-04-09 7:18 ` [PATCH v3 3/8] board: starfive: DeepComputing FML13V01 fdt selection Heinrich Schuchardt
2025-04-09 10:28 ` Matthias Brugger
2025-04-09 7:18 ` [PATCH v3 4/8] board: starfive: spl: support DeepComputing FML13V01 Heinrich Schuchardt
2025-04-09 7:51 ` Hal Feng
2025-04-09 10:28 ` Matthias Brugger
2025-04-09 7:18 ` [PATCH v3 5/8] doc: add DeepComputing FML13V01 documentation Heinrich Schuchardt
2025-04-09 7:18 ` [PATCH v3 6/8] doc: starfive: use consistent formatting Heinrich Schuchardt
2025-04-09 7:18 ` [PATCH v3 7/8] doc: starfive: use jh7110_common.rst Heinrich Schuchardt
2025-04-09 7:18 ` [PATCH v3 8/8] doc: jh7110: describe debug UART Heinrich Schuchardt
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=17c7d897-6275-4f75-91c9-13c40b7ffc1c@suse.com \
--to=mbrugger@suse.com \
--cc=dmoo_dv@protonmail.com \
--cc=e@freeshell.de \
--cc=hal.feng@starfivetech.com \
--cc=heinrich.schuchardt@canonical.com \
--cc=minda.chen@starfivetech.com \
--cc=rick@andestech.com \
--cc=schwab@suse.de \
--cc=sjg@chromium.org \
--cc=sumit.garg@kernel.org \
--cc=sumit.garg@linaro.org \
--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