Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1288464

Re: [PATCH] cpufreq: tegra: add regulator dependency for T124

From Mark Brown <broonie@kernel.org>
Newsgroups linux.kernel
Subject Re: [PATCH] cpufreq: tegra: add regulator dependency for T124
Date 2015-12-10 12:40 +0100
Message-ID <qE7JM-5B8-19@gated-at.bofh.it> (permalink)
References (1 earlier) <qDLJh-8df-33@gated-at.bofh.it> <qDOe5-1dO-11@gated-at.bofh.it> <qDQSC-2X5-13@gated-at.bofh.it> <qDTnr-4C7-9@gated-at.bofh.it> <qE6kG-4M5-27@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

On Thu, Dec 10, 2015 at 10:07:54AM +0000, Jon Hunter wrote:
> On 09/12/15 20:10, Mark Brown wrote:
> > On Wed, Dec 09, 2015 at 05:33:33PM +0000, Jon Hunter wrote:

> >> Yes, setting the frequency and voltage as defined by a given operating
> >> mode would make sense. However, I am not sure we have those defined in
> >> the kernel for this PLL and would have to be added.

> > I think given how you're describing the hardware that this will be
> > required in order to provide something robust (and also to get the best
> > power savings from the hardware).

> Yes I agree it would be more robust. However, if you care about power
> savings then you should be using the DFLL/cpufreq anyway.

Without knowing anything about the hardware this is all a bit confusing
I'm afraid.  What is "DFLL/cpufreq" as opposed to "the PLL"?

> From testing the t124 jetson and nyan-big, both of these boards have a
> different configuration for the PLL at boot time, so although we could
> pick a safe operating point for all t124 boards, I was thinking of just
> restoring their initial configuration.

This seems more complex, and also makes the idea of relying on the
initial configuration seem slightly concerning - other software seems to
be already changing the configuration before we get to the kernel so if
we don't fully understand the configuration we're doing we seem likely
to find some configuration where we miss things.

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH] cpufreq: tegra: add regulator dependency for T124 Arnd Bergmann <arnd@arndb.de> - 2015-12-08 23:00 +0100
  Re: [PATCH] cpufreq: tegra: add regulator dependency for T124 Viresh Kumar <viresh.kumar@linaro.org> - 2015-12-09 03:20 +0100
  Re: [PATCH] cpufreq: tegra: add regulator dependency for T124 Jon Hunter <jonathanh@nvidia.com> - 2015-12-09 13:10 +0100
    Re: [PATCH] cpufreq: tegra: add regulator dependency for T124 Mark Brown <broonie@kernel.org> - 2015-12-09 15:50 +0100
      Re: [PATCH] cpufreq: tegra: add regulator dependency for T124 Jon Hunter <jonathanh@nvidia.com> - 2015-12-09 18:40 +0100
        Re: [PATCH] cpufreq: tegra: add regulator dependency for T124 Mark Brown <broonie@kernel.org> - 2015-12-09 21:20 +0100
          Re: [PATCH] cpufreq: tegra: add regulator dependency for T124 Jon Hunter <jonathanh@nvidia.com> - 2015-12-10 11:10 +0100
            Re: [PATCH] cpufreq: tegra: add regulator dependency for T124 Mark Brown <broonie@kernel.org> - 2015-12-10 12:40 +0100
              Re: [PATCH] cpufreq: tegra: add regulator dependency for T124 Jon Hunter <jonathanh@nvidia.com> - 2015-12-10 13:20 +0100

csiph-web