Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: Pufan Jin <cyan2254650260@gmail.com>,
	Conor Dooley <conor+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH v3 0/2] ARM: dts: zynq: Add ALINX AX7Z020B development board
Date: Fri, 13 Nov 2026 14:05:43 +0100	[thread overview]
Message-ID: <45adea9b-be14-4954-8335-267dba33afbe@amd.com> (raw)
In-Reply-To: <20261112193245.250149-1-cyan2254650260@gmail.com>



On 11/12/26 20:32, Pufan Jin wrote:
> Add devicetree support for the ALINX AX7Z020B board, built around the
> ALINX AC7Z020 system on module with a Zynq-7000 (XC7Z020-2CLG400I) SoC.
> 
> Changes in v3:
> - Drop the vendor website Link: tags (Krzysztof Kozlowski).
> - Drop the empty bootargs property (Krzysztof Kozlowski).
> - Rename the USB PHY node from phy0 to phy, as there is only one USB PHY
>    on the board (Krzysztof Kozlowski).
> - Keep the explicit mdio node under gem0, as requested during the v1
>    review and reviewed by Andrew Lunn in v2.  dtc W=1 flags the parent
>    node's inherited #address-cells/#size-cells.  DT schema validation
>    reports the same Zynq-7000 diagnostics as zynq-zybo-z7.  The MDIO
>    layout was also verified on hardware.
> - Sort I2C child nodes by address and reorder status/reg properties.
> - Add Krzysztof's Acked-by to patch 1.
> 
> The "alinx" vendor prefix is already queued in linux-next as commit
> 1f06cd374a60 ("dt-bindings: vendor-prefixes: Add ALINX vendor prefix"),
> so it is not part of this series.
> 
> Tested on hardware before the DTS style reordering: SD boot, UART
> console, SD card, GbE (900+ Mbps and LED hardware offload), dual CAN,
> I2C, QSPI and XADC.
> 
> Pufan Jin (2):
>    dt-bindings: soc: xilinx: Add ALINX AX7Z020B board
>    ARM: dts: zynq: Add ALINX AX7Z020B development board
> 
>   .../bindings/soc/xilinx/xilinx.yaml           |   5 +
>   arch/arm/boot/dts/xilinx/Makefile             |   1 +
>   .../boot/dts/xilinx/zynq-alinx-ac7z020.dtsi   |  71 +++++++++
>   .../boot/dts/xilinx/zynq-alinx-ax7z020b.dts   | 146 ++++++++++++++++++
>   4 files changed, 223 insertions(+)
>   create mode 100644 arch/arm/boot/dts/xilinx/zynq-alinx-ac7z020.dtsi
>   create mode 100644 arch/arm/boot/dts/xilinx/zynq-alinx-ax7z020b.dts
Applied.
M


      parent reply	other threads:[~2026-11-13 13:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-12 19:32 [PATCH v3 0/2] ARM: dts: zynq: Add ALINX AX7Z020B development board Pufan Jin
2026-11-12 19:32 ` [PATCH v3 1/2] dt-bindings: soc: xilinx: Add ALINX AX7Z020B board Pufan Jin
2026-11-12 19:32 ` [PATCH v3 2/2] ARM: dts: zynq: Add ALINX AX7Z020B development board Pufan Jin
2026-11-13 13:05 ` 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=45adea9b-be14-4954-8335-267dba33afbe@amd.com \
    --to=michal.simek@amd.com \
    --cc=andrew@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=cyan2254650260@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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