From: Peter Yin <peteryin.openbmc@gmail.com>
To: patrick@stwcx.xyz, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@aj.id.au>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: peter.yin@quantatw.com, Peter Yin <peteryin.openbmc@gmail.com>
Subject: [PATCH v8 0/2] Add Facebook Minerva (AST2600) BMC
Date: Tue, 5 Sep 2023 14:22:20 +0800 [thread overview]
Message-ID: <20230905062223.774871-1-peteryin.openbmc@gmail.com> (raw)
Summary:
Correcting the arrangement order in Makefile.
+ aspeed-bmc-facebook-greatlakes.dtb \
+ aspeed-bmc-facebook-minerva.dtb \
+ aspeed-bmc-facebook-minipack.dtb \
Correcting the arrangement order in Document
+ - facebook,greatlakes-bmc
+ - facebook,minerva-bmc
+ - facebook,yosemite4-bmc
Remove redundant blank line.
1.
+ /*P4-P7 line 248-255*/
+ "","","","","","","","";
+};
2.
+
+// SOL Host Console
3.
+
+//BIOS Flash
4.
+&uart2 {
+ status = "okay";
+ pinctrl-0 = <>;
+};
Use stdout-path.
+ chosen {
+ stdout-path = &uart5;
+ };
Fix dts path.
old:arch/arm/boot/dts/
new:arch/arm/boot/dts/aspeed
*** BLURB HERE ***
Peter Yin (2):
ARM: dts: aspeed: Minerva: Add Facebook Minerva (AST2600) BMC
dt-bindings: arm: aspeed: add Meta Minerva board
.../bindings/arm/aspeed/aspeed.yaml | 1 +
arch/arm/boot/dts/aspeed/Makefile | 1 +
.../aspeed/aspeed-bmc-facebook-minerva.dts | 377 ++++++++++++++++++
3 files changed, 379 insertions(+)
create mode 100644 arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-minerva.dts
--
2.25.1
next reply other threads:[~2023-09-05 16:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 6:22 Peter Yin [this message]
2023-09-05 6:22 ` [PATCH v8 1/2] ARM: dts: aspeed: Minerva: Add Facebook Minerva (AST2600) BMC Peter Yin
2023-09-06 1:57 ` kernel test robot
2023-09-05 6:22 ` [PATCH v8 2/2] dt-bindings: arm: aspeed: add Meta Minerva board Peter Yin
2023-09-05 18:16 ` Rob Herring
2023-09-06 2:08 ` PeterYin
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=20230905062223.774871-1-peteryin.openbmc@gmail.com \
--to=peteryin.openbmc@gmail.com \
--cc=andrew@aj.id.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick@stwcx.xyz \
--cc=peter.yin@quantatw.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).