linux-kernel - Re: [PATCH 1/2] devicetree: bindings: mux: reg-mux: Add support for new property 'mux-reg-masks-state'

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: <20250625184858.GA2004209-robh@kernel.org>
Date: Wed, 25 Jun 2025 13:48:58 -0500
From: Rob Herring <robh@...nel.org>
To: Chintan Vankar <c-vankar@...com>
Cc: Thorsten Blum <thorsten.blum@...ux.dev>, Andrew Davis <afd@...com>,
	Conor Dooley <conor+dt@...nel.org>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Peter Rosin <peda@...ntia.se>, linux-kernel@...r.kernel.org,
	devicetree@...r.kernel.org, s-vadapalli@...com, vigneshr@...com,
	nm@...com, danishanwar@...com
Subject: Re: [PATCH 1/2] devicetree: bindings: mux: reg-mux: Add support for
 new property 'mux-reg-masks-state'

On Thu, Jun 05, 2025 at 12:04:21PM +0530, Chintan Vankar wrote:
> The DT binding for reg-mux currenly requires specifying register offset
> and masks in the "mux-reg-masks" property, while corresponding register
> values are defined in the "idle-states" property. This approach imposes a
> constraint where "mux-reg-masks" and "idle-states" must remain
> synchroniszed, adding complexity when configuring specific registers or a
> set of registers with large memory spaces.

Sorry, but I don't follow why there's complexity. Having to support 2 
different ways to express the same thing adds complexity we have to 
maintain forever. I prefer to impose the complexity on the .dts than 
maintainers.

Rob