public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Erik Slagter <erik@slagter.name>
To: linux-acpi@vger.kernel.org
Subject: RE: [PATCH] amd76x_pm: C3 powersaving for AMD K7
Date: Fri, 03 Feb 2006 10:35:12 +0100	[thread overview]
Message-ID: <1138959312.18273.14.camel@localhost.localdomain> (raw)
In-Reply-To: <F7DC2337C7631D4386A2DF6E8FB22B3005EFE84D@hdsmsx401.amr.corp.intel.com>

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

On Fri, 2006-02-03 at 03:45 -0500, Brown, Len wrote:
>  >... I disagree with Len in two points:
> >- I cannot see a problem witch cache snooping.
> >  The AMD-768 docs clearly
> >  states that trying to snoop the cache while in C3 is a resume event.
> 
> Certainly the BIOS writer also had access to that document, plus
> documents we do not see, yet they decided NOT to enable C2/C3.

You are probably right, but I remain suspicious that the BIOS writers
simply didn't want to go through the trouble of implementing and testing
the whole thing, presumable because:

 - who wants to have power saving on a dual processor board anyway
(well, I do, but that's just me)
 - every line of code takes time to write and test and debug, it
wouldn't quite be the first occurrence of buggy or marginal "firmware",
have a look at some harddisks :-(

If I remember correctly there was some sort of windows driver supplied
with the board to enable power saving. This would suggest that in
principle there is no reason it cannot work.

> Who defines the "right way"?  Is it guaranteed to work on all
> models and all configurations?  Exactly what is the reward
> for the cost we'd be paying and the risk we'd be taking?

The advantage is that we're talking about only 1.5 chipset here with
very few revisions. Okay, this still leaves the board manufacturer that
can do what they want.

> If somebody from AMD steps forth and says that hey, their hardware
> is broken if used in the standard way, but that this "logic around"
> is a valid model-specific workaround -- then we have something
> that MAYBE we can work with.

Yeah, that would be nice. But I guess _someone_ will have to poke them a
bit first...


[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2771 bytes --]

  reply	other threads:[~2006-02-03  9:35 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-03  8:45 [PATCH] amd76x_pm: C3 powersaving for AMD K7 Brown, Len
2006-02-03  9:35 ` Erik Slagter [this message]
2006-02-03 10:31   ` Pavel Troller
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
  -- strict thread matches above, loose matches on Subject: below --
2006-02-03 18:40 Brown, Len
2006-02-04 10:31 ` Erik Slagter
2006-02-04 10:49   ` Pavel Troller
2006-02-03 18:28 Brown, Len
2006-02-03 18:20 Brown, Len
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-02-03  9:21 ` Erik Slagter
2006-02-03  9:33   ` Pavel Troller
2006-02-03  9:39     ` Erik Slagter
2006-02-03 10:14       ` Pavel Troller
2006-02-03 10:28         ` Erik Slagter
2006-02-01 18:11 Brown, Len
2006-02-01 18:18 ` Erik Slagter
2006-02-01 18:40   ` Tony Lindgren
2006-02-01 19:13 ` Joerg Sommrey
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=1138959312.18273.14.camel@localhost.localdomain \
    --to=erik@slagter.name \
    --cc=linux-acpi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox