From: Dinh Nguyen <dinguyen@kernel.org>
To: niravkumar.l.rabara@intel.com, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
nirav.rabara@altera.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] arm64: dts: socfpga: agilex5: add NAND daughter board
Date: Tue, 11 Feb 2025 06:55:24 -0600 [thread overview]
Message-ID: <d3712a1b-48da-4d94-82a9-e7f627dead3f@kernel.org> (raw)
In-Reply-To: <20250210074604.2410783-1-niravkumar.l.rabara@intel.com>
On 2/10/25 01:46, niravkumar.l.rabara@intel.com wrote:
> From: Niravkumar L Rabara <niravkumar.l.rabara@intel.com>
>
> Agilex5 SoCFPGA devkit supports a separate NAND daughter board.
> Document NAND daughter board compatible string and add board file.
>
> Changes in v3:
> * Document Agilex5 NAND daughter board and use that compatible
> in the device tree.
>
> link to v2:
> - https://lore.kernel.org/all/20250205101318.1778757-1-niravkumar.l.rabara@intel.com/
>
> Changes in v2:
> * Use nand flash node name according to dt bindings to fix dt build warnings.
> * Arrange node in sequence.
>
> link to v1:
> - https://lore.kernel.org/all/20250107084831.2750035-1-niravkumar.l.rabara@intel.com/
>
> Niravkumar L Rabara (2):
> dt-bindings: intel: document Agilex5 NAND daughter board
> arm64: dts: socfpga: agilex5: add NAND daughter board
>
> .../bindings/arm/intel,socfpga.yaml | 1 +
> arch/arm64/boot/dts/intel/Makefile | 1 +
> .../dts/intel/socfpga_agilex5_socdk_nand.dts | 89 +++++++++++++++++++
> 3 files changed, 91 insertions(+)
> create mode 100644 arch/arm64/boot/dts/intel/socfpga_agilex5_socdk_nand.dts
>
Applied!
Thanks,
Dinh
prev parent reply other threads:[~2025-02-11 12:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 7:46 niravkumar.l.rabara
2025-02-10 7:46 ` [PATCH v3 1/2] dt-bindings: intel: document Agilex5 " niravkumar.l.rabara
2025-02-11 8:50 ` Krzysztof Kozlowski
2025-02-10 7:46 ` [PATCH v3 2/2] arm64: dts: socfpga: agilex5: add " niravkumar.l.rabara
2025-02-11 8:51 ` Krzysztof Kozlowski
2025-02-10 16:22 ` [PATCH v3 0/2] " Rob Herring (Arm)
2025-02-11 12:55 ` Dinh Nguyen [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=d3712a1b-48da-4d94-82a9-e7f627dead3f@kernel.org \
--to=dinguyen@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nirav.rabara@altera.com \
--cc=niravkumar.l.rabara@intel.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
all inboxes | Powered by JetHome®