[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210608142019.GG4200@sirena.org.uk>
Date: Tue, 8 Jun 2021 15:20:19 +0100
From: Mark Brown <broonie@...nel.org>
To: Ulf Hansson <ulf.hansson@...aro.org>
Cc: Stephan Gerhold <stephan@...hold.net>,
"Rafael J . Wysocki" <rjw@...ysocki.net>,
Viresh Kumar <viresh.kumar@...aro.org>,
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
Linux PM <linux-pm@...r.kernel.org>,
Dmitry Osipenko <digetx@...il.com>,
Jonathan Hunter <jonathanh@...dia.com>,
Thierry Reding <thierry.reding@...il.com>,
Roja Rani Yarubandi <rojay@...eaurora.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Vincent Guittot <vincent.guittot@...aro.org>,
Stephen Boyd <sboyd@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Rajendra Nayak <rnayak@...eaurora.org>
Subject: Re: [PATCH v2 4/4] PM: domains: Drop/restore performance state votes
for devices at system PM
On Tue, Jun 08, 2021 at 04:08:55PM +0200, Ulf Hansson wrote:
> Honestly, I am not sure about what the regulator-fixed-domain intends
> to model, but I assume it's something that fits well to be modelled as
> a plain regulator, to start with.
> Perhaps Mark can chime in and spread some light over this?
IIRC it's for situations where there's a device that's normally built as
a separate chip that got built into a bigger SoC and wants to rear end
something onto a power domain, I guess especially if the power domain
doesn't cover the whole of a Linux device.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists