All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Niko Pasaloukos <nikolaos.pasaloukos@blaize.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	James Cowgill <james.cowgill@blaize.com>,
	Matt Redfearn <matthew.redfearn@blaize.com>,
	Neil Jones <neil.jones@blaize.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
	Olof Johansson <olof@lixom.net>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"soc@lists.linux.dev" <soc@lists.linux.dev>
Subject: Re: [PATCH v5 4/6] arm64: Add initial support for Blaize BLZP1600 CB2
Date: Tue, 19 Nov 2024 14:02:51 +0100	[thread overview]
Message-ID: <4483a757-db62-4489-aac0-7a33d44a4cba@kernel.org> (raw)
In-Reply-To: <20241115-blaize-blzp1600_init_board_support-v5-4-c09094e63dc5@blaize.com>

On 15/11/2024 15:58, Niko Pasaloukos wrote:
> Add support for the Blaize CB2 development board based on
> the BLZP1600 SoC. This consists of a Carrier-Board-2 and a
> System-on-Module.
> 
> Both BLZP1600 SoM and CB2 are available as products.
> CB2 (Pathfinder) has multiple peripherals like UART, I2C,
> SPI, GPIO, CSI (camera), DSI (display), USB-3.0 and Ethernet.
> 
> Enable support for the Cryptocell, UART and I2C which are
> already fully supported by the drivers.
> 
> 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-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>

Subject prefix should be:
arm64: dts:
or

arm64: dts: blaize:

Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>

Best regards,
Krzysztof


  reply	other threads:[~2024-11-19 13:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-15 14:58 [PATCH v5 0/6] Add support for Blaize BLZP1600 SoC Niko Pasaloukos
2024-11-15 14:58 ` [PATCH v5 1/6] dt-bindings: Add Blaize vendor prefix Niko Pasaloukos
2024-11-19 13:05   ` Krzysztof Kozlowski
2024-11-19 13:33     ` Nikolaos Pasaloukos
2024-11-19 13:37       ` Krzysztof Kozlowski
2024-11-19 15:23         ` Nikolaos Pasaloukos
2024-11-19 15:52           ` Krzysztof Kozlowski
2024-11-19 16:23             ` Nikolaos Pasaloukos
2024-11-15 14:58 ` [PATCH v5 2/6] dt-bindings: arm: blaize: Add Blaize BLZP1600 SoC Niko Pasaloukos
2024-11-19 13:00   ` Krzysztof Kozlowski
2024-11-15 14:58 ` [PATCH v5 3/6] arm64: Add Blaize BLZP1600 SoC family Niko Pasaloukos
2024-11-19 13:03   ` Krzysztof Kozlowski
2024-11-15 14:58 ` [PATCH v5 4/6] arm64: Add initial support for Blaize BLZP1600 CB2 Niko Pasaloukos
2024-11-19 13:02   ` Krzysztof Kozlowski [this message]
2024-11-15 14:58 ` [PATCH v5 5/6] arm64: defconfig: Enable Blaize BLZP1600 platform Niko Pasaloukos
2024-11-19 13:03   ` Krzysztof Kozlowski
2024-11-15 14:58 ` [PATCH v5 6/6] MAINTAINER: Add entry for Blaize SoC Niko Pasaloukos
2024-11-15 15:09 ` [PATCH v5 0/6] Add support for Blaize BLZP1600 SoC Arnd Bergmann
2024-11-19 12:47   ` Nikolaos Pasaloukos

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=4483a757-db62-4489-aac0-7a33d44a4cba@kernel.org \
    --to=krzk@kernel.org \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=james.cowgill@blaize.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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=robh@kernel.org \
    --cc=soc@lists.linux.dev \
    --cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.