All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Hughes <tom@compton.nu>
To: Thomas Renninger <trenn@suse.de>
Cc: Cristiano Prisciandaro <cristiano.p@solnet.ch>,
	Dave Jones <davej@redhat.com>,
	cpufreq@vger.kernel.org, linux-kernel@vger.kernel.org,
	acpi4asus-user@lists.sourceforge.net
Subject: Re: [PATCH 1/1] cpufreq: eeepc 900 frequency scaling driver
Date: Mon, 24 Nov 2008 16:46:57 +0000	[thread overview]
Message-ID: <492ADA81.4070904@compton.nu> (raw)
In-Reply-To: <200811241736.53067.trenn@suse.de>

Thomas Renninger wrote:

> Oh, they are part of this general Asus \\_SB.ATKD device, which is only
> used by asus_laptop.c until now?

I believe eeepc-laptop is also accessing the same device - at least it 
is calling other methods defined in the same part of the DSDT although 
it doesn't seem to be using that name to reach them.

> Some more questions:
> Why are they providing their own cpufreq interface and not following the
> spec (providing _PSS, ..)?
> Could it be that you are only throttling the CPU?
>
> Are these functions already used by the ACPI tables internally?
>   - could be dangerous
>   - could be helpful -> Is there some upper level device/interface in ASL?
> 
> Could it happen that upcoming machines provide this interface (the two ACPI 
> functions) and also can do real CPU frequency/volt switching, e.g. via 
> acpi-cpufreq?

Well the recent eee's are all Atom based, which I assume has proper 
SpeedStep support but the early ones have a Celeron processor.

The history is that the original eee, the 701, was underclocking a 
900MHz CPU at 630Mhz and in the 900 they added support for running at 
full speed with the BIOS able to switch between the two speeds. I assume 
it just changes the clock multiplier or something.

The 901 and later of course use the Atom and presumably work differently.

Tom

-- 
Tom Hughes (tom@compton.nu)
http://www.compton.nu/

  parent reply	other threads:[~2008-11-24 16:47 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-23 15:27 [PATCH 1/1] cpufreq: eeepc 900 frequency scaling driver Cristiano Prisciandaro
2008-11-23 18:04 ` Pavel Machek
2008-12-02 16:15   ` Matthew Garrett
2008-12-02 20:14     ` Pavel Machek
2009-03-16  4:24       ` Len Brown
2009-03-16  8:29         ` Pavel Machek
2009-03-17  8:30           ` Fabio Comolli
2009-03-17  8:59             ` Fabio Comolli
2008-11-24  9:38 ` Tom Hughes
2008-11-24 15:13   ` Thomas Renninger
2008-11-24 16:36     ` Thomas Renninger
2008-11-24 16:41       ` [Acpi4asus-user] " Corentin Chary
2008-11-24 16:48         ` Tom Hughes
2008-11-24 16:58           ` Corentin Chary
2008-11-24 17:07             ` Tom Hughes
2008-11-24 16:46       ` Tom Hughes [this message]
2008-11-24 23:02       ` Cristiano Prisciandaro
2009-04-05  7:43         ` [Acpi4asus-user] " Corentin Chary
2009-04-05  7:43           ` Corentin Chary
2009-04-05 10:20           ` Matthew Garrett
2009-04-05 11:39             ` Grigori Goronzy
2008-11-24 16:39     ` Tom Hughes
2008-11-24 19:09   ` Cristiano Prisciandaro
2008-12-03 19:26   ` Tom Hughes
2008-12-04  1:57     ` Thomas Renninger
2008-12-05 23:05       ` Tom Hughes
2008-12-06 16:35         ` Matthew Garrett
2008-12-07 15:55           ` Tom Hughes
2008-12-09 12:36             ` Pavel Machek

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=492ADA81.4070904@compton.nu \
    --to=tom@compton.nu \
    --cc=acpi4asus-user@lists.sourceforge.net \
    --cc=cpufreq@vger.kernel.org \
    --cc=cristiano.p@solnet.ch \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trenn@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.