mbox series

[v5,0/6] Add support for Blaize BLZP1600 SoC

Message ID 20241115-blaize-blzp1600_init_board_support-v5-0-c09094e63dc5@blaize.com (mailing list archive)
Headers show
Series Add support for Blaize BLZP1600 SoC | expand

Message

Nikolaos Pasaloukos Nov. 15, 2024, 2:58 p.m. UTC
Blaize, Inc. (www.blaize.com) is a SoC designer and manufacturer
with integrated programmable Graph-Streaming-Processors for AI
and ML. This series adds support for the Blaize BLZP1600 SoC.

The SoC can run as either a PCIe based accelerator in a host
system, or as a stand alone SoC running Linux on its integrated
dual core ARM Cortex A53 cluster.

The SoC includes a suite of peripherals, support for which will
be added later.

This first series is just the basics to get the upstream
kernel to boot with a UART console and ARM SCMI based
clocks and resets.

V5 changes:
 * Add more information on patches and on files
 * Rename arch to ARCH_BLAIZE

V4 changes:
 * Add maintainer for blaize in arm64 dts
 * Fix Blaize schema & dts code style
 * Add range and reserved-memory as suggested

V3 changes:
 * Removed unnecessary dt-bindings
 * Update SoBs

V2 changes:
 * Update SoBs
 * `make dtbs_check` has no warnings
 * Fix dts names and removed dead code
 * DTS is separated from anything else

Signed-off-by: Nikolaos Pasaloukos <nikolaos.pasaloukos@blaize.com>
---
Nikolaos Pasaloukos (6):
      dt-bindings: Add Blaize vendor prefix
      dt-bindings: arm: blaize: Add Blaize BLZP1600 SoC
      arm64: Add Blaize BLZP1600 SoC family
      arm64: Add initial support for Blaize BLZP1600 CB2
      arm64: defconfig: Enable Blaize BLZP1600 platform
      MAINTAINER: Add entry for Blaize SoC

 Documentation/devicetree/bindings/arm/blaize.yaml  |  40 ++++
 .../devicetree/bindings/vendor-prefixes.yaml       |   2 +
 MAINTAINERS                                        |   9 +
 arch/arm64/Kconfig.platforms                       |   5 +
 arch/arm64/boot/dts/Makefile                       |   1 +
 arch/arm64/boot/dts/blaize/Makefile                |   2 +
 arch/arm64/boot/dts/blaize/blaize-blzp1600-cb2.dts |  83 +++++++++
 .../arm64/boot/dts/blaize/blaize-blzp1600-som.dtsi |  23 +++
 arch/arm64/boot/dts/blaize/blaize-blzp1600.dtsi    | 205 +++++++++++++++++++++
 arch/arm64/configs/defconfig                       |   1 +
 10 files changed, 371 insertions(+)
---
base-commit: 83d67c257f4d045ff477309b5617d931f9a7be66
change-id: 20241111-blaize-blzp1600_init_board_support-1128194ca976

Best regards,

Comments

Arnd Bergmann Nov. 15, 2024, 3:09 p.m. UTC | #1
On Fri, Nov 15, 2024, at 15:58, Niko Pasaloukos wrote:
> Blaize, Inc. (www.blaize.com) is a SoC designer and manufacturer
> with integrated programmable Graph-Streaming-Processors for AI
> and ML. This series adds support for the Blaize BLZP1600 SoC.
>
> The SoC can run as either a PCIe based accelerator in a host
> system, or as a stand alone SoC running Linux on its integrated
> dual core ARM Cortex A53 cluster.
>
> The SoC includes a suite of peripherals, support for which will
> be added later.
>
> This first series is just the basics to get the upstream
> kernel to boot with a UART console and ARM SCMI based
> clocks and resets.
>

Hi Niko,

This version looks good to me, but it's likely that others
still have review comments. Either way I should let you know
of the next steps for merging the series.

Since the 6.13 development cycle is now over (the
merge window starts once Linus publishes 6.12
this weekend), the earliest release to merge this
into is now 6.14.

Once 6.13-rc1 is out and the patch review is complete,
you can submit the patches for inclusion by sending
to:soc@lists.linux.dev (formerly soc@kernel.org).
This is usually done as a pull request, but separate
patches are fine as well, especially if you don't yet
have a kernel.org account.

After the entry to the MAINTAINERS file is merged,
I suggest you also apply for a kernel.org account,
see [1]. You probably also read the documentation at
[2] about the usual process, let me know if you
have questions about that.

       Arnd

[1] https://korg.docs.kernel.org/accounts.html
[2] https://www.kernel.org/doc/Documentation/process/maintainer-soc.rst
Nikolaos Pasaloukos Nov. 19, 2024, 12:47 p.m. UTC | #2
On 15/11/2024 15:09, Arnd Bergmann wrote:

> On Fri, Nov 15, 2024, at 15:58, Niko Pasaloukos wrote:
>> Blaize, Inc. (http://www.blaize.com) is a SoC designer and manufacturer
>> with integrated programmable Graph-Streaming-Processors for AI
>> and ML. This series adds support for the Blaize BLZP1600 SoC.
>>
>> The SoC can run as either a PCIe based accelerator in a host
>> system, or as a stand alone SoC running Linux on its integrated
>> dual core ARM Cortex A53 cluster.
>>
>> The SoC includes a suite of peripherals, support for which will
>> be added later.
>>
>> This first series is just the basics to get the upstream
>> kernel to boot with a UART console and ARM SCMI based
>> clocks and resets.
>>
> Hi Niko,
>
> This version looks good to me, but it's likely that others
> still have review comments. Either way I should let you know
> of the next steps for merging the series.
>
> Since the 6.13 development cycle is now over (the
> merge window starts once Linus publishes 6.12
> this weekend), the earliest release to merge this
> into is now 6.14.
>
> Once 6.13-rc1 is out and the patch review is complete,
> you can submit the patches for inclusion by sending
> to:soc@lists.linux.dev (formerly soc@kernel.org).
> This is usually done as a pull request, but separate
> patches are fine as well, especially if you don't yet
> have a kernel.org account.
>
> After the entry to the MAINTAINERS file is merged,
> I suggest you also apply for a kernel.org account,
> see [1]. You probably also read the documentation at
> [2] about the usual process, let me know if you
> have questions about that.
>
>         Arnd
>
> [1] https://urldefense.com/v3/__https://korg.docs.kernel.org/accounts.html__;!!FddXBOku!ny-gN1hGaRTxNpi1ADJf_s3xLmuIdAZzGy4uj6kacOw-p3lLhZfSFLF2Mb9UcuIbd1By_ERGVnHqEbEiXhbK1g$
> [2] https://urldefense.com/v3/__https://www.kernel.org/doc/Documentation/process/maintainer-soc.rst__;!!FddXBOku!ny-gN1hGaRTxNpi1ADJf_s3xLmuIdAZzGy4uj6kacOw-p3lLhZfSFLF2Mb9UcuIbd1By_ERGVnHqEbHSKH7PdA$

Hi Arnd,

Thank you very much for the detailed explanation of the merging process and release
cycles.
Also, I would like to thank all the people who help me during the review process
and for their helpful comments.

Best regards,
Niko