linux-hardening - Re: [PATCH v2 3/3] ARM: dts: aspeed: System1: IBM system1 BMC board

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <b09d6e54-66e9-482f-8f45-38381fa6b62e@sirena.org.uk>
Date: Mon, 8 Jan 2024 21:34:47 +0000
From: Mark Brown <broonie@...nel.org>
To: Ninad Palsule <ninad@...ux.ibm.com>
Cc: robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org,
	conor+dt@...nel.org, joel@....id.au, andrew@...econstruct.com.au,
	peterhuewe@....de, jarkko@...nel.org, jgg@...pe.ca,
	keescook@...omium.org, tony.luck@...el.com, gpiccoli@...lia.com,
	johannes.holland@...ineon.com, linux@...ck-us.net,
	andre.werner@...tec-electronic.com,
	Andrew Geissler <geissonator@...oo.com>,
	patrick.rudolph@...ements.com, vincent@...emblay.dev,
	peteryin.openbmc@...il.com, lakshmiy@...ibm.com,
	bhelgaas@...gle.com, naresh.solanki@...ements.com,
	alexander.stein@...tq-group.com, festevam@...x.de,
	devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	linux-aspeed@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
	linux-integrity@...r.kernel.org, linux-hardening@...r.kernel.org,
	geert+renesas@...der.be, luca.ceresoli@...tlin.com
Subject: Re: [PATCH v2 3/3] ARM: dts: aspeed: System1: IBM system1 BMC board

On Mon, Jan 08, 2024 at 02:41:14PM -0600, Ninad Palsule wrote:

> +	regulator@60 {
> +		compatible = "maxim,max8952";
> +		reg = <0x60>;
> +
> +		max8952,default-mode = <0>;
> +		max8952,dvs-mode-microvolt = <1250000>, <1200000>,
> +						<1050000>, <950000>;
> +		max8952,sync-freq = <0>;
> +		max8952,ramp-speed = <0>;
> +
> +		regulator-name = "VR_1.0V";
> +		regulator-min-microvolt = <770000>;
> +		regulator-max-microvolt = <1400000>;

A regulator labelled VR_1.0V can vary between 0.77V and 1.4V and has
exactly the same configuration as another regulator labelled VR_1.2V?
That seems...  odd?

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)