[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251212150631.GA3997751-robh@kernel.org>
Date: Fri, 12 Dec 2025 09:06:31 -0600
From: Rob Herring <robh@...nel.org>
To: Andrew Jeffery <andrew@...econstruct.com.au>
Cc: Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Linus Walleij <linusw@...nel.org>, Joel Stanley <joel@....id.au>,
linux-hwmon@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-aspeed@...ts.ozlabs.org,
linux-kernel@...r.kernel.org, openbmc@...ts.ozlabs.org,
linux-gpio@...r.kernel.org, linux-mmc@...r.kernel.org,
linux-crypto@...r.kernel.org, linux-iio@...r.kernel.org
Subject: Re: [PATCH RFC 00/16] Eliminate warnings for AST2500 and AST2600 EVB
devicetrees
On Thu, Dec 11, 2025 at 05:45:42PM +0900, Andrew Jeffery wrote:
> Hi all,
>
> This series removes the remaining warnings produced by `make
> CHECK_DTBS=y ...` for the AST2500 and AST2600 EVBs and their related
> DTSIs. The tidy-up has the usual benefit of making it clear to
> contributors that any warnings are likely their own to fix before their
> patches will be considered for merging.
>
> I've framed it as an RFC with all patches contained in the one series
> so the goal is clear, we can see what's needed to reach it, and we can
> decide whether and how it should be split or merged going forward.
>
> As it stands there's little in the way of code change, except to
> pinctrl (though also not much there). As such I've included the
> binding maintainers and subsystem lists as recipients but not yet Cc'ed
> subsystem maintainers directly because there are quite a few and I hope
> to avoid mostly uninteresting patches being a source of irritation.
>
> The patches fall into several groups:
>
> Patch 1:
> Rob's conversion of the PWM/tach binding to DT schema with fixes
> applied for the license and typos identified by Krzysztof.
>
> Patches 2-5:
> Fixes for the warnings related to the LPC and pinctrl nodes, touching
> relevant drivers and the devicetrees.
>
> I expect that if this approach is acceptable that we'll need to split
> application of the patches across successive release cycles, with the
> driver changes going in first.
>
> Patches 6-8:
> Fix MMC/SDHCI warnings, touching the relevant binding and devicetrees
>
> Patches 9-10:
> Clarify the relationships between the ACRY and AHB controller
>
> Patches 11-16:
> The remaining pieces that eliminate the warnings
Don't you see warnings for at25:
89 (atmel,at25): 'size' is a required property
89 (atmel,at25): 'pagesize' is a required property
89 (atmel,at25): 'address-width' is a required property
These are due to using the deprecated (since 2012) at25,byte-len,
at25,addr-mode, and at25,page-size properties. I think it has been long
enough you can just replace them with the new ones.
Rob
Powered by blists - more mailing lists