mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Fabio Comolli <fabio.comolli@gmail.com>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: ACPI mailing list <linux-acpi@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Len Brown <lenb@kernel.org>
Subject: Re: Possible bug in eeepc-laptop.c - EeePC 900
Date: Sat, 13 Mar 2010 13:50:35 +0100	[thread overview]
Message-ID: <b637ec0b1003130450n3293ee78wc58e08a9bbcefe17@mail.gmail.com> (raw)
In-Reply-To: <71cd59b01003130116h4265769v9e1dae95361629ce@mail.gmail.com>

Well, I'm confused.

I rebooted with the "vanilla" eeepc-laptop.c and I'm sorry to say that
the situation it's not like the one I described in the post I wrote 2
days ago. Actually the situation with the patch reverted is the same I
have with the patch applied.

What I mean is that if I boot on AC power /proc/cpuinfo always reports
900MHz and 1800 bogomips. It I boot on battery /proc/cpuinfo always
reports 630MHz and 1260 bogomips. Plugging / unplugging the AC does
not change the situation. Only reboot does.

But the cpufv interface does indeed seem to work, as glxgears and
stellarium show the frame rate change accordingly to the powersave /
performance selection.

So my question is: what does really the cpufv interface do? Is it
supposed to change the processor frequency? Or does it change
something else?

And if the answer to the latest question is affirmative, why
/proc/cpuinfo seems to ignore it?

Sorry for the confusion.
Regards,
Fabio





On Sat, Mar 13, 2010 at 10:16 AM, Corentin Chary
<corentin.chary@gmail.com> wrote:
> On Fri, Mar 12, 2010 at 9:07 PM, Fabio Comolli <fabio.comolli@gmail.com> wrote:
>> Hi
>>
>> On Fri, Mar 12, 2010 at 9:49 AM, Corentin Chary
>> <corentin.chary@gmail.com> wrote:
>>> On Thu, Mar 11, 2010 at 10:28 PM, Fabio Comolli <fabio.comolli@gmail.com> wrote:
>>>> Hi.
>>>>
>>>> On Tue, Mar 9, 2010 at 11:58 PM, Fabio Comolli <fabio.comolli@gmail.com> wrote:
>>>>> Hi.
>>>>> I have an EeePC 900 running 2.6.34-rc1.
>>>>>
>>>>> If I boot it on AC the cpu runs at full speed, 900MHz; if I boot it on
>>>>> battery it runs only at 630Mhz. Plugging / unplugging the AC does not
>>>>> change the cpu frequency. Only a reboot can change the situation.
>>>>>
>>>>> I already tried to echo 0 or 1 to the
>>>>> /sys/devices/platform/eeepc/cpufv file; no effects, even if the file
>>>>> changes its value.
>>>>>
>>>>> This is not a regression from 2.6.33: this behavior is also present in
>>>>> that version.
>>>>>
>>>>> Does this ring any bells? This is really annoying, especially when
>>>>> trying to watch a movie on battery. Also 3D apps show a 30%
>>>>> performance drop, as expected.
>>>>>
>>>>> Regards,
>>>>> Fabio
>>>>
>>>> Well, it turns out that this is indeed a regression, but I don't know
>>>> from which kernel version.
>>>> I reverted (not cleanly) this patch:
>>>>
>>>>        http://patchwork.kernel.org/patch/28591
>>>>
>>>> and now
>>>>
>>>>        echo 1 > /sys/devices/platform/eeepc/cpufv
>>>>
>>>> enables the powersave mode and
>>>>
>>>>        echo 0 > /sys/devices/platform/eeepc/cpufv
>>>>
>>>> enables the performance mode.
>>>>
>>>> Tested with the non-benchmark glxgears (275 frames/sec in powersave
>>>> mode and 405 in performance mode) and stellarium (14 frames and 20
>>>> frames).
>>>>
>>>> Regards,
>>>> Fabio
>>>>
>>>
>>> Thanks for the report,
>>> Could you try to add a quick printk to show the value stored in
>>> set_acpi(CM_ASL_CPUFV, value); ?
>>> And also, could you send the result of acpidump ?
>>> Thanks,
>>
>> After the revert there is no set_acpi(CM_ASL_CPUFV, value) anymore.
>> Please find the acpidump in attachment.
>>
>> Regards,
>> Fabio
>
> Yep, I know, but un-revert the patch, and add a printk :p
> Could you also send the result of:
> /* clean boot */
> cat cpufv
> echo 0 > cpufv
> cat cpufv
> echo 1 > cpufv
> cat cpufv
>
> Thanks,
>
> --
> Corentin Chary
> http://xf.iksaif.net
>

  reply	other threads:[~2010-03-13 12:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-11 21:28 Fabio Comolli
2010-03-12  8:49 ` Corentin Chary
2010-03-12 20:07   ` Fabio Comolli
2010-03-13  9:16     ` Corentin Chary
2010-03-13 12:50       ` Fabio Comolli [this message]
2010-03-16  6:54         ` Corentin Chary
2010-03-16 20:31           ` Fabio Comolli
2010-03-17  8:22             ` Corentin Chary
2010-03-17 22:55               ` Fabio Comolli
2010-03-17 14:49         ` Alan Jenkins
2010-03-17 15:40           ` Fabio Comolli
  -- strict thread matches above, loose matches on Subject: below --
2010-03-09 22:58 Fabio Comolli
2010-03-10 13:07 ` Corentin Chary
2010-03-10 13:46   ` Fabio Comolli
2010-03-10 22:09     ` Fabio Comolli
2010-03-10 22:19       ` Fabio Comolli

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=b637ec0b1003130450n3293ee78wc58e08a9bbcefe17@mail.gmail.com \
    --to=fabio.comolli@gmail.com \
    --cc=corentin.chary@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.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

all inboxes | Powered by JetHome®