From: Azael Avalos <coproscefalo@gmail.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-acpi@vger.kernel.org, dsilvers@simtec.co.uk,
toshiba_acpi@memebeam.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] toshiba-acpi: Support TOS1900-type devices
Date: Thu, 2 Apr 2009 10:13:23 +1700 [thread overview]
Message-ID: <74962ea30904011013v5ffa0620y1f1aefa2c84e1ce@mail.gmail.com> (raw)
In-Reply-To: <20090401170708.GA14167@srcf.ucam.org>
On Thu, Apr 2, 2009 at 10:07 AM, Matthew Garrett <mjg59@srcf.ucam.org> wrote:
> On Thu, Apr 02, 2009 at 10:03:05AM +1700, Azael Avalos wrote:
>> On Thu, Apr 2, 2009 at 9:53 AM, Matthew Garrett <mjg59@srcf.ucam.org> wrote:
>> > Yes, you shouldn't be reading directly from TOHK at any point. It seems
>> > to be a purely internal variable - I'm fairly sure that the INFO method
>> > is the only one that should be called on event generation.
>>
>> Well, on the patches sent to the omnibook module I was polling TOHK directly,
>> it is until now that I realized that I can poll the events via INFO
>> method, that is,
>> if I enable TECF first via method \\_SB.PCI0.LPCB.EC0.NTFY
>
> Mm. None of the TOS1900 DSDTs I have here have TECF or NTFY methods, so
> again that doesn't sound like the right way of driving them. Does the
> ENAB method not do this?
At least not in my model, the ENAB method is empty, heres a snippet of the DSDT:
Method (ENAB, 0, NotSerialized)
{
}
Method (INFO, 0, NotSerialized)
{
If (TECF)
{
Store (Zero, TECF)
Store (^^PCI0.LPCB.EC0.TOHK, Local0)
Store (Zero, ^^PCI0.LPCB.EC0.TOHK)
}
Else
{
Store (Zero, Local0)
}
Return (Local0)
}
And above scope _SB you can find
Method (NTFY, 0, NotSerialized)
{
Store (One, ^^^^VALZ.TECF)
Notify (VALZ, 0x80)
Return (0xAA)
}
Saludos
Azael
--
-- El mundo apesta y vosotros apestais tambien --
next prev parent reply other threads:[~2009-04-01 17:13 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 21:45 [PATCH 1/2] toshiba-acpi: Add support for hotkey notifications Matthew Garrett
2009-03-31 21:47 ` [PATCH 2/2] toshiba-acpi: Support TOS1900-type devices Matthew Garrett
2009-03-31 22:06 ` Azael Avalos
2009-03-31 22:11 ` Matthew Garrett
2009-03-31 22:19 ` Azael Avalos
2009-03-31 23:02 ` Matthew Garrett
2009-04-01 16:50 ` Azael Avalos
2009-04-01 16:53 ` Matthew Garrett
2009-04-01 17:03 ` Azael Avalos
2009-04-01 17:07 ` Matthew Garrett
2009-04-01 17:13 ` Azael Avalos [this message]
2009-06-02 14:03 ` Matthew Garrett
2009-06-09 16:42 ` Azael Avalos
2009-06-09 16:45 ` Matthew Garrett
2009-06-10 0:18 ` Azael Avalos
2009-06-10 0:22 ` Matthew Garrett
2009-06-10 0:29 ` Azael Avalos
2009-06-18 0:35 ` Azael Avalos
2009-04-08 5:44 ` [PATCH 1/2] toshiba-acpi: Add support for hotkey notifications Len Brown
2009-04-11 19:50 ` Frans Pop
2009-04-13 14:50 ` Matthew Garrett
2009-04-13 19:28 ` Frans Pop
2009-04-13 19:43 ` Matthew Garrett
2009-04-13 20:38 ` Frans Pop
2009-04-13 21:18 ` Matthew Garrett
2009-04-13 21:26 ` Frans Pop
2009-04-13 21:31 ` Matthew Garrett
2009-04-18 4:01 ` Len Brown
2009-04-18 5:47 ` Andrey Borzenkov
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=74962ea30904011013v5ffa0620y1f1aefa2c84e1ce@mail.gmail.com \
--to=coproscefalo@gmail.com \
--cc=dsilvers@simtec.co.uk \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=toshiba_acpi@memebeam.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®