linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Corentin Chary <corentin.chary@gmail.com>
To: Pascal Terjan <pterjan@mandriva.com>, "Zhang, Rui" <rui.zhang@intel.com>
Cc: acpi4asus-user@lists.sourceforge.net,
	linux acpi <linux-acpi@vger.kernel.org>
Subject: Re: Input Brightness events on EeePc 1201HA
Date: Sun, 2 May 2010 14:31:19 +0200	[thread overview]
Message-ID: <q2k71cd59b01005020531n8f827e63qd03588fd980c3c9a@mail.gmail.com> (raw)
In-Reply-To: <1272643738.26706.63.camel@plop>

CCing linux-acpi and Zhang Rui.

>> - Does brightness react to keypress (up and/or down) in grub ? windows
>> ? linux wihout X ?
>
> It does not work in GRUB for an unknown reason but I have "good" news
>
> It works in Linux, without using video (which can not manage this
> machine), until psb driver is loaded and creates a backlight device
> using PWM!

Looking at the dsdt:

                        Method (STBR, 0, Serialized)
                        {
                            If (And (^^^GFX0.TCHE, 0x02))
                            {
                                ISMI (0x7A)
                                ^^^GFX0.AINT (One, PAR0)
                            }
                            Else
                            {
                                ISMI (0x78)
                            }
                        }

ISMI (0x78) is the working path, so when psb load, And (^^^GFX0.TCHE,
0x02) become true,  Maybe in this case the psb driver should do
something that it doesn't.

A quick workaround would be to send input events in eeepc-laptop if
GFX0.TCHE & 0x2, but does not sound pretty.

> Unfortunately I can't think of a solution for machines using psb except
> disabling backlight handling there.
>
> It would either conflict (2 backlights device, on in psb, the other in
> eeepc-laptop/wmi) or have keys not handled (as both would not handle
> them if they do not handle backlight)



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

       reply	other threads:[~2010-05-02 12:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1272383014.8403.12.camel@plop>
     [not found] ` <w2t71cd59b01004280220rbbff08cek497c98985e996748@mail.gmail.com>
     [not found]   ` <1272446724.12834.24.camel@plop>
     [not found]     ` <g2o71cd59b01004280508m99790717x9d9f10c71fd1145b@mail.gmail.com>
     [not found]       ` <1272457434.12834.29.camel@plop>
     [not found]         ` <q2z71cd59b01004280528scc775622lf85055f797cec79e@mail.gmail.com>
     [not found]           ` <1272461780.12834.93.camel@plop>
     [not found]             ` <1272462009.12834.95.camel@plop>
     [not found]               ` <t2g71cd59b01004292311sd797e259g6340d701bc52a93e@mail.gmail.com>
     [not found]                 ` <1272643738.26706.63.camel@plop>
2010-05-02 12:31                   ` Corentin Chary [this message]
2010-05-02 14:25                     ` Input Brightness events on EeePc 1201HA Matthew Garrett

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=q2k71cd59b01005020531n8f827e63qd03588fd980c3c9a@mail.gmail.com \
    --to=corentin.chary@gmail.com \
    --cc=acpi4asus-user@lists.sourceforge.net \
    --cc=linux-acpi@vger.kernel.org \
    --cc=pterjan@mandriva.com \
    --cc=rui.zhang@intel.com \
    /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).