1. 23 2月, 2010 1 次提交
    • R
      ACPI: Use GPE reference counting to support shared GPEs · 9630bdd9
      Rafael J. Wysocki 提交于
      ACPI GPEs may map to multiple devices.  The current GPE interface
      only provides a mechanism for enabling and disabling GPEs, making
      it difficult to change the state of GPEs at runtime without extensive
      cooperation between devices.
      
      Add an API to allow devices to indicate whether or not they want
      their device's GPE to be enabled for both runtime and wakeup events.
      
      Remove the old GPE type handling entirely, which gets rid of various
      quirks, like the implicit disabling with GPE type setting. This
      requires a small amount of rework in order to ensure that non-wake
      GPEs are enabled by default to preserve existing behaviour.
      
      Based on patches from Matthew Garrett <mjg@redhat.com>.
      Signed-off-by: NMatthew Garrett <mjg@redhat.com>
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      Signed-off-by: NJesse Barnes <jbarnes@virtuousgeek.org>
      9630bdd9
  2. 16 12月, 2009 1 次提交
  3. 13 10月, 2009 1 次提交
  4. 11 9月, 2009 1 次提交
  5. 29 8月, 2009 1 次提交
  6. 11 4月, 2009 6 次提交
  7. 05 4月, 2009 1 次提交
  8. 31 3月, 2009 1 次提交
    • A
      proc 2/2: remove struct proc_dir_entry::owner · 99b76233
      Alexey Dobriyan 提交于
      Setting ->owner as done currently (pde->owner = THIS_MODULE) is racy
      as correctly noted at bug #12454. Someone can lookup entry with NULL
      ->owner, thus not pinning enything, and release it later resulting
      in module refcount underflow.
      
      We can keep ->owner and supply it at registration time like ->proc_fops
      and ->data.
      
      But this leaves ->owner as easy-manipulative field (just one C assignment)
      and somebody will forget to unpin previous/pin current module when
      switching ->owner. ->proc_fops is declared as "const" which should give
      some thoughts.
      
      ->read_proc/->write_proc were just fixed to not require ->owner for
      protection.
      
      rmmod'ed directories will be empty and return "." and ".." -- no harm.
      And directories with tricky enough readdir and lookup shouldn't be modular.
      We definitely don't want such modular code.
      
      Removing ->owner will also make PDE smaller.
      
      So, let's nuke it.
      
      Kudos to Jeff Layton for reminding about this, let's say, oversight.
      
      http://bugzilla.kernel.org/show_bug.cgi?id=12454Signed-off-by: NAlexey Dobriyan <adobriyan@gmail.com>
      99b76233
  9. 12 11月, 2008 1 次提交
  10. 08 11月, 2008 1 次提交
  11. 25 10月, 2008 1 次提交
  12. 11 10月, 2008 2 次提交
  13. 29 4月, 2008 1 次提交
  14. 12 3月, 2008 1 次提交
  15. 26 10月, 2007 1 次提交
  16. 20 10月, 2007 1 次提交
  17. 24 8月, 2007 1 次提交
    • L
      ACPI: Schedule /proc/acpi/event for removal · 14e04fb3
      Len Brown 提交于
      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: NLen Brown <len.brown@intel.com>
      14e04fb3
  18. 24 7月, 2007 1 次提交
  19. 13 2月, 2007 3 次提交
    • L
      ACPI: delete extra #defines in /drivers/acpi/ drivers · 7cda93e0
      Len Brown 提交于
      Cosmetic only.
      
      Except in a single case, #define ACPI_*_DRIVER_NAME
      were invoked 0 or 1 times.
      Signed-off-by: NLen Brown <len.brown@intel.com>
      7cda93e0
    • L
      ACPI: fix acpi_driver.name usage · c2b6705b
      Len Brown 提交于
      It was erroneously used as a description rather than a name.
      
      ie. turn this:
      
      lenb@se7525gp2:/sys> ls bus/acpi/drivers
      ACPI AC Adapter Driver  ACPI Embedded Controller Driver  ACPI Power Resource Driver
      ACPI Battery Driver     ACPI Fan Driver                  ACPI Processor Driver
      ACPI Button Driver      ACPI PCI Interrupt Link Driver   ACPI Thermal Zone Driver
      ACPI container driver   ACPI PCI Root Bridge Driver      hpet
      
      into this:
      
      lenb@se7525gp2:~> ls /sys/bus/acpi/drivers
      ac  battery  button  container  ec  fan  hpet  pci_link  pci_root  power  processor  thermal
      Signed-off-by: NLen Brown <len.brown@intel.com>
      c2b6705b
    • L
      ACPI: clean up ACPI_MODULE_NAME() use · f52fd66d
      Len Brown 提交于
      cosmetic only
      
      Make "module name" actually match the file name.
      Invoke with ';' as leaving it off confuses Lindent and gcc doesn't care.
      Fix indentation where Lindent did get confused.
      Signed-off-by: NLen Brown <len.brown@intel.com>
      f52fd66d
  20. 01 2月, 2007 1 次提交
  21. 09 11月, 2006 1 次提交
    • D
      ACPI: button: register with input layer · c0968f0e
      Dmitry Torokhov 提交于
      In addition to signalling button/lid events through /proc/acpi/event,
      create separate input devices and report KEY_POWER, KEY_SLEEP and
      SW_LID through input layer.  Also remove unnecessary casts and variable
      initializations, clean up formatting.
      
      Sleep button may autorepeat but userspace will have to filter duplicate
      sleep requests anyway (and discard unprocessed events right after
      wakeup).
      
      Unlike /proc/acpi/event interface input device corresponding to LID
      switch reports true lid state instead of just a counter. SW_LID is
      active when lid is closed.
      
      The driver now depends on CONFIG_INPUT.
      Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      c0968f0e
  22. 14 10月, 2006 1 次提交
  23. 10 7月, 2006 1 次提交
  24. 30 6月, 2006 2 次提交
  25. 27 6月, 2006 3 次提交
  26. 05 8月, 2005 1 次提交
  27. 04 8月, 2005 1 次提交
  28. 12 7月, 2005 1 次提交
  29. 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