From: Michael Ellerman <michael@ellerman.id.au>
To: Deepthi Dharwar <deepthi@linux.vnet.ibm.com>
Cc: linux-pm@lists.linux-foundation.org,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] cpuidle/powernv: cpuidle backend driver for powernv
Date: Wed, 24 Jul 2013 00:06:45 +1000 [thread overview]
Message-ID: <20130723140645.GI31944@concordia> (raw)
In-Reply-To: <20130723090137.7291.36657.stgit@deepthi.in.ibm.com>
On Tue, Jul 23, 2013 at 02:31:41PM +0530, Deepthi Dharwar wrote:
> This patch implements a back-end cpuidle driver for
> powernv calling power7_nap and snooze idle states.
> This can be extended by adding more idle states
> in the future to the existing framework.
Other than the state table and a few minor details this looks almost
identical to the pseries driver. Can we not have a single version in
sysdev and isolate just the differences?
cheers
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <michael@ellerman.id.au>
To: Deepthi Dharwar <deepthi@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org,
linux-pm@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] cpuidle/powernv: cpuidle backend driver for powernv
Date: Wed, 24 Jul 2013 00:06:45 +1000 [thread overview]
Message-ID: <20130723140645.GI31944@concordia> (raw)
In-Reply-To: <20130723090137.7291.36657.stgit@deepthi.in.ibm.com>
On Tue, Jul 23, 2013 at 02:31:41PM +0530, Deepthi Dharwar wrote:
> This patch implements a back-end cpuidle driver for
> powernv calling power7_nap and snooze idle states.
> This can be extended by adding more idle states
> in the future to the existing framework.
Other than the state table and a few minor details this looks almost
identical to the pseries driver. Can we not have a single version in
sysdev and isolate just the differences?
cheers
next prev parent reply other threads:[~2013-07-23 14:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 9:01 [PATCH 0/3] cpuidle: (powernv) cpuidle driver Deepthi Dharwar
2013-07-23 9:01 ` Deepthi Dharwar
2013-07-23 9:01 ` [PATCH 1/3] cpuidle/powernv: cpuidle backend driver for powernv Deepthi Dharwar
2013-07-23 9:01 ` Deepthi Dharwar
2013-07-23 14:06 ` Michael Ellerman [this message]
2013-07-23 14:06 ` Michael Ellerman
2013-07-24 9:58 ` Deepthi Dharwar
2013-07-24 9:58 ` Deepthi Dharwar
2013-07-27 5:27 ` [linux-pm] " Daniel Lezcano
2013-07-27 5:27 ` Daniel Lezcano
2013-07-29 14:39 ` Deepthi Dharwar
2013-07-29 14:39 ` Deepthi Dharwar
2013-07-29 14:53 ` Daniel Lezcano
2013-07-29 14:53 ` Daniel Lezcano
2013-07-30 3:51 ` Deepthi Dharwar
2013-08-02 10:32 ` Preeti U Murthy
2013-07-23 9:01 ` [PATCH 2/3] cpuidle/powernv: Enable idle powernv cpu to call into the cpuidle framework Deepthi Dharwar
2013-07-23 9:01 ` Deepthi Dharwar
2013-07-27 5:29 ` Daniel Lezcano
2013-07-27 5:29 ` Daniel Lezcano
2013-07-29 14:27 ` Deepthi Dharwar
2013-07-29 14:44 ` Daniel Lezcano
2013-07-30 3:50 ` Deepthi Dharwar
2013-07-23 9:02 ` [PATCH 3/3] cpuidle/powernv: Support smt-snooze-delay parameter in powernv idle Deepthi Dharwar
2013-07-23 9:02 ` Deepthi Dharwar
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=20130723140645.GI31944@concordia \
--to=michael@ellerman.id.au \
--cc=deepthi@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linuxppc-dev@lists.ozlabs.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.