1. 10 12月, 2009 2 次提交
    • A
      asus-acpi: Remove uneccesary acpi_disabled checks · 5a4a9f6f
      Alan Jenkins 提交于
      acpi_bus_register_driver() already checks acpi_disabled, so acpi bus
      drivers don't need to.
      Signed-off-by: NAlan Jenkins <alan-jenkins@tuffmail.co.uk>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      5a4a9f6f
    • A
      asus-acpi: Remove redundant NULL checks · 2d5db0be
      Alan Jenkins 提交于
      The acpi device callbacks add, start, remove, suspend and resume can
      never be called with a NULL acpi_device. Each callsite in acpi/scan.c
      has to dereference the device in order to get the ops structure, e.g.
      
          struct acpi_device *acpi_dev = to_acpi_device(dev);
          struct acpi_driver *acpi_drv = acpi_dev->driver;
      
          if (acpi_drv && acpi_drv->ops.suspend)
              return acpi_drv->ops.suspend(acpi_dev, state);
      
      Remove all checks for acpi_dev == NULL within these callbacks.
      
      Also remove the checks for acpi_driver_data(acpi_dev) == NULL. None of
      these checks could fail unless the driver does something strange
      (which none of them do), the acpi core did something terribly wrong,
      or we have a memory corruption issue. If this does happen then it's
      best to dereference the pointer and crash noisily.
      Signed-off-by: NAlan Jenkins <alan-jenkins@tuffmail.co.uk>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      2d5db0be
  2. 18 6月, 2009 1 次提交
    • B
      ACPI: asus-acpi: use .notify method instead of installing handler directly · 352fa202
      Bjorn Helgaas 提交于
      This patch adds a .notify() method.  The presence of .notify() causes
      Linux/ACPI to manage event handlers and notify handlers on our behalf,
      so we don't have to install and remove them ourselves.
      
      This driver relies on seeing system notify events, not device-specific
      ones (because it used ACPI_SYSTEM_NOTIFY).  We use the
      ACPI_DRIVER_ALL_NOTIFY_EVENTS driver flag to request all events, then
      just ignore any device events we get.
      Signed-off-by: NBjorn Helgaas <bjorn.helgaas@hp.com>
      CC: Corentin Chary <corentincj@iksaif.net>
      CC: Karol Kozimor <sziwan@users.sourceforge.net>
      CC: acpi4asus-user@lists.sourceforge.net
      Signed-off-by: NLen Brown <len.brown@intel.com>
      352fa202
  3. 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
  4. 21 1月, 2009 1 次提交
  5. 19 12月, 2008 1 次提交
  6. 18 10月, 2008 1 次提交
  7. 17 10月, 2008 1 次提交
  8. 11 10月, 2008 2 次提交
  9. 02 8月, 2008 1 次提交
  10. 18 3月, 2008 1 次提交
  11. 07 2月, 2008 1 次提交
  12. 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
  13. 04 8月, 2007 1 次提交
  14. 24 7月, 2007 1 次提交
  15. 02 7月, 2007 1 次提交
    • M
      asus_acpi: fix oops on non-asus machines · 5ebffd7c
      Maxime Austruy 提交于
      If asus_acpi_init doesn't find any device it knows about, it mistakenly
      returns a "success" error code even though it cleans up after itself.  Later
      when trying to rmmod asus_acpi, the module_exit routine would try to clean up
      one more time and we would end up calling
      acpi_bus_unregister_driver(&asus_hotk_driver) twice.  This patch addresses
      this first problem by returning -ENODEV when no appropriate device is found.
      
      Then there was also another bug with the code handling the return value of
      backlight_device_register.  If this function ever failed, the driver would
      cleanup by calling the module_exit routine from module_init, but it would
      still return "success".  So any attempt to rmmod this module would result in
      asus_acpi_exit being called twice but it's not ready to handle it (I haven't
      hit this bug, just found it by code inspection).  This patch fixes that by
      inserting a return -ENODEV; at the end of this error handling path.
      Signed-off-by: NMaxime Austruy <maxime@tralhalla.org>
      Cc: Len Brown <lenb@kernel.org>
      Cc: Richard Purdie <rpurdie@rpsys.net>
      Cc: Jan Engelhardt <jengelh@computergmbh.de>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      5ebffd7c
  16. 20 6月, 2007 1 次提交
  17. 01 6月, 2007 1 次提交
    • S
      acpi: fix section mismatch warning in asus + toshiba · b2b77b23
      Sam Ravnborg 提交于
      Fix following section mismatch warnings in acpi
      
      WARNING: drivers/acpi/asus_acpi.o(.init.text+0xb7): Section mismatch: reference to .exit.text: (after 'init_module')
      WARNING: o-i386/drivers/acpi/toshiba_acpi.o(.init.text+0x13a): Section mismatch: reference to .exit.text: (after 'init_module')
      
      The exit function is used in the init function during an error codition.
      As __exit may be discarded during link-time / run-time this is no good.
      Do not mark the exit function __exit.
      
      Note: This warning is only seen by my local copy of modpost
            but the change will soon hit upstream.
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      Cc: Len Brown <lenb@kernel.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      b2b77b23
  18. 20 2月, 2007 2 次提交
  19. 17 2月, 2007 1 次提交
  20. 13 2月, 2007 1 次提交
    • 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
  21. 09 2月, 2007 1 次提交
  22. 03 2月, 2007 1 次提交
  23. 21 12月, 2006 1 次提交
  24. 20 12月, 2006 1 次提交
    • Y
      ACPI: video: Add dev argument for backlight_device_register · 519ab5f2
      Yu Luming 提交于
      This patch set adds generic abstract layer support for acpi video driver to
      have generic user interface to control backlight and output switch control by
      leveraging the existing backlight sysfs class driver, and by adding a new
      video output sysfs class driver.
      
      This patch:
      
      Add dev argument for backlight_device_register to link the class device to
      real device object.  The platform specific driver should find a way to get the
      real device object for their video device.
      
      [akpm@osdl.org: build fix]
      [akpm@osdl.org: fix msi-laptop.c]
      Signed-off-by: NLuming Yu <Luming.yu@intel.com>
      Cc: "Antonino A. Daplas" <adaplas@pol.net>
      Cc: Greg KH <greg@kroah.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      519ab5f2
  25. 21 10月, 2006 1 次提交
  26. 14 10月, 2006 4 次提交
  27. 02 7月, 2006 1 次提交
  28. 01 7月, 2006 7 次提交