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: <176703895443.2172504.7231951665641312391.robh@kernel.org>
Date: Mon, 29 Dec 2025 14:39:25 -0600
From: Rob Herring <robh@...nel.org>
To: Kuan-Wei Chiu <visitorckw@...il.com>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org, 
 jserv@...s.ncku.edu.tw, conor+dt@...nel.org, eleanor15x@...il.com, 
 linux-arm-kernel@...ts.infradead.org, linusw@...nel.org, krzk+dt@...nel.org, 
 arnd@...db.de, devicetree@...r.kernel.org
Subject: Re: [PATCH v2] ARM: dts: integrator: Fix DMA ranges mismatch
 warning on IM-PD1


On Thu, 25 Dec 2025 17:31:18 +0000, Kuan-Wei Chiu wrote:
> When compiling the device tree for the Integrator/AP with IM-PD1, the
> following warning is observed regarding the display controller node:
> 
> arch/arm/boot/dts/arm/integratorap-im-pd1.dts:251.3-14: Warning
> (dma_ranges_format):
> /bus@...00000/bus@...00000/display@...0000:dma-ranges: empty
> "dma-ranges" property but its #address-cells (2) differs from
> /bus@...00000/bus@...00000 (1)
> 
> The "dma-ranges" property is intended to describe DMA address
> translations for child nodes. However, the only child of the display
> controller is a "port" node, which does not perform DMA memory
> accesses.
> 
> Since the property is not required for the child node and triggers a
> warning due to default address cell mismatch, remove it.
> 
> Fixes: 7bea67a99430 ("ARM: dts: integrator: Fix DMA ranges")
> Cc: stable@...r.kernel.org
> Signed-off-by: Kuan-Wei Chiu <visitorckw@...il.com>
> ---
> Changes in v2:
> - Switch approach to remove the unused "dma-ranges" property instead of
>   adding "#address-cells" and "#size-cells".
> 
>  arch/arm/boot/dts/arm/integratorap-im-pd1.dts | 1 -
>  1 file changed, 1 deletion(-)
> 


My bot found new DTB warnings on the .dts files added or changed in this
series.

Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
are fixed by another series. Ultimately, it is up to the platform
maintainer whether these warnings are acceptable or not. No need to reply
unless the platform maintainer has comments.

If you already ran DT checks and didn't see these error(s), then
make sure dt-schema is up to date:

  pip3 install dtschema --upgrade


This patch series was applied (using b4) to base:
 Base: attempting to guess base-commit...
 Base: tags/next-20251219 (exact match)
 Base: tags/next-20251219 (use --merge-base to override)

If this is not the correct base, please add 'base-commit' tag
(or use b4 which does this automatically)

New warnings running 'make CHECK_DTBS=y for arch/arm/boot/dts/arm/' for 20251225173118.580110-1-visitorckw@...il.com:

arch/arm/boot/dts/arm/integratorap-im-pd1.dtb: display@...0000 (arm,pl110): 'port@0' does not match any of the regexes: '^pinctrl-[0-9]+$'
	from schema $id: http://devicetree.org/schemas/display/arm,pl11x.yaml






Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ