From: "Langsdorf, Mark" <mark.langsdorf@amd.com>
To: "'joss@debian.org'" <joss@debian.org>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Athlon L110 CPU and powernow-k8
Date: Mon, 19 Apr 2010 06:43:48 -0700 [thread overview]
Message-ID: <DDE95BDD51FB774B804A9C029E735EE103E9BF5129@sausexmbp02.amd.com> (raw)
In-Reply-To: <20100418102608.GA29846@a1.tnic>
> Date: Fri, 16 Apr 2010 22:40:58 +0200
> From: Josselin Mouette <joss@debian.org>
> To: linux-kernel@vger.kernel.org
> Subject: Athlon L110 CPU and powernow-k8
> X-Mailer: Evolution 2.29.92.1
> Message-ID: <1271450458.6794.33.camel@tomoyo>
>
> In both cases, the issue is the same: the DSDT table provided by the
> BIOS does not include the P-states. Waiting for a hypothetical BIOS
> update that would fix this bug requires some faith that I
> don't have. It is possible to work around this by compiling the
> kernel with a custom DSDT table with appropriate P-states patched
> in, however I consider this a developer hack.
>
> I wonder what is possible to do to support this CPU correctly in the
> kernel. The only sane solution I can think of is to hardcode the
> P-states for this CPU model in the powernow-k8 driver itself.
I think that hard-coding P-states into the PowerNow
driver is not a mantainable solution.
I don't quite understand why the you think that
a custom DSDT as a BIOS hack, but think that
adding custom frequencies to the driver itself is
acceptable.
The last time this issue came up on cpufreq, Dave
Jones nixed a general solution to add custom P-states
through the driver on the grounds that people would
undervolt their systems, causing a lot of screwy,
unpredictable behavior. I agreed with his opinion
then and I don't see anything in this mesage to
change that view.
--Mark Langsdorf
Operating System Research Center
AMD
next parent reply other threads:[~2010-04-19 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100418102608.GA29846@a1.tnic>
2010-04-19 13:43 ` Langsdorf, Mark [this message]
2010-04-19 18:42 ` Athlon L110 CPU and powernow-k8 Josselin Mouette
2010-04-16 20:40 Josselin Mouette
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=DDE95BDD51FB774B804A9C029E735EE103E9BF5129@sausexmbp02.amd.com \
--to=mark.langsdorf@amd.com \
--cc=joss@debian.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).