linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tixy@linaro.org (Jon Medhurst (Tixy))
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: dts: Add idle-states for Juno
Date: Mon, 26 Oct 2015 14:12:31 +0000	[thread overview]
Message-ID: <1445868751.2807.21.camel@linaro.org> (raw)
In-Reply-To: <9hheggnca1y.fsf@e105922-lin.cambridge.arm.com>

On Thu, 2015-10-22 at 14:22 +0100, Punit Agrawal wrote:
> "Jon Medhurst (Tixy)" <tixy@linaro.org> writes:
> 
> > From: Jon Medhurst <tixy@linaro.org>
> >
> > Signed-off-by: Jon Medhurst <tixy@linaro.org>
> 
> Apologies for resurrecting an old thread.
> 
> Following the discussion on this thread, even though certain concerns
> were raised, there wasn't any objection to $SUBJECT being merged.
> 
> I don't see this patch in any tree; perhaps it's slipped through the
> cracks.

It did slip through the cracks. Lorenzo's last comment was "I am fine
with enabling the idle states, I need to review and test the idle states
DT data in the patch first though." and I didn't chase things up.

The patch will need refreshing to add idle for Juno r1. Which will then
probably resurrect the discussion about where the numbers come from for
residency times, and are the same ones for r0 valid on r1 (and r2?).

In an effort to forestall that I would say: does anyone actually care if
the values are optimal? Juno is a reference platform and powered off
mains, so tuning for the optimum power consumption is pretty pointless.
But because it _is_ used as a reference by people it should at least
have these features enabled, to serve as an example, and for test
coverage.

(And we can all pretend to ignore the elephant in the room
http://lwn.net/Articles/659347/)

-- 
Tixy

  reply	other threads:[~2015-10-26 14:12 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)
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) [this message]
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=1445868751.2807.21.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).