From: Michal Simek <monstr@monstr.eu>
To: linux-kernel@vger.kernel.org, monstr@monstr.eu,
michal.simek@xilinx.com, git@xilinx.com
Cc: Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"moderated list:ARM/ZYNQ ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/3] arm64: zynqmp: Add support for kr260 and kd240
Date: Fri, 1 Aug 2025 13:24:38 +0200 [thread overview]
Message-ID: <64e24ac1-e0dc-4d0c-a9ab-8bb26f5acdcb@monstr.eu> (raw)
In-Reply-To: <cover.1752837842.git.michal.simek@amd.com>
On 7/18/25 13:24, Michal Simek wrote:
> Hi,
>
> add description for k24 and kr260 with kd240 boards.
> Pretty much both k24 and k26 SOMs can be plugged to other carrier cards but
> not all combinations are tested together.
>
> Thanks,
> Michal
>
>
> Michal Simek (3):
> dt-bindings: soc: xilinx: Add support for K24, KR260 and KD240 CCs
> arm64: zynqmp: Add support for kr260 board
> arm64: zynqmp: Add support for kd240 board
>
> .../bindings/soc/xilinx/xilinx.yaml | 81 ++++
> arch/arm64/boot/dts/xilinx/Makefile | 24 +
> .../boot/dts/xilinx/zynqmp-sck-kd-g-revA.dtso | 390 +++++++++++++++
> .../boot/dts/xilinx/zynqmp-sck-kr-g-revA.dtso | 438 +++++++++++++++++
> .../boot/dts/xilinx/zynqmp-sck-kr-g-revB.dtso | 451 ++++++++++++++++++
> .../boot/dts/xilinx/zynqmp-sm-k24-revA.dts | 23 +
> .../boot/dts/xilinx/zynqmp-smk-k24-revA.dts | 21 +
> 7 files changed, 1428 insertions(+)
> create mode 100644 arch/arm64/boot/dts/xilinx/zynqmp-sck-kd-g-revA.dtso
> create mode 100644 arch/arm64/boot/dts/xilinx/zynqmp-sck-kr-g-revA.dtso
> create mode 100644 arch/arm64/boot/dts/xilinx/zynqmp-sck-kr-g-revB.dtso
> create mode 100644 arch/arm64/boot/dts/xilinx/zynqmp-sm-k24-revA.dts
> create mode 100644 arch/arm64/boot/dts/xilinx/zynqmp-smk-k24-revA.dts
>
Applied.
M
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP/Versal ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP/Versal/Versal NET SoCs
TF-A maintainer - Xilinx ZynqMP/Versal/Versal NET SoCs
prev parent reply other threads:[~2025-08-01 11:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 11:24 [PATCH 0/3] arm64: zynqmp: Add support for kr260 and kd240 Michal Simek
2025-07-18 11:24 ` [PATCH 1/3] dt-bindings: soc: xilinx: Add support for K24, KR260 and KD240 CCs Michal Simek
2025-07-21 0:36 ` Rob Herring (Arm)
2025-07-18 11:24 ` [PATCH 2/3] arm64: zynqmp: Add support for kr260 board Michal Simek
2025-07-18 11:24 ` [PATCH 3/3] arm64: zynqmp: Add support for kd240 board Michal Simek
2025-08-12 14:24 ` Rob Herring
2025-08-18 7:35 ` Michal Simek
2025-08-01 11:24 ` Michal Simek [this message]
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=64e24ac1-e0dc-4d0c-a9ab-8bb26f5acdcb@monstr.eu \
--to=monstr@monstr.eu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=git@xilinx.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--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).