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: Wed, 17 Mar 2010 23:55:45 +0100	[thread overview]
Message-ID: <b637ec0b1003171555j43a50997sb4f5a781b0037b0f@mail.gmail.com> (raw)
In-Reply-To: <71cd59b01003170122h1ef767a3ma186e7ef278d73a1@mail.gmail.com>

Hi

On Wed, Mar 17, 2010 at 9:22 AM, Corentin Chary
<corentin.chary@gmail.com> wrote:
> On Tue, Mar 16, 2010 at 9:31 PM, Fabio Comolli <fabio.comolli@gmail.com> wrote:
>> Hi.
>>
>> On Tue, Mar 16, 2010 at 7:54 AM, Corentin Chary
>> <corentin.chary@gmail.com> wrote:
>>> On Sat, Mar 13, 2010 at 1:50 PM, Fabio Comolli <fabio.comolli@gmail.com> wrote:
>>>> 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
>>>>
>>>
>>> Here is what I can read in your DSDT:
>>>
>>> When INIT or _Q31 is called, the bios check the the battery is
>>> present, and call FSBA(0) or FSBA(1).
>>> _Q31 seems to be called by an hotkey, could you run "acpi_listen" and
>>> search the hotkey that generate 0x50 or 0x51 ?
>>
>> This is the output requested.
>>
>> hotkey ATKD 0000002e 00000000
>> hotkey ATKD 0000002f 00000000
>> hotkey ATKD 00000030 00000000
>> hotkey ATKD 00000012 00000000
>> hotkey ATKD 00000013 00000000
>> hotkey ATKD 00000014 00000000
>> hotkey ATKD 00000015 00000000
>> hotkey ATKD 00000010 00000000
>> button/sleep SLPB 00000080 00000001
>> hotkey ATKD 00000010 00000001
>
> None of thesed generate 0x50 or 0x51, may be somehting else :/
>
>

Found it!

Plugging the AC gives:

ac_adapter AC0 00000080 00000001
battery BAT0 00000080 00000001
hotkey ATKD 00000050 00000002

And unplugging gives:

battery BAT0 00000080 00000001
ac_adapter AC0 00000080 00000001
ac_adapter AC0 00000080 00000000
battery BAT0 00000080 00000001
hotkey ATKD 00000051 00000002
battery BAT0 00000080 00000001
ac_adapter AC0 00000080 00000000

However, the cpufv value is not affected at all.

>
> --
> Corentin Chary
> http://xf.iksaif.net
>

Regards,
Fabio

  reply	other threads:[~2010-03-17 22:55 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
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 [this message]
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=b637ec0b1003171555j43a50997sb4f5a781b0037b0f@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®