From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Rob Herring <robherring2@gmail.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Olof Johansson <olof@lixom.net>,
Rob Herring <rob.herring@calxeda.com>,
Len Brown <len.brown@intel.com>
Subject: Re: [PATCH] cpuidle: add Calxeda SOC idle support
Date: Sat, 24 Nov 2012 11:03:30 +0100 [thread overview]
Message-ID: <2676657.zDjyfqIDdm@vostro.rjw.lan> (raw)
In-Reply-To: <201211122200.07901.arnd@arndb.de>
On Monday, November 12, 2012 10:00:07 PM Arnd Bergmann wrote:
> On Wednesday 07 November 2012, Rob Herring wrote:
> > From: Rob Herring <rob.herring@calxeda.com>
> >
> > Add support for core powergating on Calxeda platforms. Initially, this
> > supports ECX-1000 (highbank), but support will be added for ECX-2000
> > later.
> >
> > Signed-off-by: Rob Herring <rob.herring@calxeda.com>
> > Cc: Len Brown <len.brown@intel.com>
> > Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
>
> Acked-by: Arnd Bergmann <arnd@arndb.de>
>
> > It's not really clear where we want ARM cpuidle drivers. We're moving
> > everything else out of arch/arm, and my understanding is Len doesn't want
> > them in drivers/idle. It seems kind of silly to me to have the framework
> > and drivers in 2 places. I've put this in drivers/cpuidle, but it doesn't
> > make any difference to me.
>
> Fine with me. I just don't want in in arch/arm because I'm guessing this will
> be shared with arm64, which in turn shares idle (and other) drivers with various
> powerpc, mips and x86 socs.
Applied to linux-pm.git/linux-next as v3.8 material.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2012-11-24 9:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 23:23 Rob Herring
2012-11-12 22:00 ` Arnd Bergmann
2012-11-24 10:03 ` Rafael J. Wysocki [this message]
2012-11-24 23:21 ` Olof Johansson
2012-11-24 23:32 ` Rafael J. Wysocki
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=2676657.zDjyfqIDdm@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=arnd@arndb.de \
--cc=len.brown@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=rob.herring@calxeda.com \
--cc=robherring2@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®