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/5] ARM: dts: aspeed: Add Facebook Wedge400 (AST2500) BMC
Date: Mon, 24 Aug 2020 14:19:43 -0700 [thread overview]
Message-ID: <20200824211948.12852-1-rentao.bupt@gmail.com> (raw)
From: Tao Ren <rentao.bupt@gmail.com>
The patch series adds Facebook Wedge400 (AST2500) BMC device tree, and
FMC flash layout is re-structured because flash size and layout varies
across different Facebook AST2500 OpenBMC platforms.
Patch #1 removes flash layout from ast2500-facebook-netbmc-common.dtsi
because now we have 32MB, 64MB an 128MB flashes on different Facebook
AST2500 OpenBMC platforms.
Patch #2, #3 and #4 sets FMC flash layout in CMM, Yamp and Minipack
device tree explicitly because the original layout settings were removed
from ast2500-facebook-netbmc-common.dtsi (in patch #1).
Patch #5 adds Facebook Wedge400 AST2500 BMC device tree.
Tao Ren (5):
ARM: dts: aspeed: Remove flash layout from Facebook AST2500 Common
dtsi
ARM: dts: aspeed: cmm: Set 32MB FMC flash layout
ARM: dts: aspeed: yamp: Set 32MB FMC flash layout
ARM: dts: aspeed: minipack: Update 64MB FMC flash layout
ARM: dts: aspeed: Add Facebook Wedge400 BMC
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/aspeed-bmc-facebook-cmm.dts | 17 +
.../boot/dts/aspeed-bmc-facebook-minipack.dts | 47 +-
.../boot/dts/aspeed-bmc-facebook-wedge400.dts | 420 ++++++++++++++++++
.../arm/boot/dts/aspeed-bmc-facebook-yamp.dts | 17 +
.../dts/ast2500-facebook-netbmc-common.dtsi | 13 -
6 files changed, 500 insertions(+), 15 deletions(-)
create mode 100644 arch/arm/boot/dts/aspeed-bmc-facebook-wedge400.dts
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-08-24 21:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 21:19 rentao.bupt [this message]
2020-08-24 21:19 ` [PATCH 1/5] ARM: dts: aspeed: Remove flash layout from Facebook AST2500 Common dtsi rentao.bupt
2020-08-25 14:16 ` Patrick Williams
2020-08-24 21:19 ` [PATCH 2/5] ARM: dts: aspeed: cmm: Set 32MB FMC flash layout rentao.bupt
2020-08-25 14:16 ` Patrick Williams
2020-08-24 21:19 ` [PATCH 3/5] ARM: dts: aspeed: yamp: " rentao.bupt
2020-08-25 14:17 ` Patrick Williams
2020-08-24 21:19 ` [PATCH 4/5] ARM: dts: aspeed: minipack: Update 64MB " rentao.bupt
2020-08-25 14:18 ` Patrick Williams
2020-08-25 20:26 ` Tao Ren
2020-08-24 21:19 ` [PATCH 5/5] ARM: dts: aspeed: Add Facebook Wedge400 BMC rentao.bupt
2020-08-25 4:07 ` Joel Stanley
2020-08-25 20:17 ` Tao Ren
[not found] ` <20231220082714.GA17989@wunner.de>
2024-01-03 6:04 ` Tao Ren
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=20200824211948.12852-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).