From: Michael Ellerman <mpe@ellerman.id.au>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Preeti U Murthy <preeti@linux.vnet.ibm.com>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"benh@kernel.crashing.org" <benh@kernel.crashing.org>,
"shreyas@linux.vnet.ibm.com" <shreyas@linux.vnet.ibm.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH] cpuidle/powernv: Populate cpuidle state details by querying the device-tree
Date: Mon, 27 Oct 2014 14:34:30 +1100 [thread overview]
Message-ID: <1414380870.24967.0.camel@concordia> (raw)
In-Reply-To: <20141024143030.GA25966@red-moon>
On Fri, 2014-10-24 at 15:30 +0100, Lorenzo Pieralisi wrote:
> On Tue, Oct 14, 2014 at 08:53:00AM +0100, Preeti U Murthy wrote:
> > We hard code the metrics relevant for cpuidle states in the kernel today.
> > Instead pick them up from the device tree so that they remain relevant
> > and updated for the system that the kernel is running on.
>
> Device tree properties should be documented, and these bindings are
> getting very similar to the ones I have just completed for ARM,
> I wonder whether we should take the generic bits out of ARM bindings (ie
> exit_latency) and make those available to other architectures.
The firmware that emits those properties is already in the field, so it would
have been nice to use a generic binding but it's too late now.
cheers
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <mpe@ellerman.id.au>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"shreyas@linux.vnet.ibm.com" <shreyas@linux.vnet.ibm.com>,
Preeti U Murthy <preeti@linux.vnet.ibm.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] cpuidle/powernv: Populate cpuidle state details by querying the device-tree
Date: Mon, 27 Oct 2014 14:34:30 +1100 [thread overview]
Message-ID: <1414380870.24967.0.camel@concordia> (raw)
In-Reply-To: <20141024143030.GA25966@red-moon>
On Fri, 2014-10-24 at 15:30 +0100, Lorenzo Pieralisi wrote:
> On Tue, Oct 14, 2014 at 08:53:00AM +0100, Preeti U Murthy wrote:
> > We hard code the metrics relevant for cpuidle states in the kernel today.
> > Instead pick them up from the device tree so that they remain relevant
> > and updated for the system that the kernel is running on.
>
> Device tree properties should be documented, and these bindings are
> getting very similar to the ones I have just completed for ARM,
> I wonder whether we should take the generic bits out of ARM bindings (ie
> exit_latency) and make those available to other architectures.
The firmware that emits those properties is already in the field, so it would
have been nice to use a generic binding but it's too late now.
cheers
next prev parent reply other threads:[~2014-10-27 3:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 7:53 [PATCH] cpuidle/powernv: Populate cpuidle state details by querying the device-tree Preeti U Murthy
2014-10-21 13:33 ` Rafael J. Wysocki
2014-10-21 13:33 ` Rafael J. Wysocki
2014-10-24 14:30 ` Lorenzo Pieralisi
2014-10-24 14:30 ` Lorenzo Pieralisi
2014-10-27 3:34 ` Michael Ellerman [this message]
2014-10-27 3:34 ` Michael Ellerman
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=1414380870.24967.0.camel@concordia \
--to=mpe@ellerman.id.au \
--cc=benh@kernel.crashing.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=preeti@linux.vnet.ibm.com \
--cc=rjw@rjwysocki.net \
--cc=shreyas@linux.vnet.ibm.com \
/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.