From: Tom Rini <trini@konsulko.com>
To: Kelly Hung <ppighouse@gmail.com>
Cc: u-boot@lists.denx.de, openbmc@lists.ozlabs.org, kelly_hung@asus.com
Subject: Re: [PATCH] dts: ast2600: add x4tf dts for asus product
Date: Tue, 30 Jan 2024 10:09:06 -0500 [thread overview]
Message-ID: <20240130150906.GR1152441@bill-the-cat> (raw)
In-Reply-To: <20240130104045.199879-1-Kelly_Hung@asus.com>
[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]
On Tue, Jan 30, 2024 at 06:40:45PM +0800, Kelly Hung wrote:
> This initial device-tree provides the necessary configuration for
> basic BMC functionality and work on ASUS X4TF production.
>
> Signed-off-by: Kelly Hung <Kelly_Hung@asus.com>
> ---
> arch/arm/dts/Makefile | 3 +-
> arch/arm/dts/ast2600-x4tf.dts | 239 ++++++++++++++++++++++++++++++++++
[snip]
> diff --git a/arch/arm/dts/ast2600-x4tf.dts b/arch/arm/dts/ast2600-x4tf.dts
> new file mode 100644
> index 00000000..3c478058
> --- /dev/null
> +++ b/arch/arm/dts/ast2600-x4tf.dts
> @@ -0,0 +1,239 @@
> +// SPDX-License-Identifier: GPL-2.0+
> +// Copyright 2020 IBM Corp.
> +/dts-v1/;
> +
> +#include "ast2600-u-boot.dtsi"
> +
> +/ {
> + model = "AST2600 ASUS";
> + compatible = "aspeed,ast2600-evb", "aspeed,ast2600";
Compatible should be board unique.
> +&uart5 {
> + u-boot,dm-pre-reloc;
All of these are bootph* now.
And is there effort being made to upstream the dts files for these
platforms to Linux?
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-01-30 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 10:40 [PATCH] dts: ast2600: add x4tf dts for asus product Kelly Hung
2024-01-30 15:09 ` Tom Rini [this message]
2024-02-01 9:22 ` Kelly Hung(洪嘉莉)
2024-02-01 9:58 ` Kelly Hung(洪嘉莉)
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=20240130150906.GR1152441@bill-the-cat \
--to=trini@konsulko.com \
--cc=kelly_hung@asus.com \
--cc=openbmc@lists.ozlabs.org \
--cc=ppighouse@gmail.com \
--cc=u-boot@lists.denx.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).