Hello again,
> Hum .. maybe, the best way to know would be to dump it in various
> hardware states.
I've found some time yesterday to give it a try and first had a look at the EC
register space. I've actually managed to find a register which reflects
the state of the hotkeys - it's register 0xE6. I could probably now just
write a driver to poll this at 5 or 10 Hz and be done with it, but that
solution seems a little hackish. The EC register space is probably still
necessary for accelerometer access (I'll try to set the X/Y/ZALM bits to
1 later and see what happens), but I think for hotkeys, an event-based
solution would be better.
> >> > ERQ0 (present in BUF1) is compared to Arg2 (BY09) == 0x1
> >> > if true, it will store some values and call notify
> > So this would then trigger the WMI event in the driver, right?
> > I'd assume that EVID is the EVent ID - would make sense, since somewhere
> > in the embedded controller code, there's this snippet:
> >
> > Method (_QEF, 0, NotSerialized)
> > {
> > Store (0xEF, P80H)
> > \_SB.WMI2.CMD2 (0x2D, 0x01, 0x01)
> > }
> >
> > Method (_QF1, 0, NotSerialized)
> > {
> > Store (0xF1, P80H)
> > \_SB.WMI2.CMD2 (0x2C, 0x01, 0x01)
> > }
> >
> > AFAICT the problem might be that ERQ0 is never initialized.. so it's
> > probably zero from the start and the first code branch in CMD0 will
> > never be called.
>
> ERQ0 is initialized here (with 0x00):
> Name (BUF1, Buffer (0x40)
AFAICT it's never accessed anywhere else, right? So it's going to sit
there at 0x00 and the Notify (\_SB.WMI2, 0x80) code will never be
called.
I still have a bit of confusion going on with respect to the difference
between WMI notifications and EC notifications. The Notify() call above
would trigger the WMI notification, but in what way would the kernel be
notified about something like the following:
Method (_Q8F, 0, NotSerialized)
{
Store ("_Q8F : Hot Key Event", Debug)
Store (0x8F, P80H)
DSGO ()
DSSV ()
Store ("_Q8F : Hot Key Event Finished", Debug)
}
IIRC all _Qxx methods are also some kind of notification system, right?
Thanks, Yours, Florian
--
0666 - Filemode of the Beast
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
