public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joerg Sommrey <jo@sommrey.de>
To: "Brown, Len" <len.brown@intel.com>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	arjan@infradead.org, Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH] amd76x_pm: C3 powersaving for AMD K7
Date: Wed, 1 Feb 2006 20:13:18 +0100	[thread overview]
Message-ID: <20060201191318.GC17225@sommrey.de> (raw)
In-Reply-To: <F7DC2337C7631D4386A2DF6E8FB22B3005E907CA@hdsmsx401.amr.corp.intel.com>

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

On Wed, Feb 01, 2006 at 01:11:36PM -0500, Brown, Len wrote:
>  
> >>  This patch can also be found at
> >>  http://www.sommrey.de/amd76x_pm/amd76x_pm-2.6.15-4.patch
> >> 
> >>  In this version more locking was added to make sure all or 
> >>  no CPU enter C3 mode.
> >> 
> >>  Signed-off-by: Joerg Sommrey <jo@sommrey.de>
> >
> >Thanks.  I'll merge this into -mm and shall plague the ACPI 
> >guys with it. 
> >They have said discouraging things about board-specific drivers in the
> >past.  We shall see.
> 
> Linux/ACPI has had generic supported SMP deep (> C1) C-states
> for a few months now and AFAIK it is working fine.
> Why is a platform specific driver needed for these boards?

I didn't get the ACPI C3 states working.

-jo

-- 
-rw-r--r--  1 jo users 63 2006-02-01 19:10 /home/jo/.signature

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2006-02-01 19:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-01 18:11 [PATCH] amd76x_pm: C3 powersaving for AMD K7 Brown, Len
2006-02-01 18:18 ` Erik Slagter
2006-02-01 18:40   ` Tony Lindgren
2006-02-01 19:13 ` Joerg Sommrey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-02-03 18:28 Brown, Len
2006-02-03  8:45 Brown, Len
2006-02-03 14:16 ` Joerg Sommrey
2006-02-03 15:59 ` Juhani Rautiainen
2006-02-03 17:02   ` Erik Slagter
2006-02-08 20:10   ` Pavel Machek
2006-02-02 22:24 Joerg Sommrey
2006-02-02 22:37 ` Andrew Morton
2006-02-03  7:03   ` Joerg Sommrey
2006-02-02 22:43 ` Dave Jones
2006-02-02  1:35 Brown, Len
2006-02-02  1:50 ` Alan Cox
2006-02-02  9:50   ` Erik Slagter
2006-02-02 19:38     ` Tony Lindgren
2006-01-31 18:55 Joerg Sommrey
2006-02-01  3:34 ` Andrew Morton
2006-02-01 10:25   ` Erik Slagter
2006-02-01 17:20   ` Tony Lindgren

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=20060201191318.GC17225@sommrey.de \
    --to=jo@sommrey.de \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony@atomide.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