mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rob Herring (Arm)" <robh@kernel.org>
To: niravkumar.l.rabara@intel.com
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Dinh Nguyen <dinguyen@kernel.org>,
	linux-kernel@vger.kernel.org,  Conor Dooley <conor+dt@kernel.org>,
	devicetree@vger.kernel.org,  nirav.rabara@altera.com
Subject: Re: [PATCH v3 0/2] arm64: dts: socfpga: agilex5: add NAND daughter board
Date: Mon, 10 Feb 2025 10:22:45 -0600	[thread overview]
Message-ID: <173920412142.477451.9950583431294395280.robh@kernel.org> (raw)
In-Reply-To: <20250210074604.2410783-1-niravkumar.l.rabara@intel.com>


On Mon, 10 Feb 2025 15:46:02 +0800, 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
> 
> --
> 2.25.1
> 
> 
> 


My bot found new DTB warnings on the .dts files added or changed in this
series.

Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
are fixed by another series. Ultimately, it is up to the platform
maintainer whether these warnings are acceptable or not. No need to reply
unless the platform maintainer has comments.

If you already ran DT checks and didn't see these error(s), then
make sure dt-schema is up to date:

  pip3 install dtschema --upgrade


New warnings running 'make CHECK_DTBS=y for arch/arm64/boot/dts/intel/' for 20250210074604.2410783-1-niravkumar.l.rabara@intel.com:

arch/arm64/boot/dts/intel/socfpga_n5x_socdk.dtb: clock-controller@ffd10000: 'clocks' is a required property
	from schema $id: http://devicetree.org/schemas/clock/intel,easic-n5x.yaml#






  parent reply	other threads:[~2025-02-10 16:22 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 ` Rob Herring (Arm) [this message]
2025-02-11 12:55 ` [PATCH v3 0/2] " Dinh Nguyen

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=173920412142.477451.9950583431294395280.robh@kernel.org \
    --to=robh@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dinguyen@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nirav.rabara@altera.com \
    --cc=niravkumar.l.rabara@intel.com \
    /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®