Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: Frank Li <Frank.Li@nxp.com>
To: Vladimir Zapolskiy <vz@mleia.com>,
	Piotr Wojtaszczyk <piotr.wojtaszczyk@timesys.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-arm-kernel@lists.infradead.org (moderated list:ARM/LPC32XX
	SOC SUPPORT),
	devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND
	FLATTENED DEVICE TREE BINDINGS),
	linux-kernel@vger.kernel.org (open list)
Cc: imx@lists.linux.dev
Subject: [PATCH 4/5] ARM: dts: lpc3250-phy3250: add at25 required properties
Date: Wed, 29 Oct 2025 16:28:00 -0400	[thread overview]
Message-ID: <20251029202801.3963952-4-Frank.Li@nxp.com> (raw)
In-Reply-To: <20251029202801.3963952-1-Frank.Li@nxp.com>

Add at25 required properties (size, address-width and pagesize), which
duplicate deprecated properties.

Change nodename 'at25' to 'eeprom'.

Fix below CHECK_DTB warning:
  arch/arm/boot/dts/nxp/lpc/lpc3250-phy3250.dtb: at25@0 (atmel,at25): 'pagesize' is a required property
  arch/arm/boot/dts/nxp/lpc/lpc3250-phy3250.dtb: at25@0 (atmel,at25): $nodename: 'anyOf' conditional failed, one must be fixed:

Signed-off-by: Frank Li <Frank.Li@nxp.com>
---
 arch/arm/boot/dts/nxp/lpc/lpc3250-phy3250.dts | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/arch/arm/boot/dts/nxp/lpc/lpc3250-phy3250.dts b/arch/arm/boot/dts/nxp/lpc/lpc3250-phy3250.dts
index 21a6d0bca1e8a..15463a96938cc 100644
--- a/arch/arm/boot/dts/nxp/lpc/lpc3250-phy3250.dts
+++ b/arch/arm/boot/dts/nxp/lpc/lpc3250-phy3250.dts
@@ -200,7 +200,7 @@ &ssp0 {
 	cs-gpios = <&gpio 3 5 0>;
 	status = "okay";
 
-	eeprom: at25@0 {
+	eeprom: eeprom@0 {
 		compatible = "atmel,at25";
 		reg = <0>;
 		spi-max-frequency = <5000000>;
@@ -216,6 +216,10 @@ eeprom: at25@0 {
 		at25,byte-len = <0x8000>;
 		at25,addr-mode = <2>;
 		at25,page-size = <64>;
+
+		size = <0x8000>;
+		address-width = <16>;
+		pagesize = <64>;
 	};
 };
 
-- 
2.34.1


  parent reply	other threads:[~2025-10-29 20:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-29 20:27 [PATCH 1/5] ARM: dts: lpc32xx: add bus surfix for simple-bus Frank Li
2025-10-29 20:27 ` [PATCH 2/5] ARM: dts: lpc32xx: add sspclk clock for SPI[0,1] Frank Li
2025-11-13 23:12   ` Vladimir Zapolskiy
2025-10-29 20:27 ` [PATCH 3/5] ARM: dts: lpc3250-ea3250: add key- prefix for gpio-keys Frank Li
2025-11-14  0:02   ` Vladimir Zapolskiy
2025-10-29 20:28 ` Frank Li [this message]
2025-11-13 23:47   ` [PATCH 4/5] ARM: dts: lpc3250-phy3250: add at25 required properties Vladimir Zapolskiy
2025-11-14 16:14     ` Frank Li
2025-11-14 16:32       ` Vladimir Zapolskiy
2025-10-29 20:28 ` [PATCH 5/5] ARM: dts: lpc32xx: update #address-cells of arm,pl175 to 2 Frank Li
2025-11-13 23:44   ` Vladimir Zapolskiy
2025-11-13 23:55 ` [PATCH 1/5] ARM: dts: lpc32xx: add bus surfix for simple-bus Vladimir Zapolskiy
2025-11-14 16:19   ` Frank Li
2025-11-14 16:44     ` Vladimir Zapolskiy
2025-11-14 16:56       ` Frank Li

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=20251029202801.3963952-4-Frank.Li@nxp.com \
    --to=frank.li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=imx@lists.linux.dev \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piotr.wojtaszczyk@timesys.com \
    --cc=robh@kernel.org \
    --cc=vz@mleia.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