From: rentao.bupt@gmail.com
To: Rob Herring <robh+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,
openbmc@lists.ozlabs.org, taoren@fb.com
Cc: Tao Ren <rentao.bupt@gmail.com>
Subject: [PATCH 0/6] ARM: dts: Add Facebook AST2600 BMCs
Date: Wed, 28 Jul 2021 16:37:49 -0700 [thread overview]
Message-ID: <20210728233755.17963-1-rentao.bupt@gmail.com> (raw)
From: Tao Ren <rentao.bupt@gmail.com>
The patch series introuces 3 new Facebook AST2600 Network BMC platforms.
Patch #1 adds dtsi file to describe the fixed flash layout of 128MB mtd
device. The flash layout is used by all the 3 AST2600 BMC as well as
Wedge400 (AST2500).
Patch #2 simplies Wedge400 dts by including the flash layout dtsi.
Patch #3 adds common dtsi which is included by all the new Facebook
AST2600 Network BMC platforms.
Patch #4 adds the device tree for Facebook Cloudripper (AST2600) BMC.
Patch #5 adds the device tree for Facebook Elbert (AST2600) BMC.
Patch #6 adds the device tree for Facebook Fuji (AST2600) BMC.
Tao Ren (6):
ARM: dts: Add Facebook BMC 128MB flash layout
ARM: dts: aspeed: wedge400: Use common flash layout
ARM: dts: aspeed: Common dtsi for Facebook AST2600 Network BMCs
ARM: dts: aspeed: Add Facebook Cloudripper (AST2600) BMC
ARM: dts: aspeed: Add Facebook Elbert (AST2600) BMC
ARM: dts: aspeed: Add Facebook Fuji (AST2600) BMC
arch/arm/boot/dts/Makefile | 3 +
.../dts/aspeed-bmc-facebook-cloudripper.dts | 564 ++++++++
.../boot/dts/aspeed-bmc-facebook-elbert.dts | 185 +++
.../arm/boot/dts/aspeed-bmc-facebook-fuji.dts | 1276 +++++++++++++++++
.../boot/dts/aspeed-bmc-facebook-wedge400.dts | 48 +-
.../dts/ast2600-facebook-netbmc-common.dtsi | 176 +++
.../dts/facebook-bmc-flash-layout-128.dtsi | 60 +
7 files changed, 2265 insertions(+), 47 deletions(-)
create mode 100644 arch/arm/boot/dts/aspeed-bmc-facebook-cloudripper.dts
create mode 100644 arch/arm/boot/dts/aspeed-bmc-facebook-elbert.dts
create mode 100644 arch/arm/boot/dts/aspeed-bmc-facebook-fuji.dts
create mode 100644 arch/arm/boot/dts/ast2600-facebook-netbmc-common.dtsi
create mode 100644 arch/arm/boot/dts/facebook-bmc-flash-layout-128.dtsi
--
2.17.1
next reply other threads:[~2021-07-28 23:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 23:37 rentao.bupt [this message]
2021-07-28 23:37 ` [PATCH 1/6] ARM: dts: Add Facebook BMC 128MB flash layout rentao.bupt
2021-07-28 23:37 ` [PATCH 2/6] ARM: dts: aspeed: wedge400: Use common " rentao.bupt
2021-07-28 23:37 ` [PATCH 3/6] ARM: dts: aspeed: Common dtsi for Facebook AST2600 Network BMCs rentao.bupt
2021-07-28 23:37 ` [PATCH 4/6] ARM: dts: aspeed: Add Facebook Cloudripper (AST2600) BMC rentao.bupt
2021-07-28 23:37 ` [PATCH 5/6] ARM: dts: aspeed: Add Facebook Elbert " rentao.bupt
2021-07-28 23:37 ` [PATCH 6/6] ARM: dts: aspeed: Add Facebook Fuji " rentao.bupt
2021-08-05 0:28 ` Joel Stanley
2021-08-05 1:19 ` Tao Ren
2021-08-05 1:37 ` Joel Stanley
2021-08-05 2:09 ` Tao Ren
2021-08-05 2:17 ` Joel Stanley
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=20210728233755.17963-1-rentao.bupt@gmail.com \
--to=rentao.bupt@gmail.com \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=robh+dt@kernel.org \
--cc=taoren@fb.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;
as well as URLs for NNTP newsgroup(s).