25 Aug, 2007

2 commits


24 Aug, 2007

5 commits

  • The asus laptop driver conditionnaly registers leds in asus_led_register()
    depending on their availability, but unconditionnaly unregisters them all at
    exit time or when the module fails to load. Unregistering not registered leds
    result in the following Oops. So we should check before unregistering.

    [] do_page_fault+0x511/0x5e9
    [] error_code+0x6a/0x70
    [] device_unregister+0x26/0x32
    [] led_classdev_unregister+0x58/0x94 [led_class]
    [] asus_led_exit+0x17/0x41 [asus_laptop]
    [] asus_laptop_exit+0xd/0x3f [asus_laptop]
    [] sys_delete_module+0x17b/0x1a2
    [] sysenter_past_esp+0x6b/0xa1

    EIP: [] device_del+0xb/0x23a SS:ESP 0068:f594ef0c

    Signed-off-by: Guillaume Chazarain
    Signed-off-by: Len Brown

    Guillaume Chazarain
     
  • sonypi_compat uses a kfifo that needs to be present before _SRS is
    called to be able to cope with the IRQs triggered when setting
    resources.

    Signed-off-by: Mattia Dongili
    Signed-off-by: Len Brown

    Mattia Dongili
     
  • Signed-off-by: Mattia Dongili
    Signed-off-by: Len Brown

    Mattia Dongili
     
  • Schedule /proc/acpi/event for removal in 6 months.

    Re-name acpi_bus_generate_event() to acpi_bus_generate_proc_event()
    to make sure there is no confusion that it is for /proc/acpi/event only.

    Add CONFIG_ACPI_PROC_EVENT to allow removal of /proc/acpi/event.
    There is no functional change if CONFIG_ACPI_PROC_EVENT=y

    Signed-off-by: Len Brown

    Len Brown
     
  • The previous events patch added a netlink event for every
    user of the legacy /proc/acpi/event interface.

    However, some users of /proc/acpi/event are really input events,
    and they already report their events via the input layer.

    Introduce a new interface, acpi_bus_generate_netlink_event(),
    which is explicitly called by devices that want to repoprt
    events via netlink. This allows the input-like events
    to opt-out of generating netlink events. In summary:

    events that are sent via netlink:
    ac/battery/sbs
    thermal
    processor
    thinkpad_acpi dock/bay

    events that are sent via input layer:
    button
    video hotkey
    thinkpad_acpi hotkey
    asus_acpi/asus-laptop hotkey
    sonypi/sonylaptop

    Signed-off-by: Zhang Rui
    Signed-off-by: Len Brown

    Zhang Rui
     

19 Aug, 2007

1 commit


12 Aug, 2007

1 commit


08 Aug, 2007

1 commit

  • The current kconfig help text was misleading users. Also, the default for
    an input-layer-optimized support caused way too many problems without
    up-to-date userspace in place.

    So, rework the help text, and change the default to N. Note that
    distributions are supposed to enable this option as soon as they update HAL
    to a version that handles the thinkpad-acpi new input layer interface.

    Signed-off-by: Henrique de Moraes Holschuh
    Cc: Michael S. Tsirkin
    Cc: Hugh Dickins
    Signed-off-by: Len Brown

    Henrique de Moraes Holschuh
     

04 Aug, 2007

3 commits


25 Jul, 2007

1 commit


24 Jul, 2007

2 commits

  • modpost is going to use these to create e.g. acpi:ACPI0001
    in modules.alias.

    Signed-off-by: Thomas Renninger
    Signed-off-by: Len Brown

    Thomas Renninger
     
  • > Subject : drivers/misc/asus-laptop.c:*: error: 'struct led_classdev' has no member named 'class_dev'
    > References : http://lkml.org/lkml/2007/7/22/299
    > Submitter : Gabriel C

    Fallout from f8a7c6fe14f556ca8eeddce258cb21392d0c3a2f. However, looking
    at it shows that checks done in ASUS_LED_UNREGISTER() can't trigger
    at all (we never get to asus_led_exit() if registration fails) and
    if that registration fails, we actually leak stuff. IOW, it's worse
    than just replacing class_dev with dev in there - the tests themselves
    had been papering over the lousy cleanup logics.

    Signed-off-by: Al Viro
    Signed-off-by: Len Brown

    Al Viro
     

22 Jul, 2007

24 commits