All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Clément Péron" <peron.clem@gmail.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Mark Brown <broonie@kernel.org>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
	Stephen Boyd <sboyd@kernel.org>,
	"open list:ALLWINNER CPUFREQ DRIVER" <linux-pm@vger.kernel.org>,
	Steven Price <steven.price@arm.com>
Subject: Re: Question about OPP regulator for Panfrost Devfreq
Date: Wed, 13 May 2020 13:36:54 +0200	[thread overview]
Message-ID: <CAJiuCcdh5101FNMA+LKsvVV++M-iUyWSgqDr5FVQdXcpt6WqyA@mail.gmail.com> (raw)
In-Reply-To: <20200513110350.uojo5jaufx7rj5v6@vireshk-i7>

Hi Viresh,

On Wed, 13 May 2020 at 13:03, Viresh Kumar <viresh.kumar@linaro.org> wrote:
>
> On 13-05-20, 12:00, Mark Brown wrote:
> > The OPP code can and should be calling regulator_enable().  If the OPP
> > code needs some particular voltage configuration it can and should be
> > calling regulator_set_voltage() to tell the core what it needs.  What
> > I'm saying is that if when the OPP code enables the regulator it needs
> > a particular voltage configuration it should tell the core about that
> > prior to enabling.
>
> I see. Thanks for that.
>
> Clement: I will prepare a patch for you to test then.

Thanks for taking care of that, I'm sure it will works fine for me,
but maybe it should be double tested by Marek Szyprowski on the exynos
bus.

Thanks
Clement

>
> --
> viresh

      reply	other threads:[~2020-05-13 11:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-09 19:56 Question about OPP regulator for Panfrost Devfreq Clément Péron
2020-05-11  5:25 ` Viresh Kumar
2020-05-12 20:51   ` Clément Péron
2020-05-13  5:46     ` Viresh Kumar
2020-05-13  8:18       ` Clément Péron
2020-05-13  9:19         ` Viresh Kumar
2020-05-13 10:18           ` Mark Brown
2020-05-13 10:40             ` Viresh Kumar
2020-05-13 11:00               ` Mark Brown
2020-05-13 11:03                 ` Viresh Kumar
2020-05-13 11:36                   ` Clément Péron [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJiuCcdh5101FNMA+LKsvVV++M-iUyWSgqDr5FVQdXcpt6WqyA@mail.gmail.com \
    --to=peron.clem@gmail.com \
    --cc=broonie@kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=nm@ti.com \
    --cc=sboyd@kernel.org \
    --cc=steven.price@arm.com \
    --cc=viresh.kumar@linaro.org \
    --cc=vireshk@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.