From: tixy@linaro.org (Jon Medhurst (Tixy))
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: dts: Add idle-states for Juno
Date: Thu, 30 Apr 2015 18:36:44 +0100 [thread overview]
Message-ID: <1430415404.2868.49.camel@linaro.org> (raw)
In-Reply-To: <20150430171701.GA31834@red-moon>
On Thu, 2015-04-30 at 18:17 +0100, Lorenzo Pieralisi wrote:
> On Thu, Apr 30, 2015 at 05:40:35PM +0100, Jon Medhurst (Tixy) wrote:
> > On Thu, 2015-04-30 at 17:00 +0100, Sudeep Holla wrote:
> > >
> > > On 30/04/15 14:57, Jon Medhurst (Tixy) wrote:
> > > > From: Jon Medhurst <tixy@linaro.org>
> > > >
> > > > Signed-off-by: Jon Medhurst <tixy@linaro.org>
> > > > ---
> > > >
> > > > These have been kicking around out of tree for ages, any reason they
> > > > shouldn't be in mainline?
> > >
> > > One possible reason could be that these values are not tuned(e.g.
> > > latency values, can they be same for both clusters ?)
> >
> > I thought that both clusters being the same was questionable.
> >
> > > Though these
> > > reasons are not blocking and this patch will not cause any
> > > functionality break even if is merged as is.
> >
> > My main purpose with trying to get this merged is so that people using
> > Juno for general testing and validation will actually have cpuidle
> > running and so potentially find more bugs.
>
> I am reluctant to enable idle states in the default Juno dts, they
> will affect latencies and performance tests significantly. I should
> find a way to disable them by default and possibly have a DT property
> to enabled them explicitly, we can't merge the dts as it is we have
> to change the CPUidle code first.
Presumably the same argument goes for cpufreq? That'll upset people
doing performance benchmarks, so shouldn't be enabled by default?
Anyway, I'll just step back and let you ARM guys decide what and when
any upstream kernel support should be merged.
--
Tixy
next prev parent reply other threads:[~2015-04-30 17:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 13:57 [PATCH] arm64: dts: Add idle-states for Juno Jon Medhurst (Tixy)
2015-04-30 15:42 ` Liviu Dudau
2015-04-30 16:28 ` Jon Medhurst (Tixy)
2015-04-30 16:00 ` Sudeep Holla
2015-04-30 16:40 ` Jon Medhurst (Tixy)
2015-04-30 16:57 ` Sudeep Holla
2015-04-30 17:17 ` Lorenzo Pieralisi
2015-04-30 17:36 ` Jon Medhurst (Tixy) [this message]
2015-04-30 17:40 ` Sudeep Holla
2015-05-01 8:52 ` Jon Medhurst (Tixy)
2015-05-01 9:02 ` Catalin Marinas
2015-05-01 10:12 ` Lorenzo Pieralisi
2015-05-01 10:22 ` Liviu Dudau
2015-05-01 11:20 ` Lorenzo Pieralisi
2015-05-01 13:30 ` Catalin Marinas
2015-05-01 14:28 ` Lorenzo Pieralisi
2015-05-01 1:55 ` Leo Yan
2015-05-01 10:22 ` Jon Medhurst (Tixy)
2015-05-01 10:45 ` Lorenzo Pieralisi
2015-05-01 11:55 ` Leo Yan
2015-05-01 13:58 ` Liviu Dudau
2015-05-07 12:40 ` Lorenzo Pieralisi
2015-05-07 14:32 ` Leo Yan
2015-05-01 11:39 ` Leo Yan
2015-10-22 13:22 ` Punit Agrawal
2015-10-26 14:12 ` Jon Medhurst (Tixy)
2015-10-26 15:17 ` Lorenzo Pieralisi
2015-11-23 17:45 ` Punit Agrawal
2015-11-24 17:53 ` Lorenzo Pieralisi
2015-12-07 16:59 ` Punit Agrawal
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=1430415404.2868.49.camel@linaro.org \
--to=tixy@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).