public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Janosch Machowinski <scotch-cGBD8117FJM@public.gmane.org>
To: linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Strange interpreter behaviour
Date: Sat, 07 Jan 2006 18:18:22 +0100	[thread overview]
Message-ID: <43BFF7DE.1000909@tzi.de> (raw)

Hey,
I got an ASUS M6, which contains some strange _CST related ASL code.
In the _CST method there is a check, if \_SB.INV7 is set :
                 If (\_SB.INV7)
                 {
                     Return (NOC3)
                 }
This seems to always return true. There is also the method \_GPE:_L17 
which just inverts \_SB.INV7 and sends a signal to refetch the CST Object :
           Method (_L17, 0, NotSerialized)
         {
             If (\_SB.INV7)
             {
                 Store (0x00, \_SB.INV7)
             }
             Else
             {
                 Store (0x01, \_SB.INV7)
             }

             Notify (\_PR.CPU1, 0x81)
         }

Now I called the _L17 method manually :
echo "0:\\_GPE:_L17:\\_GPE:_L17:10001:1" > /proc/acpi/hotkey/poll_config
echo "10001:0:1:0" > /proc/acpi/hotkey/action

What I noticed is that every time I call the action, my C-State usage 
counter gets reset to zero. From that behaviour I would follow, that the 
L17 method was executed and the CST Object was refetched. So there seems 
to be an error in setting the \_SB.INV7 bit/register/whatever. (I assume 
0 is false an 1 is true in ASL if-clauses ?)
Greets
    Janosch
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2006-01-07 17:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-07 17:18 Janosch Machowinski [this message]
     [not found] ` <43BFF7DE.1000909-cGBD8117FJM@public.gmane.org>
2006-01-16 17:19   ` Strange interpreter behaviour Bruno Ducrot
     [not found]     ` <20060116171932.GF25115-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2006-01-16 21:27       ` Janosch Machowinski
     [not found]         ` <43CC0FC0.9090806-cGBD8117FJM@public.gmane.org>
2006-01-17 10:30           ` Bruno Ducrot
     [not found]             ` <20060117103043.GA2154-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2006-01-17 12:41               ` Janosch Machowinski
     [not found]                 ` <43CCE603.3010600-cGBD8117FJM@public.gmane.org>
2006-01-17 13:24                   ` Bruno Ducrot
     [not found]                     ` <20060117132435.GB2154-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2006-01-17 14:28                       ` Janosch Machowinski
     [not found]                         ` <43CCFF1C.4000309-cGBD8117FJM@public.gmane.org>
2006-01-17 15:47                           ` Bruno Ducrot
2006-01-20 15:27                             ` Janosch Machowinski
2006-01-20 19:32                               ` Bruno Ducrot
2006-01-21 18:55                                 ` Janosch Machowinski
  -- strict thread matches above, loose matches on Subject: below --
2006-01-09  5:58 Yu, Luming
2006-01-09  7:16 ` Janosch Machowinski
2006-01-16  2:27 Yu, Luming
2006-01-16 19:22 ` Janosch Machowinski

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=43BFF7DE.1000909@tzi.de \
    --to=scotch-cgbd8117fjm@public.gmane.org \
    --cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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