From: Sam Ravnborg <sam@ravnborg•org>
To: Len Brown <lenb@kernel•org>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Len Brown <len.brown@intel•com>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
"David S. Miller" <davem@davemloft•net>,
sparclinux@vger•kernel.org,
Linux PM list <linux-pm@vger•kernel.org>
Subject: Re: Should SPARC use cpuidle? (was: linux-next: build failure after merge of the final tree (acpi tree related))
Date: Tue, 12 Feb 2013 20:42:32 +0100 [thread overview]
Message-ID: <20130212194232.GA15705@merkur.ravnborg.org> (raw)
In-Reply-To: <511A837B.8020804@kernel.org>
>
> > Do you btw. have any hints how I can convert to the cpu_idle thing you hinted?
>
> If you have exactly 1 idle state, then cpuidle isn't that interesting,
> except, perhaps the standard residency counters. If you have multiple
> states to choose from, cpuidle becomes more valuable.
>
> There are lots of cpuidle users now, including x86's intel_idle,
> processor_idle, and the entire ARM tree.
I think LEON has only a single power-down state.
The APC stuff I know nothing about :-(
So for now I think I will let it be as it is then.
Sam
prev parent reply other threads:[~2013-02-12 19:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 7:34 linux-next: build failure after merge of the final tree (acpi tree related) Stephen Rothwell
2013-02-11 18:22 ` Bjorn Helgaas
2013-02-11 23:23 ` Len Brown
2013-02-12 17:35 ` Sam Ravnborg
2013-02-12 18:01 ` Should SPARC use cpuidle? (was: linux-next: build failure after merge of the final tree (acpi tree related)) Len Brown
2013-02-12 18:03 ` Should SPARC use cpuidle? Len Brown
2013-02-12 19:36 ` Sam Ravnborg
2013-02-12 19:42 ` Sam Ravnborg [this message]
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=20130212194232.GA15705@merkur.ravnborg.org \
--to=sam@ravnborg$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=len.brown@intel$(echo .)com \
--cc=lenb@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-pm@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=sparclinux@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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