From: Krzysztof Kozlowski <krzk@kernel.org>
To: Eddie James <eajames@linux.ibm.com>, linux-aspeed@lists.ozlabs.org
Cc: devicetree@vger.kernel.org, andrew@codeconstruct.com.au,
joel@jms.id.au, conor+dt@kernel.org, krzk+dt@kernel.org,
robh@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/4] ARM: dts: aspeed: Add IBM P11 Blueridge BMC system
Date: Wed, 15 May 2024 16:11:21 +0200 [thread overview]
Message-ID: <52bf83a5-f62a-4758-999b-9245d4a0ceab@kernel.org> (raw)
In-Reply-To: <20240514213510.159144-3-eajames@linux.ibm.com>
On 14/05/2024 23:35, Eddie James wrote:
> Add the device tree for the new BMC system. The Blueridge is a
> P11 system with four processors.
>
> Signed-off-by: Eddie James <eajames@linux.ibm.com>
> ---
> arch/arm/boot/dts/aspeed/Makefile | 1 +
> .../dts/aspeed/aspeed-bmc-ibm-blueridge.dts | 1691 +++++++++++++++++
> 2 files changed, 1692 insertions(+)
> create mode 100644 arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-blueridge.dts
>
> diff --git a/arch/arm/boot/dts/aspeed/Makefile b/arch/arm/boot/dts/aspeed/Makefile
> index e51c6d2037255..f3db9ee156429 100644
> --- a/arch/arm/boot/dts/aspeed/Makefile
> +++ b/arch/arm/boot/dts/aspeed/Makefile
> @@ -32,6 +32,7 @@ dtb-$(CONFIG_ARCH_ASPEED) += \
> aspeed-bmc-facebook-yamp.dtb \
> aspeed-bmc-facebook-yosemitev2.dtb \
> aspeed-bmc-facebook-yosemite4.dtb \
> + aspeed-bmc-ibm-blueridge.dtb \
> aspeed-bmc-ibm-bonnell.dtb \
> aspeed-bmc-ibm-everest.dtb \
> aspeed-bmc-ibm-rainier.dtb \
> diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-blueridge.dts b/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-blueridge.dts
> new file mode 100644
> index 0000000000000..418eaf0a46146
> --- /dev/null
> +++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-blueridge.dts
> @@ -0,0 +1,1691 @@
> +// SPDX-License-Identifier: GPL-2.0-or-later
> +// Copyright 2024 IBM Corp.
> +/dts-v1/;
> +
> +#include <dt-bindings/gpio/aspeed-gpio.h>
> +#include <dt-bindings/i2c/i2c.h>
> +#include <dt-bindings/leds/leds-pca955x.h>
> +#include "aspeed-g6.dtsi"
> +#include "ibm-power11-quad.dtsi"
> +
> +/ {
> + model = "Blueridge";
> + compatible = "ibm,blueridge-bmc", "aspeed,ast2600";
Undocumented binding.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-05-15 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 21:35 [PATCH v5 0/4] ARM: dts: aspeed: Add IBM P11 BMC systems Eddie James
2024-05-14 21:35 ` [PATCH v5 1/4] ARM: dts: aspeed: Add IBM P11 FSI devices Eddie James
2024-05-14 21:35 ` [PATCH v5 2/4] ARM: dts: aspeed: Add IBM P11 Blueridge BMC system Eddie James
2024-05-15 14:11 ` Krzysztof Kozlowski [this message]
2024-05-14 21:35 ` [PATCH v5 3/4] ARM: dts: aspeed: Add IBM P11 Blueridge 4U " Eddie James
2024-05-14 21:35 ` [PATCH v5 4/4] ARM: dts: aspeed: Add IBM P11 Fuji " Eddie James
2024-05-15 13:13 ` [PATCH v5 0/4] ARM: dts: aspeed: Add IBM P11 BMC systems Rob Herring (Arm)
2024-05-15 14:10 ` Krzysztof Kozlowski
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=52bf83a5-f62a-4758-999b-9245d4a0ceab@kernel.org \
--to=krzk@kernel.org \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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).