[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201215115602.GA4738@sirena.org.uk>
Date: Tue, 15 Dec 2020 11:56:02 +0000
From: Mark Brown <broonie@...nel.org>
To: Hsin-hsiung Wang <hsin-hsiung.wang@...iatek.com>
Cc: Lee Jones <lee.jones@...aro.org>, Rob Herring <robh+dt@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
Liam Girdwood <lgirdwood@...il.com>,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org,
srv_heupstream@...iatek.com, Wen Su <wen.su@...iatek.com>
Subject: Re: [PATCH v3 5/8] regulator: mt6359: Add support for MT6359
regulator
On Tue, Dec 15, 2020 at 05:23:08PM +0800, Hsin-hsiung Wang wrote:
> On Tue, 2020-11-24 at 17:07 +0000, Mark Brown wrote:
> > This looks like it could just be regmap_get_voltage_sel_regmap()?
> > Otherwise the driver looks good.
> Thanks for the review.
> MT6359 regulator has sel_reg and status_reg, so we use
> mt6359_get_linear_voltage_sel for status_reg instead of
> regmap_get_voltage_sel_regmap() which uses sel_reg.
Is the selector register not readable? In general the rule is that the
get should be reporting what was configured, the actual status should be
reported separately if it can be read separately. We don't currently
have a mechanism for doing that with voltage but one could be added.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists