Re: [PATCH 2/4] toshiba_acpi: Support alternate hotkey interfaces

[Seth Forshee]

On Sat, Dec 17, 2011 at 04:32:14AM -0700, Azael Avalos wrote:
> 2011/12/17 Thomas Renninger <trenn@xxxxxxx>:
> > On Thursday 15 December 2011 19:06:09 Seth Forshee wrote:
> > ...
> >> +static bool toshiba_acpi_i8042_filter(unsigned char data, unsigned char str,
> >> + Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â struct serio *port)
> >> +{
> >> + Â Â if (str & 0x20)
> >> + Â Â Â Â Â Â return false;
> >> +
> >> + Â Â if (unlikely(data == 0xe0))
> >> + Â Â Â Â Â Â return false;
> >> +
> >> + Â Â if ((data & 0x7f) == TOS1900_FN_SCAN) {
> >> + Â Â Â Â Â Â schedule_work(&toshiba_acpi->hotkey_work);
> >> + Â Â Â Â Â Â return true;
> >> + Â Â }
> > What have you tried to check whether some other kind of ACPI event
> > is happening?
> > Do any acpi/SCI interrupts happen?:
> > watch -n1 "cat /proc/interrupts |grep acpi"
> 
> I already did this, no events whatsoever, I was using a Satellite X205
> at the time

I've done similar checks on the NB505, no events.

> >
> > Could it by chance be an EC or other device GPE/SCI?
> >
> 
> Seth mentioned me something about this, but w/o proper docs from
> Toshiba, we are blindly shooting.
> 
> Seth?

In the DSDTs I've inspected there is an EC query method that looks like
it handles events for the hotkeys, but I've never been able to find
anything that will cause the GPE to trigger when the hotkeys are
pressed.

Interestingly, I also saw that the Windows hotkey driver for the NB505
logs some messages that indicate it's also filtering Fn key presses, and
I also found that the binary contains the NTFY string. That's not proof
of anything, but it does suggest that the Windows driver might be doing
something similar to support hotkeys. Which makes me wonder if the GPE
works at all.

> 
> >> +
> >> + Â Â return false;
> >> +}
> >> +
> >> +static void toshiba_acpi_hotkey_work(struct work_struct *work)
> >> +{
> >> + Â Â acpi_handle ec_handle = ec_get_handle();
> >> + Â Â acpi_status status;
> >> +
> >> + Â Â if (!ec_handle)
> >> + Â Â Â Â Â Â return;
> >> +
> >> + Â Â status = acpi_evaluate_object(ec_handle, "NTFY", NULL, NULL);
> >> + Â Â if (ACPI_FAILURE(status))
> >> + Â Â Â Â Â Â pr_err("ACPI NTFY method execution failed\n");
> > Why is calling NTFY needed?
> 
> The NTFY method triggers a 0x80 notify event on TOS1900 device,
> and thus being trapped by toshiba_acpi_notify, here are the methods
> 
> Method (NTFY, 0, NotSerialized)
> {
>   Store (One, ^^^^VALZ.TECF)
>   Notify (VALZ, 0x80)
>   Return (0xAA)
> }
> 
> And then
> 
> 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)
> }

The NB505 is very similar. We might be able to get by without NTFY if
all it was doing was providing the notification, but as you can see it
also sets a flag that's needed to read the hotkey event with the INFO
method.

> >
> > ...
> >
> >> +static int toshiba_acpi_suspend(struct acpi_device *acpi_dev,
> >> + Â Â Â Â Â Â Â Â Â Â Â Â Â Â pm_message_t state)
> >> +{
> >> + Â Â struct toshiba_acpi_dev *dev = acpi_driver_data(acpi_dev);
> >> + Â Â u32 result;
> >> +
> >> + Â Â if (dev->hotkey_dev)
> >> + Â Â Â Â Â Â hci_write1(dev, HCI_HOTKEY_EVENT, HCI_HOTKEY_DISABLE, &result);
> >> +
> >> + Â Â return 0;
> >> +}
> >> +
> >> +static int toshiba_acpi_resume(struct acpi_device *acpi_dev)
> >> +{
> >> + Â Â struct toshiba_acpi_dev *dev = acpi_driver_data(acpi_dev);
> >> + Â Â u32 result;
> >> +
> >> + Â Â if (dev->hotkey_dev)
> >> + Â Â Â Â Â Â hci_write1(dev, HCI_HOTKEY_EVENT, HCI_HOTKEY_ENABLE, &result);
> >> +
> >> + Â Â return 0;
> >> +}
> > What are the suspend/resume funcs for?
> > What bad things happen without them?
> 
> Some models (NB500 among others) stop sending hotkey events
> when resumed, and even activating the hotkeys again don't work,
> the suspend/resume functions do the trick ;)

The NB505 (which is what I've been testing with) requires this as well.

Seth

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/