[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <008ee9d6-6259-43df-9af3-2dc9877cfe94@sirena.org.uk>
Date: Fri, 5 Jan 2024 15:18:44 +0000
From: Mark Brown <broonie@...nel.org>
To: Karel Balej <karelb@...li.ms.mff.cuni.cz>
Cc: Karel Balej <balejk@...fyz.cz>, Lee Jones <lee@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org,
Duje Mihanović <duje.mihanovic@...le.hr>,
~postmarketos/upstreaming@...ts.sr.ht, phone-devel@...r.kernel.org
Subject: Re: [RFC PATCH 4/5] regulator: add 88pm88x regulators driver
On Thu, Dec 28, 2023 at 10:39:13AM +0100, Karel Balej wrote:
> @@ -68,6 +68,21 @@ static struct mfd_cell pm886_devs[] = {
> .num_resources = ARRAY_SIZE(pm88x_onkey_resources),
> .resources = pm88x_onkey_resources,
> },
> + {
> + .name = "88pm88x-regulator",
> + .id = PM88X_REGULATOR_ID_LDO2,
> + .of_compatible = "marvell,88pm88x-regulator",
> + },
Why are we adding an of_compatible here? It's redundant, the MFD split
is a feature of Linux internals not of the hardware, and the existing
88pm8xx MFD doesn't use them.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists