1. 06 11月, 2012 1 次提交
  2. 23 2月, 2010 1 次提交
    • R
      PCI / ACPI / PM: Platform support for PCI PME wake-up · b67ea761
      Rafael J. Wysocki 提交于
      Although the majority of PCI devices can generate PMEs that in
      principle may be used to wake up devices suspended at run time,
      platform support is generally necessary to convert PMEs into wake-up
      events that can be delivered to the kernel.  If ACPI is used for this
      purpose, PME signals generated by a PCI device will trigger the ACPI
      GPE associated with the device to generate an ACPI wake-up event that
      we can set up a handler for, provided that everything is configured
      correctly.
      
      Unfortunately, the subset of PCI devices that have GPEs associated
      with them is quite limited.  The devices without dedicated GPEs have
      to rely on the GPEs associated with other devices (in the majority of
      cases their upstream bridges and, possibly, the root bridge) to
      generate ACPI wake-up events in response to PME signals from them.
      
      Add ACPI platform support for PCI PME wake-up:
      o Add a framework making is possible to use ACPI system notify
        handlers for run-time PM.
      o Add new PCI platform callback ->run_wake() to struct
        pci_platform_pm_ops allowing us to enable/disable the platform to
        generate wake-up events for given device.  Implemet this callback
        for the ACPI platform.
      o Define ACPI wake-up handlers for PCI devices and PCI root buses and
        make the PCI-ACPI binding code register wake-up notifiers for all
        PCI devices present in the ACPI tables.
      o Add function pci_dev_run_wake() which can be used by PCI drivers to
        check if given device is capable of generating wake-up events at
        run time.
      
      Developed in cooperation with Matthew Garrett <mjg@redhat.com>.
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      Signed-off-by: NJesse Barnes <jbarnes@virtuousgeek.org>
      b67ea761
  3. 18 6月, 2009 7 次提交
  4. 28 5月, 2009 1 次提交
    • K
      PCI/ACPI: fix wrong ref count handling in acpi_pci_bind() · dacd2549
      Kenji Kaneshige 提交于
      The 'dev' field of struct acpi_pci_data is having a pointer to struct
      pci_dev without incrementing the reference counter. Because of this, I
      got the following kernel oops when I was doing some pci hotplug
      operations. This patch fixes this bug by replacing wrong hand-made
      pci_find_slot() with pci_get_slot() in acpi_pci_bind().
      
       BUG: unable to handle kernel NULL pointer dereference at 00000000000000e8
       IP: [<ffffffff803f0e9b>] acpi_pci_unbind+0xb1/0xdd
      
       Call Trace:
        [<ffffffff803ecee4>] acpi_bus_remove+0x54/0x68
        [<ffffffff803ecf6d>] acpi_bus_trim+0x75/0xe3
        [<ffffffffa0345ddd>] acpiphp_disable_slot+0x16d/0x1e0 [acpiphp]
        [<ffffffffa03441f0>] disable_slot+0x20/0x60 [acpiphp]
        [<ffffffff803cfc18>] power_write_file+0xc8/0x110
        [<ffffffff803c6a54>] pci_slot_attr_store+0x24/0x30
        [<ffffffff803469ce>] sysfs_write_file+0xce/0x140
        [<ffffffff802e94e7>] vfs_write+0xc7/0x170
        [<ffffffff802e9aa0>] sys_write+0x50/0x90
        [<ffffffff8020bd6b>] system_call_fastpath+0x16/0x1b
      Signed-off-by: NKenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
      Reviewed-by: NBjorn Helgaas <bjorn.helgaas@hp.com>
      Reviewed-by: NAlex Chiang <achiang@hp.com>
      Tested-by: NAlex Chiang <achiang@hp.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      dacd2549
  5. 31 12月, 2008 2 次提交
  6. 07 2月, 2008 1 次提交
    • A
      ACPI: misc cleanups · e5685b9d
      Adrian Bunk 提交于
          This patch contains the following possible cleanups:
          - make the following needlessly global code static:
            - drivers/acpi/bay.c:dev_attr_eject
            - drivers/acpi/bay.c:dev_attr_present
            - drivers/acpi/dock.c:dev_attr_docked
            - drivers/acpi/dock.c:dev_attr_flags
            - drivers/acpi/dock.c:dev_attr_uid
            - drivers/acpi/dock.c:dev_attr_undock
            - drivers/acpi/pci_bind.c:acpi_pci_unbind()
            - drivers/acpi/pci_link.c:acpi_link_lock
            - drivers/acpi/sbs.c:acpi_sbs_callback()
            - drivers/acpi/sbshc.c:acpi_smbus_transaction()
            - drivers/acpi/sleep/main.c:acpi_sleep_prepare()
          - #if 0 the following unused global functions:
            - drivers/acpi/numa.c:acpi_unmap_pxm_to_node()
          - remove the following unused EXPORT_SYMBOL's:
            - acpi_register_gsi
            - acpi_unregister_gsi
            - acpi_strict
            - acpi_bus_receive_event
            - register_acpi_bus_type
            - unregister_acpi_bus_type
            - acpi_os_printf
            - acpi_os_sleep
            - acpi_os_stall
            - acpi_os_read_pci_configuration
            - acpi_os_create_semaphore
            - acpi_os_delete_semaphore
            - acpi_os_wait_semaphore
            - acpi_os_signal_semaphore
            - acpi_os_signal
            - acpi_pci_irq_enable
            - acpi_get_pxm
      Signed-off-by: NAdrian Bunk <bunk@kernel.org>
      Acked-by: NAlexey Starikovskiy <astarikovskiy@suse.de>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      e5685b9d
  7. 21 11月, 2007 1 次提交
    • G
      ACPI: acpiphp: Remove dmesg spam on device remove · 6ce7641b
      Gary Hade 提交于
      In cases where acpi_pci_bind() does not
      attach device data, acpi_pci_unbind()
      complains via an ACPI exception about the missing data when
      the device is removed.  For example, acpi_pci_bind() does not
      attach data for non-existent device functions so when the device
      is removed using the ACPI PCI hotplug driver 'acpiphp' an ACPI
      exception is logged for every non-existent function.  This patch
      avoids the confusing log messages by removing the unnecessary
      ACPI exception.
      Signed-off-by: NGary Hade <garyhade@us.ibm.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      6ce7641b
  8. 13 2月, 2007 1 次提交
  9. 21 12月, 2006 2 次提交
  10. 16 12月, 2006 2 次提交
  11. 14 10月, 2006 1 次提交
  12. 27 6月, 2006 3 次提交
  13. 03 9月, 2005 1 次提交
  14. 05 8月, 2005 1 次提交
  15. 28 6月, 2005 2 次提交
  16. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4