From: Rob Herring <robh@kernel.org>
To: Niko Pasaloukos <nikolaos.pasaloukos@blaize.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"soc@kernel.org" <soc@kernel.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"olof@lixom.net" <olof@lixom.net>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"sboyd@kernel.org" <sboyd@kernel.org>,
James Cowgill <james.cowgill@blaize.com>,
Matt Redfearn <matthew.redfearn@blaize.com>,
Neil Jones <neil.jones@blaize.com>
Subject: Re: [PATCH 5/5] arm64: Add initial support for Blaize BLZP1600 CB2
Date: Wed, 12 Apr 2023 09:03:44 -0500 [thread overview]
Message-ID: <20230412140344.GA2234522-robh@kernel.org> (raw)
In-Reply-To: <20230406102149.729726-6-nikolaos.pasaloukos@blaize.com>
On Thu, Apr 06, 2023 at 10:22:32AM +0000, Niko Pasaloukos wrote:
> Adds support for the Blaize CB2 development board based on
> BLZP1600 SoC. This consists of a Carrier-Board and a SoM.
>
> The blaize-blzp1600.dtsi is the common part for the SoC,
> blaize-blzp1600-som.dtsi is the common part for the SoM and
> blaize-blzp1600-som-cb2.dts is the board specific file.
>
> Co-developed-by: James Cowgill <james.cowgill@blaize.com>
> Signed-off-by: James Cowgill <james.cowgill@blaize.com>
> Co-developed-by: Matt Redfearn <matt.redfearn@blaize.com>
> Signed-off-by: Matt Redfearn <matt.redfearn@blaize.com>
> Co-developed-by: Neil Jones <neil.jones@blaize.com>
> Signed-off-by: Neil Jones <neil.jones@blaize.com>
> Signed-off-by: Nikolaos Pasaloukos <nikolaos.pasaloukos@blaize.com>
> ---
> arch/arm64/Kconfig.platforms | 5 +
> arch/arm64/boot/dts/Makefile | 1 +
> arch/arm64/boot/dts/blaize/Makefile | 2 +
> .../dts/blaize/blaize-blzp1600-som-cb.dtsi | 217 +++++
> .../dts/blaize/blaize-blzp1600-som-cb2.dts | 103 ++
> .../boot/dts/blaize/blaize-blzp1600-som.dtsi | 104 ++
> .../boot/dts/blaize/blaize-blzp1600.dtsi | 894 ++++++++++++++++++
> arch/arm64/configs/defconfig | 1 +
> 8 files changed, 1327 insertions(+)
> create mode 100644 arch/arm64/boot/dts/blaize/Makefile
> create mode 100644 arch/arm64/boot/dts/blaize/blaize-blzp1600-som-cb.dtsi
> create mode 100644 arch/arm64/boot/dts/blaize/blaize-blzp1600-som-cb2.dts
> create mode 100644 arch/arm64/boot/dts/blaize/blaize-blzp1600-som.dtsi
> create mode 100644 arch/arm64/boot/dts/blaize/blaize-blzp1600.dtsi
New platforms should be free of warnings from 'make dtbs_check'. Please
run and fix if you have not, and confirm that in the commit message.
Rob
next prev parent reply other threads:[~2023-04-12 14:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 10:22 [PATCH 0/5] Add support for Blaize BLZP1600 SoC Niko Pasaloukos
2023-04-06 10:22 ` [PATCH 1/5] dt-bindings: Add Blaize vendor prefix Niko Pasaloukos
2023-04-06 17:21 ` Krzysztof Kozlowski
2023-04-06 10:22 ` [PATCH 2/5] dt-bindings: arm: blaize: Add Blaize BLZP1600 SoC Niko Pasaloukos
2023-04-06 17:22 ` Krzysztof Kozlowski
2023-04-06 10:22 ` [PATCH 3/5] dt-bindings: reset: Add binding constants for BLZP1600 Niko Pasaloukos
2023-04-06 17:23 ` Krzysztof Kozlowski
2023-04-06 10:22 ` [PATCH 5/5] arm64: Add initial support for Blaize BLZP1600 CB2 Niko Pasaloukos
2023-04-06 17:31 ` Krzysztof Kozlowski
2023-04-12 14:03 ` Rob Herring [this message]
2023-04-06 10:22 ` [PATCH 4/5] dt-bindings: clock: Add binding constants for BLZP1600 Niko Pasaloukos
2023-04-06 17:24 ` Krzysztof Kozlowski
2023-04-06 17:34 ` [PATCH 0/5] Add support for Blaize BLZP1600 SoC 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=20230412140344.GA2234522-robh@kernel.org \
--to=robh@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=james.cowgill@blaize.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.redfearn@blaize.com \
--cc=neil.jones@blaize.com \
--cc=nikolaos.pasaloukos@blaize.com \
--cc=olof@lixom.net \
--cc=p.zabel@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=soc@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).