[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yl7Nb0mNjt7kV3uV@sirena.org.uk>
Date: Tue, 19 Apr 2022 15:55:43 +0100
From: Mark Brown <broonie@...nel.org>
To: Stephen Boyd <swboyd@...omium.org>
Cc: Bjorn Andersson <bjorn.andersson@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Satya Priya <quic_c_skakit@...cinc.com>,
Lee Jones <lee.jones@...aro.org>,
Liam Girdwood <lgirdwood@...il.com>,
linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, quic_collinsd@...cinc.com,
quic_subbaram@...cinc.com, quic_jprakash@...cinc.com
Subject: Re: [PATCH V10 7/9] regulator: Add a regulator driver for the PM8008
PMIC
On Thu, Apr 14, 2022 at 05:25:49PM -0700, Stephen Boyd wrote:
> Quoting Satya Priya (2022-04-14 05:30:16)
> > +static struct platform_driver pm8008_regulator_driver = {
> > + .driver = {
> > + .name = "qcom-pm8008-regulator",
> I'd prefer to use an of_device_id table here. That would let us populate
> a "qcom,pm8008-regulators" node that had the ldo nodes as children and
> avoid mfd cells.
That's encoding the current Linux way of splitting up drivers into the
DT rather than describing the hardware.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists