mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Fabio Comolli <fabio.comolli@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Len Brown <lenb@kernel.org>, Matthew Garrett <mjg@redhat.com>,
	Cristiano Prisciandaro <cristiano.p@solnet.ch>,
	Dave Jones <davej@redhat.com>,
	cpufreq@vger.kernel.org, linux-kernel@vger.kernel.org,
	tom@compton.nu
Subject: Re: [PATCH 1/1] cpufreq: eeepc 900 frequency scaling driver
Date: Tue, 17 Mar 2009 09:30:48 +0100	[thread overview]
Message-ID: <b637ec0b0903170130n68754d9eu504ad6b6f4330d89@mail.gmail.com> (raw)
In-Reply-To: <20090316082952.GA1963@elf.ucw.cz>

Well, I see that this thread has resumed after three months of being idle.
Is there a chance that either Cristiano's or Tom's version can be included?

By the way, I currently run my eeepc 900 with cpufreq disabled.
Looking at the patch, with Tom's mods to eeepc_laptop I could do the
same, am I right? I see only an include for cpufreq.h and nothing
else.

Thanks,
Fabio



On Mon, Mar 16, 2009 at 9:29 AM, Pavel Machek <pavel@ucw.cz> wrote:
> On Mon 2009-03-16 00:24:18, Len Brown wrote:
>>
>> On Tue, 2 Dec 2008, Pavel Machek wrote:
>>
>> > On Tue 2008-12-02 16:15:21, Matthew Garrett wrote:
>> > > On Sun, Nov 23, 2008 at 07:04:09PM +0100, Pavel Machek wrote:
>> > >
>> > > > Is this really needed? Could we simply talk to the cpu directly,
>> > > > without help of ACPI?
>> > >
>> > > No. The ACPI write ends up talking to the embedded controller and some
>> > > io ports.
>> >
>> > Oops... I always knew that eee-s are broken by design (reporting
>> > battery percent as mWh, etc...) but I did not realize how bad it
>> > is. (ACPI has perfectly standard cpu frequency scaling interface, even
>> > if it is not used too often these days....)
>>
>> Huh?
>>
>> What cpufreq driver is deployed more broadly than acpi-cpufreq?
>> AFAIK, Linux uses it on nearly every ACPI compliant Intel-based
>> system that has frequency scaling.
>
> Problem seems to be that eee uses custom ACPI methods
> (switch_to_fast_clock(0/1)-like), not anything acpi-cpufreq could
> drive... Broken by design :-(.
>                                                                        Pavel
> --
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

  reply	other threads:[~2009-03-17  8:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-23 15:27 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 [this message]
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
2008-11-24 23:02       ` Cristiano Prisciandaro
2009-04-05  7:43         ` [Acpi4asus-user] " 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=b637ec0b0903170130n68754d9eu504ad6b6f4330d89@mail.gmail.com \
    --to=fabio.comolli@gmail.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=cristiano.p@solnet.ch \
    --cc=davej@redhat.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg@redhat.com \
    --cc=pavel@ucw.cz \
    --cc=tom@compton.nu \
    /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

all inboxes | Powered by JetHome®