From: Tero Kristo <t-kristo@ti.com>
To: Tony Lindgren <tony@atomide.com>, Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Dave Gerlach <d-gerlach@ti.com>, Nishanth Menon <nm@ti.com>,
linux-pm@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: Cpufreq regression in next-20161207
Date: Thu, 8 Dec 2016 10:54:06 +0200 [thread overview]
Message-ID: <bba6373e-3f2e-cbfa-1928-e205b2dc5ff3@ti.com> (raw)
In-Reply-To: <20161208060447.GE4264@atomide.com>
On 08/12/16 08:04, Tony Lindgren wrote:
> * Viresh Kumar <viresh.kumar@linaro.org> [161207 21:58]:
>> On 07-12-16, 21:52, Tony Lindgren wrote:
>>> Hmm good question. Maybe we don't have the regulators configured for
>>> pandaboard?
>>
>> Hmm, and who would be the right person to confirm that? And its not only about
>> pandaboard but the whole OMAP4 family (which is using cpufreq-dt driver).
>
> Nishanth and Dave in Cc should be able to confirm. Most likely it's some
> missing .config option for the regulators in multi_v7_defconfig compared
> to omap2plus_defconfig though.
>
> Regards,
>
> Tony
Pandaboard has a weird configuration, where MPU VDD is controlled by a
separate component; TPS62361, but rest of the voltages are provided by
TWL6030. The support for this was attempted to be upstreamed along with
the required changes for the VC/VP framework under mach-omap2, but this
was never accepted.
I'm not sure but I recall it wasn't possible to control the MPU voltage
via the default I2C interface, instead you had to use the VC/VP path,
which isn't fully implemented for OMAP4. As a consequence, none of the
OMAP4 boards have a properly functioning MPU voltage supply control in
place and you will rely on u-boot provided voltages.
-Tero
prev parent reply other threads:[~2016-12-08 8:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 4:56 Cpufreq regression in next-20161207 Tony Lindgren
2016-12-08 5:07 ` Viresh Kumar
2016-12-08 5:52 ` Tony Lindgren
2016-12-08 5:57 ` Viresh Kumar
2016-12-08 6:04 ` Tony Lindgren
2016-12-08 8:54 ` Tero Kristo [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=bba6373e-3f2e-cbfa-1928-e205b2dc5ff3@ti.com \
--to=t-kristo@ti.com \
--cc=d-gerlach@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rafael.j.wysocki@intel.com \
--cc=sboyd@codeaurora.org \
--cc=tony@atomide.com \
--cc=viresh.kumar@linaro.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