From: Dominik Brodowski <linux-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
To: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>,
len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: C2/C3 don't do anything
Date: Sat, 5 Feb 2005 08:39:21 +0100 [thread overview]
Message-ID: <20050205073921.GD8019@dominikbrodowski.de> (raw)
In-Reply-To: <20050204225527.GA30585-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
On Fri, Feb 04, 2005 at 02:55:28PM -0800, Tony Lindgren wrote:
> > > > Should we have some extra code to scan the southbridges,
> > >
> > > Definitely. There is already some "errata" handling in the processor module,
> > > possibly this could get extended.
> >
> > I'm still using the patch to enable C3 on ICHx-M I once posted. Basically,
> > it provided a valid PM2_CNT_BLK address in case the OEM had forgotten to do
> > that, which in turn enabled C3 by providing a valid ARB_DIS address
> > (provided P_LVL3_LAT is valid).
>
> I have some code for the amd76x_pm module that can be modified for
> scanning various southbridges. And then add functions for the
> to enable them. I don't know when I'll have time to play with that
> though.
>
> This could be a separate module to start with, and then get integrated
> into the ACPI code later on.
Or this could be an extension of
drivers/acpi/processor_core.c::acpi_processor_errata() from the beginning.
Len, what do you think?
Dominik
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
prev parent reply other threads:[~2005-02-05 7:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-03 3:46 C2/C3 don't do anything Tony Lindgren
[not found] ` <20050203034639.GA29164-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2005-02-04 20:30 ` Dominik Brodowski
[not found] ` <20050204203026.GA8049-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2005-02-04 21:34 ` Karol Kozimor
[not found] ` <20050204213407.GA26515-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2005-02-04 22:55 ` Tony Lindgren
[not found] ` <20050204225527.GA30585-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2005-02-05 7:39 ` Dominik Brodowski [this message]
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=20050205073921.GD8019@dominikbrodowski.de \
--to=linux-x3ehhduj6siigcdfoqap7bvvk+yq3zxh@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.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