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,
	tony@atomide.com, erik@slagter.name, alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH] amd76x_pm: C3 powersaving for AMD K7
Date: Fri, 3 Feb 2006 15:16:51 +0100	[thread overview]
Message-ID: <20060203141651.GA15228@sommrey.de> (raw)
In-Reply-To: <F7DC2337C7631D4386A2DF6E8FB22B3005EFE84D@hdsmsx401.amr.corp.intel.com>

On Fri, Feb 03, 2006 at 03:45:59AM -0500, Brown, Len wrote:
> >- Enabling C2/C3 in the BIOS would be a very bad thing IMHO.
> >  From all he testing with amd76x_pm I found that is very tricky
> >  to go into C2/C3 "the right way".
> 
> 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?
> 
I'd be glad to know "the right way".  All I have is something that seems
to work on a number of boxes :-(
There are some benefits from using it and there are some known issues.
Whoever wants to use this must decide for himself if he's willing to
take the risk.  I'll emphasise this in the documentation.

> >  Simply reading the PM register without a
> >  suitable logic around leads to all kinds of instabilities.  You need
> >  to implement this logic and then enable the hardware.  The BIOS cannot
> >  do this.
> 
> How about if we put it this way...
> If the ACPI maintainer were an AMD employee,
> and he accepted a patch like this specific to Intel hardware --
> a patch that rejects whatever validation Intel, the BIOS
> vendor and the board vendor have put into the product --
> I'd call for his expulsion for ineptitude.

Don't get me wrong: I didn't ask for inclusion of this patch into
something official.  All I want is to tell people: here is something
that is useful for me and might be useful for you.

My point was to say, that *for me* this stuff doesn't look that
dangerous in exactly the environment it was written for:
AMD K7 + 762 + 766/768.

You have a well-defined position not to include this into the ACPI
subsystem, you pointed out your reasons for (not) doing so and I accept
that.

For me there are just a few questions left:
What is an appropiate way of announcing this patch on linux-kernel in the
future?  Does anybody feel uncomfortable with the way I did it in the
past?  Shall I cc: linux-acpi in the future, as suggested by Andrew?

-jo

-- 
-rw-r--r--  1 jo users 63 2006-02-03 14:28 /home/jo/.signature

  reply	other threads:[~2006-02-03 14:17 UTC|newest]

Thread overview: 22+ 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 14:16 ` Joerg Sommrey [this message]
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:28 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-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=20060203141651.GA15228@sommrey.de \
    --to=jo@sommrey.de \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=erik@slagter.name \
    --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