linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Andrew Jeffery <andrew@codeconstruct.com.au>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Linus Walleij <linusw@kernel.org>, Joel Stanley <joel@jms.id.au>,
	linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	openbmc@lists.ozlabs.org, linux-gpio@vger.kernel.org,
	linux-mmc@vger.kernel.org, linux-crypto@vger.kernel.org,
	linux-iio@vger.kernel.org
Subject: Re: [PATCH RFC 00/16] Eliminate warnings for AST2500 and AST2600 EVB devicetrees
Date: Fri, 12 Dec 2025 09:06:31 -0600	[thread overview]
Message-ID: <20251212150631.GA3997751-robh@kernel.org> (raw)
In-Reply-To: <20251211-dev-dt-warnings-all-v1-0-21b18b9ada77@codeconstruct.com.au>

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

  parent reply	other threads:[~2025-12-12 15:06 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-11  8:45 [PATCH RFC 00/16] Eliminate warnings for AST2500 and AST2600 EVB devicetrees Andrew Jeffery
2025-12-11  8:45 ` [PATCH RFC 01/16] dt-bindings: hwmon: Convert aspeed,ast2400-pwm-tacho to DT schema Andrew Jeffery
2025-12-11 20:27   ` Guenter Roeck
2025-12-12  5:53     ` Andrew Jeffery
2025-12-11  8:45 ` [PATCH RFC 02/16] pinctrl: aspeed: g5: Constrain LPC binding revision workaround to AST2500 Andrew Jeffery
2025-12-11  8:45 ` [PATCH RFC 03/16] pinctrl: aspeed: g5: Allow use of LPC node instead of LPC host controller Andrew Jeffery
2025-12-11  8:45 ` [PATCH RFC 04/16] ARM: dts: aspeed: g5: Use LPC phandle for pinctrl aspeed,external-nodes Andrew Jeffery
2025-12-11  8:45 ` [PATCH RFC 05/16] ARM: dts: aspeed: Remove unspecified LPC host controller node Andrew Jeffery
2025-12-11  8:45 ` [PATCH RFC 06/16] dt-bindings: mmc: Switch ref to sdhci-common.yaml Andrew Jeffery
2025-12-11 11:31   ` Ulf Hansson
2025-12-11 15:57   ` Rob Herring (Arm)
2025-12-11 17:03     ` Rob Herring
2025-12-11  8:45 ` [PATCH RFC 07/16] ARM: dts: aspeed: Remove sdhci-drive-type property from AST2600 EVB Andrew Jeffery
2025-12-11 11:31   ` Ulf Hansson
2025-12-11  8:45 ` [PATCH RFC 08/16] ARM: dts: aspeed: Use specified wp-inverted property for " Andrew Jeffery
2025-12-11 11:31   ` Ulf Hansson
2025-12-11  8:45 ` [PATCH RFC 09/16] dt-bindings: bus: aspeed: Require syscon for AST2600 AHB controller Andrew Jeffery
2025-12-11 19:56   ` Rob Herring (Arm)
2025-12-11  8:45 ` [PATCH RFC 10/16] dt-bindings: crypto: Document aspeed,ahbc property for Aspeed ACRY Andrew Jeffery
2025-12-11 19:57   ` Rob Herring (Arm)
2025-12-11  8:45 ` [PATCH RFC 11/16] ARM: dts: aspeed: Drop syscon compatible from EDAC in g6 dtsi Andrew Jeffery
2025-12-11  8:45 ` [PATCH RFC 12/16] ARM: dts: aspeed: g6: Drop unspecified aspeed,ast2600-udma node Andrew Jeffery
2025-12-11  8:45 ` [PATCH RFC 13/16] ARM: dts: aspeed: ast2600-evb: Tidy up A0 work-around for UART5 Andrew Jeffery
2025-12-11  8:45 ` [PATCH RFC 14/16] dt-bindings: iio: adc: Allow interrupts property for AST2600 Andrew Jeffery
2025-12-11 19:57   ` Rob Herring (Arm)
2025-12-13 17:02     ` Jonathan Cameron
2025-12-11  8:45 ` [PATCH RFC 15/16] ARM: dts: aspeed: g6: Drop clocks property from arm,armv7-timer Andrew Jeffery
2025-12-11  8:45 ` [PATCH RFC 16/16] dt-bindings: mfd: Document smp-memram node for AST2600 SCU Andrew Jeffery
2025-12-11 15:57   ` Rob Herring (Arm)
2025-12-12  5:57     ` Andrew Jeffery
2025-12-11 14:07 ` [PATCH RFC 00/16] Eliminate warnings for AST2500 and AST2600 EVB devicetrees Rob Herring
2025-12-12 15:06 ` Rob Herring [this message]
2025-12-12 23:05   ` Andrew Jeffery

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=20251212150631.GA3997751-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=andrew@codeconstruct.com.au \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=joel@jms.id.au \
    --cc=krzk+dt@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).