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: <CAL_JsqJmTmb3GF+CvidWhzgoDP60tb=BtggMcyEP_Ev9dNtjAQ@mail.gmail.com>
Date: Wed, 3 Sep 2025 08:40:06 -0500
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>, 
	Joel Stanley <joel@....id.au>, devicetree@...r.kernel.org, 
	linux-arm-kernel@...ts.infradead.org, linux-aspeed@...ts.ozlabs.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ARM: dts: aspeed: Drop syscon "reg-io-width" properties

On Wed, Sep 3, 2025 at 2:18 AM Andrew Jeffery
<andrew@...econstruct.com.au> wrote:
>
> On Fri, 2025-08-29 at 16:13 -0500, Rob Herring (Arm) wrote:
> > The default width is 4 bytes for "syscon" devices, so "reg-io-width" is
> > redundant and can be dropped.
>
> I had a quick look in the syscon bindings and can't see that this is
> documented? The driver implementation behaves this way though.

It's not. I suppose we could add that to syscon-common.yaml, but
that's only documentation. It has 0 effect on the schema validation. I
would guess we have hundreds of syscon's that rely on the default.

Rob

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ