public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Pohl <sebastianp@uni-koblenz.de>
To: Zhang Rui <rui.zhang@intel.com>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	Mattia Dongili <malattia@linux.it>
Subject: Re: acpi on sony vaio vgn-sz61mn
Date: Tue, 23 Jun 2009 11:14:18 +0200	[thread overview]
Message-ID: <4A409CEA.6040900@uni-koblenz.de> (raw)
In-Reply-To: <1245746886.15520.98.camel@rzhang-dt>

Zhang Rui wrote:
> On Tue, 2009-06-23 at 16:45 +0800, Sebastian Pohl wrote:
>   
>> Zhang Rui wrote:
>>     
>>> On Tue, 2009-06-23 at 16:30 +0800, Sebastian Pohl wrote:
>>>   
>>>       
>>>> Hi!
>>>>
>>>> Zhang Rui wrote:
>>>>     
>>>>         
>>>>> On Wed, 2009-06-17 at 21:43 +0800, Sebastian Pohl wrote:
>>>>>   
>>>>>       
>>>>>           
>>>>>> Hello everyone!
>>>>>>
>>>>>> Thank you to everyone working on the sony stuff! It made my laptop a 
>>>>>> much more valuable companion!
>>>>>>
>>>>>> But there are still some flaws that are left. I am writing to get an 
>>>>>> advise what to do with them. 
>>>>>>     
>>>>>>         
>>>>>>             
>>>>>   
>>>>>       
>>>>>           
>>>>>> Ok, the problems are:
>>>>>>
>>>>>> - The special button s2 generates the same acpi event as the stamina switch
>>>>>> - The lidswitch does not generate any acpi events
>>>>>> - The Power does not generate any acpi events
>>>>>>
>>>>>>     
>>>>>>         
>>>>>>             
>>>>> please kill acpid, and run "cat /proc/acpi/event", what do you get when
>>>>> pressing each of the three buttons?
>>>>>   
>>>>>       
>>>>>           
>>>> Both, the s2 Button and the stamina switch generate the following
>>>>
>>>>     
>>>>         
>>> so Q1 and Q2 are sony platform driver problems.
>>> what do you get when pressing the power button?
>>>
>>> thanks,
>>> rui
>>>   
>>>       
>> When presing the power button nothing happens. No acpi output, no 
>> interrupts, nothing. Same with the lid-switch.
>>
>>     
>
> even no ACPI interrupts?
> please attach the output of grep . /sys/firmware/acpi/interrupts/*
> both before and after pressing these buttons for a couple of times.
>
> thanks,
> rui
>
>   
Hi,

this is before:

/sys/firmware/acpi/interrupts/error:       0
/sys/firmware/acpi/interrupts/ff_gbl_lock:       0    enabled
/sys/firmware/acpi/interrupts/ff_pmtimer:       0    invalid
/sys/firmware/acpi/interrupts/ff_pwr_btn:       0    invalid
/sys/firmware/acpi/interrupts/ff_rt_clk:       0    disabled
/sys/firmware/acpi/interrupts/ff_slp_btn:       0    invalid
/sys/firmware/acpi/interrupts/gpe00:       0    invalid
/sys/firmware/acpi/interrupts/gpe01:       0    enabled
/sys/firmware/acpi/interrupts/gpe02:       0    enabled
/sys/firmware/acpi/interrupts/gpe03:       0    disabled
/sys/firmware/acpi/interrupts/gpe04:       0    disabled
/sys/firmware/acpi/interrupts/gpe05:       0    disabled
/sys/firmware/acpi/interrupts/gpe06:       0    enabled
/sys/firmware/acpi/interrupts/gpe07:       0    enabled
/sys/firmware/acpi/interrupts/gpe08:       0    invalid
/sys/firmware/acpi/interrupts/gpe09:       0    disabled
/sys/firmware/acpi/interrupts/gpe0A:       0    invalid
/sys/firmware/acpi/interrupts/gpe0B:       0    enabled
/sys/firmware/acpi/interrupts/gpe0C:       0    disabled
/sys/firmware/acpi/interrupts/gpe0D:       0    disabled
/sys/firmware/acpi/interrupts/gpe0E:       0    disabled
/sys/firmware/acpi/interrupts/gpe0F:       0    invalid
/sys/firmware/acpi/interrupts/gpe10:       0    invalid
/sys/firmware/acpi/interrupts/gpe11:       0    invalid
/sys/firmware/acpi/interrupts/gpe12:       0    invalid
/sys/firmware/acpi/interrupts/gpe13:       0    invalid
/sys/firmware/acpi/interrupts/gpe14:       0    invalid
/sys/firmware/acpi/interrupts/gpe15:       0    invalid
/sys/firmware/acpi/interrupts/gpe16:       0    invalid
/sys/firmware/acpi/interrupts/gpe17:       0    enabled
/sys/firmware/acpi/interrupts/gpe18:       0    enabled
/sys/firmware/acpi/interrupts/gpe19:       0    invalid
/sys/firmware/acpi/interrupts/gpe1A:       0    invalid
/sys/firmware/acpi/interrupts/gpe1B:       0    invalid
/sys/firmware/acpi/interrupts/gpe1C:       0    invalid
/sys/firmware/acpi/interrupts/gpe1D:       0    invalid
/sys/firmware/acpi/interrupts/gpe1E:       0    invalid
/sys/firmware/acpi/interrupts/gpe1F:       0    invalid
/sys/firmware/acpi/interrupts/gpe_all:       0
/sys/firmware/acpi/interrupts/sci:       0


and after 10 times pressing the power button and opening/closing the lid:

/sys/firmware/acpi/interrupts/error:       0
/sys/firmware/acpi/interrupts/ff_gbl_lock:       0    enabled
/sys/firmware/acpi/interrupts/ff_pmtimer:       0    invalid
/sys/firmware/acpi/interrupts/ff_pwr_btn:       0    invalid
/sys/firmware/acpi/interrupts/ff_rt_clk:       0    disabled
/sys/firmware/acpi/interrupts/ff_slp_btn:       0    invalid
/sys/firmware/acpi/interrupts/gpe00:       0    invalid
/sys/firmware/acpi/interrupts/gpe01:       0    enabled
/sys/firmware/acpi/interrupts/gpe02:       0    enabled
/sys/firmware/acpi/interrupts/gpe03:       0    disabled
/sys/firmware/acpi/interrupts/gpe04:       0    disabled
/sys/firmware/acpi/interrupts/gpe05:       0    disabled
/sys/firmware/acpi/interrupts/gpe06:       0    enabled
/sys/firmware/acpi/interrupts/gpe07:       0    enabled
/sys/firmware/acpi/interrupts/gpe08:       0    invalid
/sys/firmware/acpi/interrupts/gpe09:       0    disabled
/sys/firmware/acpi/interrupts/gpe0A:       0    invalid
/sys/firmware/acpi/interrupts/gpe0B:       0    enabled
/sys/firmware/acpi/interrupts/gpe0C:       0    disabled
/sys/firmware/acpi/interrupts/gpe0D:       0    disabled
/sys/firmware/acpi/interrupts/gpe0E:       0    disabled
/sys/firmware/acpi/interrupts/gpe0F:       0    invalid
/sys/firmware/acpi/interrupts/gpe10:       0    invalid
/sys/firmware/acpi/interrupts/gpe11:       0    invalid
/sys/firmware/acpi/interrupts/gpe12:       0    invalid
/sys/firmware/acpi/interrupts/gpe13:       0    invalid
/sys/firmware/acpi/interrupts/gpe14:       0    invalid
/sys/firmware/acpi/interrupts/gpe15:       0    invalid
/sys/firmware/acpi/interrupts/gpe16:       0    invalid
/sys/firmware/acpi/interrupts/gpe17:       0    enabled
/sys/firmware/acpi/interrupts/gpe18:       0    enabled
/sys/firmware/acpi/interrupts/gpe19:       0    invalid
/sys/firmware/acpi/interrupts/gpe1A:       0    invalid
/sys/firmware/acpi/interrupts/gpe1B:       0    invalid
/sys/firmware/acpi/interrupts/gpe1C:       0    invalid
/sys/firmware/acpi/interrupts/gpe1D:       0    invalid
/sys/firmware/acpi/interrupts/gpe1E:       0    invalid
/sys/firmware/acpi/interrupts/gpe1F:       0    invalid
/sys/firmware/acpi/interrupts/gpe_all:       0
/sys/firmware/acpi/interrupts/sci:       0

I cant see any difference...

regards

     sebastian
>> regards
>>
>>     sebastian
>>
>>     
>>>> sony/hotkey SPIC 00000001 00000021
>>>>     
>>>>         
>>>>> run "cat /proc/interrupts" both before and after pressing these buttons,
>>>>> does the number of ACPI or sony interrupts increase?
>>>>> If ACPI interrupts increases, please run
>>>>> "grep . /sys/firmware/acpi/interrupts/*" and tell us which GPE/Fixed
>>>>> event is fired.
>>>>>
>>>>>   
>>>>>       
>>>>>           
>>>> Only the stamina switch and the s2 button increase any interrupts but 
>>>> only sony interrupts are generated.
>>>>     
>>>>         
>>>>> 
>>>>>   
>>>>>       
>>>>>           
>>>>>> Should i post them to bugtrackter or 
>>>>>> something else?
>>>>>>
>>>>>>     
>>>>>>         
>>>>>>             
>>>>> please file a new bug report at
>>>>> http://bugzilla.kernel.org/enter_bug.cgi?product=ACPI
>>>>> and attach all the request info there.
>>>>> please also attach the acpidump output.
>>>>>
>>>>> thanks,
>>>>> rui
>>>>>
>>>>>   
>>>>>       
>>>>>           
>>>> thank you!
>>>>
>>>> regards
>>>>
>>>>      sebastian
>>>>     
>>>>         
>>>   
>>>       
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>   

--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-06-23  9:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17 13:43 acpi on sony vaio vgn-sz61mn Sebastian Pohl
2009-06-18  0:58 ` Zhang Rui
2009-06-23  8:30   ` Sebastian Pohl
2009-06-23  8:44     ` Zhang Rui
2009-06-23  8:45       ` Sebastian Pohl
2009-06-23  8:48         ` Zhang Rui
2009-06-23  9:14           ` Sebastian Pohl [this message]
2009-06-23  9:23             ` Zhang, Rui
2009-06-23  9:33               ` Sebastian Pohl
2009-06-24  0:58                 ` Zhang Rui
2009-06-24  9:13                   ` Sebastian Pohl
2009-06-25  1:31                     ` Zhang Rui
2009-06-25  8:31                       ` Sebastian Pohl
2009-06-18  2:16 ` Mattia Dongili

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=4A409CEA.6040900@uni-koblenz.de \
    --to=sebastianp@uni-koblenz.de \
    --cc=linux-acpi@vger.kernel.org \
    --cc=malattia@linux.it \
    --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