From: Tony Lindgren <tony@atomide.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-omap@vger.kernel.org,
"Benoît Cousson" <bcousson@baylibre.com>,
devicetree@vger.kernel.org,
"Carl Philipp Klemm" <philipp@uvos.xyz>,
"Merlijn Wajer" <merlijn@wizzup.org>,
"Sebastian Reichel" <sre@kernel.org>,
"Daniel Lezcano" <daniel.lezcano@linaro.org>,
"Eduardo Valentin" <edubezval@gmail.com>,
"Peter Ujfalusi" <peter.ujfalusi@gmail.com>
Subject: Re: [PATCH 3/3] ARM: dts: motorola-mapphone: Add 1.2GHz OPP
Date: Fri, 1 Jan 2021 08:06:32 +0200 [thread overview]
Message-ID: <20210101060632.GI26857@atomide.com> (raw)
In-Reply-To: <20201231094315.GB22962@amd>
* Pavel Machek <pavel@ucw.cz> [201231 09:43]:
> I'm pretty sure it is GHz, not GiHz.
Oops right, will fix.
> > + operating-points = <
> > + /* kHz uV */
> > + 300000 1025000
> > + 600000 1200000
> > + 800000 1313000
> > + 1008000 1375000
> > + 1200000 1375000
> > + >;
>
> Is it intended to be 1.008GHz, or is it a typo?
The "1008000 1375000" is already there for 4430 in general, we now
add also add "1200000 1375000" but only for moto devices that have
it tested. The voltage used is the same in both cases.
The rates come from what's available from dpll_mpu_ck without
reprogramming the dpll.
Regards,
Tony
prev parent reply other threads:[~2021-01-01 6:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 8:42 [PATCH 1/3] ARM: dts: Configure missing thermal interrupt for 4430 Tony Lindgren
2020-12-30 8:42 ` [PATCH 2/3] ARM: dts: motorola-mapphone: Configure lower temperature passive cooling Tony Lindgren
2020-12-31 14:33 ` Pavel Machek
2020-12-31 18:53 ` Pavel Machek
2020-12-30 8:42 ` [PATCH 3/3] ARM: dts: motorola-mapphone: Add 1.2GHz OPP Tony Lindgren
2020-12-31 9:43 ` Pavel Machek
2021-01-01 6:06 ` Tony Lindgren [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=20210101060632.GI26857@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=pavel@ucw.cz \
--cc=peter.ujfalusi@gmail.com \
--cc=philipp@uvos.xyz \
--cc=sre@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).