All of lore.kernel.org
 help / color / mirror / Atom feed
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

WARNING: multiple messages have this Message-ID (diff)
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 tr
Date: Tue, 12 Feb 2013 19:42:32 +0000	[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

  parent reply	other threads:[~2013-02-12 19:42 UTC|newest]

Thread overview: 59+ 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  7:34 ` Stephen Rothwell
2013-02-11 18:22 ` Bjorn Helgaas
2013-02-11 18:22   ` Bjorn Helgaas
2013-02-11 23:23 ` Len Brown
2013-02-11 23:23   ` Len Brown
2013-02-12 17:35   ` Sam Ravnborg
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:01       ` Should SPARC use cpuidle? (was: linux-next: build failure after merge of the final tree (acpi tree r Len Brown
2013-02-12 18:03       ` Should SPARC use cpuidle? Len Brown
2013-02-12 18:03         ` Len Brown
2013-02-12 19:36         ` Sam Ravnborg
2013-02-12 19:36           ` Sam Ravnborg
2013-02-12 19:42       ` Sam Ravnborg [this message]
2013-02-12 19:42         ` Should SPARC use cpuidle? (was: linux-next: build failure after merge of the final tree (acpi tr Sam Ravnborg
  -- strict thread matches above, loose matches on Subject: below --
2017-11-30  3:46 linux-next: build failure after merge of the akpm-current tree Stephen Rothwell
2017-11-30  3:46 ` Stephen Rothwell
2014-04-22  6:22 linux-next: build failure after merge of the audit tree Stephen Rothwell
2014-04-22  6:22 ` Stephen Rothwell
2014-04-22 15:56 ` Richard Guy Briggs
2014-04-22 15:56   ` Richard Guy Briggs
2014-04-22 16:32 ` Eric Paris
2014-04-22 16:32   ` Eric Paris
2014-04-22 21:27   ` Stephen Rothwell
2014-04-22 21:27     ` Stephen Rothwell
2012-06-12  4:54 linux-next: build failure after merge of the final tree (pci tree related) Stephen Rothwell
2012-06-12  4:54 ` Stephen Rothwell
2012-06-12 15:31 ` Bjorn Helgaas
2012-06-12 15:31   ` Bjorn Helgaas
2012-06-12 15:31   ` Bjorn Helgaas
2012-06-13  0:50   ` Stephen Rothwell
2012-06-13  0:50     ` Stephen Rothwell
2012-06-13 23:20     ` Bjorn Helgaas
2012-06-13 23:20       ` Bjorn Helgaas
2011-06-09  7:27 linux-next: build failure after merge of the final tree (staging related) Stephen Rothwell
2011-06-09 18:41 ` Greg KH
2011-06-09 19:22   ` Greg KH
2011-06-10  6:05     ` Stephen Rothwell
2011-06-10  6:09       ` Stephen Rothwell
2011-06-10 22:34         ` Greg KH
2011-06-15  4:21           ` Stephen Rothwell
2011-06-16 19:14             ` Greg KH
2011-06-23  0:35               ` Stephen Rothwell
2011-06-23 21:51                 ` Greg KH
2011-06-24  0:00                   ` Stephen Rothwell
2011-06-27 21:45                     ` Greg KH
2011-06-28  0:16                       ` Stephen Rothwell
2011-06-15 12:05       ` Geert Uytterhoeven
2011-06-15 12:05         ` Geert Uytterhoeven
2011-06-15 15:47         ` Greg KH
2011-06-15 15:47           ` linux-next: build failure after merge of the final tree (staging Greg KH
2011-06-15 14:35       ` [PATCH] arch/tile: remove useless set_fixmap_nocache() macro Chris Metcalf
2011-06-15 14:35       ` Chris Metcalf
2011-06-15 14:35         ` Chris Metcalf
2011-06-15 14:35         ` Chris Metcalf
2011-06-15 14:35         ` Chris Metcalf
2011-06-09 19:52   ` linux-next: build failure after merge of the final tree (staging related) Henry Ptasinski
2011-06-09 20:19     ` Greg KH

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.org \
    --cc=davem@davemloft.net \
    --cc=len.brown@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=sparclinux@vger.kernel.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.