[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f9bac96d-3822-4942-986a-61a8cedaba84@sirena.org.uk>
Date: Mon, 12 Jun 2023 19:13:02 +0100
From: Mark Brown <broonie@...nel.org>
To: Chen-Yu Tsai <wenst@...omium.org>
Cc: AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>,
Matthias Brugger <matthias.bgg@...il.com>,
Gene Chen <gene_chen@...htek.com>,
Johnson Wang <johnson.wang@...iatek.com>,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4/9] regulator: mt6358: Drop *_SSHUB regulators
On Mon, Jun 12, 2023 at 12:45:21PM +0800, Chen-Yu Tsai wrote:
> list the *_SSHUB versions. So if SCP DVFS is used, the regulator driver
> has no idea what's going on, and can't interfere either, which I think is
> actually a good thing. Only one side should have complete control of one
> output.
Very much so - there's a SCMI regulator interface for communicating with
SCPs where that's required (eg, for things like SD cards).
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists