public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Schlichter <thomas.schlichter@web.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "Daniel Lezcano" <daniel.lezcano@linaro.org>,
	"Len Brown" <lenb@kernel.org>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"Peter De Schrijver" <pdeschrijver@nvidia.com>,
	"Andreas Müller" <goo@stapelspeicher.org>,
	"Julius Werner" <jwerner@chromium.org>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpuidle: fix new C-states not functional after AC disconnect
Date: Fri, 18 Jan 2013 21:34:29 +0100	[thread overview]
Message-ID: <1755809.pcSThauESZ@netbook> (raw)
In-Reply-To: <11530988.U26HMGnFLa@vostro.rjw.lan>

[-- Attachment #1: Type: text/plain, Size: 2391 bytes --]

Dear Rafael,

thank you for applying Daniel's patch. I tested 3.8-rc4 and found that one 
patch ist still missing to fix the problem of not usable C-state after 
disconnect. I had it attached with my last e-mail as patch 1. For your 
conveniency, I have attached it here again.

With that patch the problem is fixed for me. So please consider applying this, 
too.

Kind regards,
  Thomas

Am Sonntag, 13. Januar 2013, 21:04:45 schrieb Rafael J. Wysocki:
> On Sunday, January 13, 2013 03:41:34 PM Daniel Lezcano wrote:
> > On 01/13/2013 01:34 PM, Thomas Schlichter wrote:
> > > Hi,
> > > 
> > > there is a long-standing regression about new C-states not working after
> > > disconnecting AC power from a laptop if the cpuidle driver "acpi-idle"
> > > is
> > > used. It was reported here:
> > > 
> > > [1] https://bugzilla.kernel.org/show_bug.cgi?id=42870  (March 5th 2012)
> > > [2] https://bugzilla.kernel.org/show_bug.cgi?id=43349  (June 7th 2012)
> > > [3] https://lkml.org/lkml/2012/10/16/518   (October 19th 2012)
> > > 
> > > In [1] Andreas proposed a patch that initialized the missing power_usage
> > > values from within acpi_idle in the same way as cpuidle does.
> > > In [2] I proposed a patch to use the power values provided by ACPI to
> > > initialize the power_usage variables.
> > > In [3] Julius proposed a patch to call the initialization function
> > > set_power_states()  not only once, but always when the C-states change.
> > > 
> > > Currently, Daniel Lezcano seems to be working on an intrusive change of
> > > not
> > > using the power_usage value at all for choosing a C-state:
> > > 
> > > [4] https://lkml.org/lkml/2012/12/14/155
> > > 
> > > As I could not find any of these patches in any git trees to be merged
> > > for
> > > 3.8, I propose an other, least intrusive patch for the time being. It is
> > > attached an initializes _all_ power_usage values in the first place.
> > > 
> > > As this is a real power consumption regression since 3.2, I really ask
> > > you to apply anything and push it to stable, too!
> > 
> > Rafael, is possible to apply the patch [1/2] I previously sent ?
> > 
> > https://patchwork.kernel.org/patch/1878691/
> 
> I need to talk about this with Len.  That should happen tomorrow if
> everything goes well.
> 
> > So we get this bug fixed.
> > 
> > I will resend the patch [2/2] as soon as possible.
> 
> OK
> 
> Thanks,
> Rafael

[-- Attachment #2: 0001-Get-power-info-before-updating-the-C-states.patch --]
[-- Type: text/x-patch, Size: 1013 bytes --]

>From fc300f4fefff59fe1029bf7852ea32d957145821 Mon Sep 17 00:00:00 2001
From: Thomas Schlichter <thomas.schlichter@web.de>
Date: Sun, 2 Sep 2012 14:35:34 +0200
Subject: [PATCH] Get power info before updating the C-states

acpi_processor_get_power_info() has to be called before
acpi_processor_setup_cpuidle_states() to have the latest
information available. This fixes the missing C-state information
after AC-->DC transition.

Signed-off-by: Thomas Schlichter <thomas.schlichter@web.de>
---
 drivers/acpi/processor_idle.c |    1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/acpi/processor_idle.c b/drivers/acpi/processor_idle.c
index f1a5da4..17ed60b 100644
--- a/drivers/acpi/processor_idle.c
+++ b/drivers/acpi/processor_idle.c
@@ -1149,6 +1149,7 @@ int acpi_processor_cst_has_changed(struct acpi_processor *pr)
 		}
 
 		/* Populate Updated C-state information */
+		acpi_processor_get_power_info(pr);
 		acpi_processor_setup_cpuidle_states(pr);
 
 		/* Enable all cpuidle devices */
-- 
1.7.10.4


  reply	other threads:[~2013-01-18 20:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-13 12:34 [PATCH] cpuidle: fix new C-states not functional after AC disconnect Thomas Schlichter
2013-01-13 14:41 ` Daniel Lezcano
2013-01-13 20:04   ` Rafael J. Wysocki
2013-01-18 20:34     ` Thomas Schlichter [this message]
2013-01-18 22:24       ` Thomas Schlichter
2013-01-31  3:52     ` Julius Werner
2013-01-31 13:21       ` Rafael J. Wysocki
  -- strict thread matches above, loose matches on Subject: below --
2013-01-13 19:30 Sedat Dilek
2013-01-13 20:36 ` Sedat Dilek
2013-01-13 20:44   ` Daniel Lezcano
2013-01-13 20:49     ` Sedat Dilek
2013-01-30 20:23     ` Thomas Schlichter

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=1755809.pcSThauESZ@netbook \
    --to=thomas.schlichter@web.de \
    --cc=daniel.lezcano@linaro.org \
    --cc=goo@stapelspeicher.org \
    --cc=jwerner@chromium.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pdeschrijver@nvidia.com \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox