From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Nick Piggin <npiggin@suse.de>,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-pm@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/3] cpufreq: pmac64: speed up frequency switch
Date: Fri, 16 Aug 2013 08:14:32 +1000 [thread overview]
Message-ID: <1376604872.4255.115.camel@pasglop> (raw)
In-Reply-To: <20130815201000.GB3067@blackmetal.musicnaut.iki.fi>
On Thu, 2013-08-15 at 23:10 +0300, Aaro Koskinen wrote:
> I guess we should keep the current 12us latency in g5_neo2_cpufreq_init()
> (although I doubt it's correct...), and only add the new 10ms latency
> value to g5_pm72_cpufreq_init() - that way we can enable the older systems
> to use ondemand (despite long latencies), while not risking regressing
> any of the current functionality.
>
> I'll resend the series with the changes.
Well, mine is a 11,2, it's not a neo2.
I suppose we could try to measure the latency :-)
Cheers,
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Nick Piggin <npiggin@suse.de>,
linux-pm@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: Re: [PATCH 1/3] cpufreq: pmac64: speed up frequency switch
Date: Fri, 16 Aug 2013 08:14:32 +1000 [thread overview]
Message-ID: <1376604872.4255.115.camel@pasglop> (raw)
In-Reply-To: <20130815201000.GB3067@blackmetal.musicnaut.iki.fi>
On Thu, 2013-08-15 at 23:10 +0300, Aaro Koskinen wrote:
> I guess we should keep the current 12us latency in g5_neo2_cpufreq_init()
> (although I doubt it's correct...), and only add the new 10ms latency
> value to g5_pm72_cpufreq_init() - that way we can enable the older systems
> to use ondemand (despite long latencies), while not risking regressing
> any of the current functionality.
>
> I'll resend the series with the changes.
Well, mine is a 11,2, it's not a neo2.
I suppose we could try to measure the latency :-)
Cheers,
Ben.
next prev parent reply other threads:[~2013-08-15 22:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 20:24 [PATCH 1/3] cpufreq: pmac64: speed up frequency switch Aaro Koskinen
2013-07-23 20:24 ` [PATCH 2/3] cpufreq: pmac64: re-estimate G5 cpufreq transition latency Aaro Koskinen
2013-07-24 5:34 ` Viresh Kumar
2013-07-24 5:34 ` Viresh Kumar
2013-07-24 10:18 ` Aaro Koskinen
2013-07-24 10:18 ` Aaro Koskinen
2013-07-24 10:45 ` Viresh Kumar
2013-07-24 10:45 ` Viresh Kumar
2013-07-23 20:24 ` [PATCH 3/3] cpufreq: pmac64: enable cpufreq on iMac G5 (iSight) model Aaro Koskinen
2013-07-24 5:34 ` Viresh Kumar
2013-07-24 5:34 ` Viresh Kumar
2013-07-23 21:20 ` [PATCH 1/3] cpufreq: pmac64: speed up frequency switch Rafael J. Wysocki
2013-07-23 21:20 ` Rafael J. Wysocki
2013-07-23 21:14 ` Benjamin Herrenschmidt
2013-07-23 21:14 ` Benjamin Herrenschmidt
2013-08-12 1:07 ` Benjamin Herrenschmidt
2013-08-12 1:07 ` Benjamin Herrenschmidt
2013-08-15 20:10 ` Aaro Koskinen
2013-08-15 20:10 ` Aaro Koskinen
2013-08-15 22:14 ` Benjamin Herrenschmidt [this message]
2013-08-15 22:14 ` Benjamin Herrenschmidt
2013-07-24 5:32 ` Viresh Kumar
2013-07-24 5:32 ` Viresh Kumar
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=1376604872.4255.115.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=aaro.koskinen@iki.fi \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@suse.de \
--cc=rjw@sisk.pl \
--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 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.