• Corentin Chary's avatar
    eeepc-wmi: serialize access to wmi method · 279f8f95
    Corentin Chary authored
    \AMW0.WMBC, which is the main method that we use,
    is not reentrant. When wireless hotpluging is enabled,
    toggling the status of the wireless device using WMBC will
    trigger a notification and the notification handler need to
    call WMBC again to get the new status of the device, this
    will trigger the following error:
    
    ACPI Error (dswload-0802): [_T_0] Namespace lookup failure, AE_ALREADY_EXISTS
    ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog (20100428/psloop-231)
    ACPI Error (psparse-0537): Method parse/execution failed [\AMW0.WMBC] (Node f7023b88), AE_ALREADY_EXISTS
    ACPI: Marking method WMBC as Serialized because of AE_ALREADY_EXISTS error
    
    Since there is currently no way to tell the acpi subsystem to mark
    a method as serialized, we do it in eeepc-wmi.
    
    Of course, we could let the first call fail, and then it would work,
    but it doesn't seems really clean, and it will make the first
    WMBC call return a random value.
    
    This patch was tested on EeePc 1000H with a RaLink RT2860
    wireless card using the rt2800pci driver. rt2860sta driver
    seems to deadlock when we remove the pci device...
    Signed-off-by: default avatarCorentin Chary <corentincj@iksaif.net>
    Signed-off-by: default avatarMatthew Garrett <mjg@redhat.com>
    279f8f95
eeepc-wmi.c 30 KB