lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ad644270-4236-4a71-b301-b912b0cd49f3@broadcom.com>
Date: Wed, 28 Jan 2026 13:07:31 -0800
From: Florian Fainelli <florian.fainelli@...adcom.com>
To: Lee Yongjun <jun85566@...il.com>, rjui@...adcom.com,
 sbranden@...adcom.com, robh@...nel.org, krzk+dt@...nel.org,
 conor+dt@...nel.org
Cc: bcm-kernel-feedback-list@...adcom.com,
 linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arm64: dts: broadcom: ns2-svk: fix AT25 EEPROM node and
 properties

On 1/22/26 08:18, Lee Yongjun wrote:
> The AT25 EEPROM node on the Northstar 2 SVK board used legacy vendor
> properties and a non-standard node name, which triggers dtbs_check
> warnings.
> 
> Update the node to follow the dt-schema by:
> - Renaming the node from at25@0 to eeprom@0.
> - Replacing deprecated "at25,byte-len" with "size".
> - Replacing deprecated "at25,page-size" with "pagesize".
> - Replacing deprecated "at25,addr-mode" with "address-width".
> 
> For "address-width", the legacy value <2> corresponds to the EE_ADDR2
> flag in the driver (include/linux/spi/eeprom.h), which is explicitly
> defined as 16-bit addressing. Therefore, <16> is the technically
> accurate value that preserves the existing hardware behavior while
> satisfying the at25.yaml schema requirements.
> 
> Signed-off-by: Lee Yongjun <jun85566@...il.com>

Thanks for your patch, however I have something from Rob already queued up:

https://lore.kernel.org/r/20260106-dt-dtbs-broadcom-fixes-v1-9-ba45874e4553@kernel.org

You could re-submit the portion of your patch that renames the node?
-- 
Florian

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ