mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Neil Armstrong <neil.armstrong@linaro.org>
To: linux-kernel-dev@aliel.fr, Kevin Hilman <khilman@baylibre.com>,
	Jerome Brunet <jbrunet@baylibre.com>,
	Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-amlogic@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] arm64: dts: amlogic: Fix dtc warnings with W=1
Date: Mon, 16 Nov 2026 10:55:35 +0100	[thread overview]
Message-ID: <19786c13-d3fd-4258-a1d5-2a28a1dccc31@linaro.org> (raw)
In-Reply-To: <20261115-fix-amlogic-dt-warnings-v1-0-94cbd67a32ea@aliel.fr>

On 11/15/26 23:29, Ronald Claveau via B4 Relay wrote:
> Building the Amlogic device trees with W=1 CHECK_DTBS=y currently
> produces several dtc warnings, all related to the same pattern:
> 
>    Warning (unit_address_vs_reg): /soc/bus@.../pinctrl@XXXX: node has a
>    unit name, but no reg or ranges property
>    Warning (simple_bus_reg): /soc/bus@.../pinctrl@XXXX: missing or
>    empty reg/ranges property
> 
> The pinctrl nodes use an empty "ranges;" while having a unit address.
> 
> With this series applied, the Amlogic DTBs build without any warning
> with:
> 
>    make ARCH=arm64 W=1 CHECK_DTBS=y amlogic/
> 
> Boot tested on Khadas VIM1 (GXL) and Khadas VIM4 (T7)
> 
> Signed-off-by: Ronald Claveau <linux-kernel-dev@aliel.fr>
> ---
> Ronald Claveau (7):
>        arm64: dts: amlogic: t7: Add ranges to periphs pinctrl node
>        arm64: dts: amlogic: a1: Add ranges to periphs pinctrl node
>        arm64: dts: amlogic: axg: Add ranges to periphs pinctrl node
>        arm64: dts: amlogic: g12: Add ranges to periphs pinctrl node
>        arm64: dts: amlogic: gxbb: Add ranges to periphs pinctrl node
>        arm64: dts: amlogic: gxl: Add ranges to periphs pinctrl node
>        arm64: dts: amlogic: s4: Add ranges to periphs pinctrl node
> 
>   arch/arm64/boot/dts/amlogic/amlogic-t7.dtsi       | 2 +-
>   arch/arm64/boot/dts/amlogic/meson-a1.dtsi         | 2 +-
>   arch/arm64/boot/dts/amlogic/meson-axg.dtsi        | 5 +++--
>   arch/arm64/boot/dts/amlogic/meson-g12-common.dtsi | 6 ++----
>   arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi       | 5 +++--
>   arch/arm64/boot/dts/amlogic/meson-gxl.dtsi        | 5 +++--
>   arch/arm64/boot/dts/amlogic/meson-s4.dtsi         | 2 +-
>   7 files changed, 14 insertions(+), 13 deletions(-)
> ---
> base-commit: 6d582d78fad9d828e575ca0cdcff8ea47a77220b
> change-id: 20261115-fix-amlogic-dt-warnings-7cba2a4eb9d4
> 
> Best regards,
> --
> Ronald Claveau <linux-kernel-dev@aliel.fr>

Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>

Thanks,
Neil

      parent reply	other threads:[~2026-11-16  9:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-15 22:29 Ronald Claveau via B4 Relay
2026-11-15 22:29 ` [PATCH 1/7] arm64: dts: amlogic: t7: Add ranges to periphs pinctrl node Ronald Claveau via B4 Relay
2026-11-15 22:29 ` [PATCH 2/7] arm64: dts: amlogic: a1: " Ronald Claveau via B4 Relay
2026-11-15 22:29 ` [PATCH 3/7] arm64: dts: amlogic: axg: " Ronald Claveau via B4 Relay
2026-11-15 22:29 ` [PATCH 4/7] arm64: dts: amlogic: g12: " Ronald Claveau via B4 Relay
2026-11-15 22:29 ` [PATCH 5/7] arm64: dts: amlogic: gxbb: " Ronald Claveau via B4 Relay
2026-11-15 22:29 ` [PATCH 6/7] arm64: dts: amlogic: gxl: " Ronald Claveau via B4 Relay
2026-11-15 22:29 ` [PATCH 7/7] arm64: dts: amlogic: s4: " Ronald Claveau via B4 Relay
2026-11-16  9:55 ` Neil Armstrong [this message]

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=19786c13-d3fd-4258-a1d5-2a28a1dccc31@linaro.org \
    --to=neil.armstrong@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jbrunet@baylibre.com \
    --cc=khilman@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel-dev@aliel.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=robh@kernel.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

all inboxes | Powered by JetHome®