1. 24 6月, 2009 3 次提交
  2. 04 6月, 2009 1 次提交
    • J
      rfkill: rewrite · 19d337df
      Johannes Berg 提交于
      This patch completely rewrites the rfkill core to address
      the following deficiencies:
      
       * all rfkill drivers need to implement polling where necessary
         rather than having one central implementation
      
       * updating the rfkill state cannot be done from arbitrary
         contexts, forcing drivers to use schedule_work and requiring
         lots of code
      
       * rfkill drivers need to keep track of soft/hard blocked
         internally -- the core should do this
      
       * the rfkill API has many unexpected quirks, for example being
         asymmetric wrt. alloc/free and register/unregister
      
       * rfkill can call back into a driver from within a function the
         driver called -- this is prone to deadlocks and generally
         should be avoided
      
       * rfkill-input pointlessly is a separate module
      
       * drivers need to #ifdef rfkill functions (unless they want to
         depend on or select RFKILL) -- rfkill should provide inlines
         that do nothing if it isn't compiled in
      
       * the rfkill structure is not opaque -- drivers need to initialise
         it correctly (lots of sanity checking code required) -- instead
         force drivers to pass the right variables to rfkill_alloc()
      
       * the documentation is hard to read because it always assumes the
         reader is completely clueless and contains way TOO MANY CAPS
      
       * the rfkill code needlessly uses a lot of locks and atomic
         operations in locked sections
      
       * fix LED trigger to actually change the LED when the radio state
         changes -- this wasn't done before
      Tested-by: NAlan Jenkins <alan-jenkins@tuffmail.co.uk>
      Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br> [thinkpad]
      Signed-off-by: NJohannes Berg <johannes@sipsolutions.net>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      19d337df
  3. 04 4月, 2009 3 次提交
  4. 16 3月, 2009 4 次提交
  5. 19 2月, 2009 2 次提交
    • R
      x86: dell-laptop: depends on POWER_SUPPLY · 310d8c93
      Randy Dunlap 提交于
      Build breaks when DELL_LAPTOP=y and POWER_SUPPLY=m.  DELL_LAPTOP needs to
      depend on POWER_SUPPLY.
      
      dell-laptop.c:(.text+0x1ef3c4): undefined reference to `power_supply_is_system_supplied'
      dell-laptop.c:(.text+0x1ef45e): undefined reference to `power_supply_is_system_supplied'
      Signed-off-by: NRandy Dunlap <randy.dunlap@oracle.com>
      Cc: Matthew Garrett <mjg59@srcf.ucam.org>
      Cc: Ingo Molnar <mingo@elte.hu>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: "H. Peter Anvin" <hpa@zytor.com>
      Cc: Len Brown <lenb@kernel.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      310d8c93
    • A
      eeepc: should depend on INPUT · 3a5093ee
      Alexey Dobriyan 提交于
      Otherwise with INPUT=m, EEEPC_LAPTOP=y one gets
      
      drivers/built-in.o: In function `input_sync':
      eeepc-laptop.c:(.text+0x18ce51): undefined reference to `input_event'
      drivers/built-in.o: In function `input_report_key':
      eeepc-laptop.c:(.text+0x18ce73): undefined reference to `input_event'
      drivers/built-in.o: In function `eeepc_hotk_check':
      eeepc-laptop.c:(.text+0x18d05f): undefined reference to `input_allocate_device'
      eeepc-laptop.c:(.text+0x18d10f): undefined reference to `input_register_device'
      eeepc-laptop.c:(.text+0x18d131): undefined reference to `input_free_device'
      drivers/built-in.o: In function `eeepc_backlight_exit':
      eeepc-laptop.c:(.text+0x18d546): undefined reference to `input_unregister_device'
      Signed-off-by: NAlexey Dobriyan <adobriyan@gmail.com>
      Cc: Len Brown <lenb@kernel.org>
      Cc: Ingo Molnar <mingo@elte.hu>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      3a5093ee
  6. 21 1月, 2009 1 次提交
  7. 17 1月, 2009 1 次提交
  8. 16 1月, 2009 1 次提交
  9. 19 12月, 2008 3 次提交
  10. 13 11月, 2008 2 次提交
  11. 07 11月, 2008 1 次提交
    • B
      ACPI: remove CONFIG_ACPI_EC · 8950d89a
      Bjorn Helgaas 提交于
      Remove CONFIG_ACPI_EC.  It was always set the same as CONFIG_ACPI,
      and it had no menu label, so there was no way to set it to anything
      other than "y".
      
      Per section 6.5.4 of the ACPI 3.0b specification,
      
          OSPM must make Embedded Controller operation regions, accessed
          via the Embedded Controllers described in ECDT, available before
          executing any control method.
      
      The ECDT table is optional, but if it is present, the above text
      means that the EC it describes is a required part of the ACPI
      subsystem, so CONFIG_ACPI_EC=n wouldn't make sense.
      Signed-off-by: NBjorn Helgaas <bjorn.helgaas@hp.com>
      Acked-by: NAlexey Starikovskiy <astarikovskiy@suse.de>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      8950d89a
  12. 23 10月, 2008 1 次提交
  13. 17 10月, 2008 2 次提交
  14. 09 10月, 2008 1 次提交
    • C
      acer-wmi: Add rfkill support for wireless and bluetooth · 0606e1ab
      Carlos Corbacho 提交于
      This patch implements rfkill support for the wireless and bluetooth devices
      commonly found on Acer laptops.
      
      For now, we will always poll these devices once a second to guarantee we
      can catch state changes. On newer Acer laptops, it may be possible to rely
      on WMI events to do this instead, and experimental support for this will be
      added in a later patch.
      
      3G has been deliberately left off for now, as we still have no way to
      detect it, (nor, AFAIK, has any Linux user tried the code) and on laptops
      that don't support 3G, trying to poll for the status will leave the logs
      full of ACPI tracebacks.
      
      The old sysfs interface for wireless and bluetooth will be removed in a
      later patch.
      
      (Thanks to Henrique de Moraes Holschuh and Dmitry Torokhov for reviewing
      this patch).
      Signed-off-by: NCarlos Corbacho <carlos@strangeworlds.co.uk>
      Acked-by: NHenrique de Moraes Holschuh <hmh@hmh.eng.br>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      0606e1ab
  15. 24 9月, 2008 1 次提交
  16. 05 8月, 2008 1 次提交
  17. 02 8月, 2008 2 次提交
  18. 31 7月, 2008 2 次提交
  19. 26 7月, 2008 4 次提交
  20. 22 7月, 2008 1 次提交
    • D
      HP iLO driver · 89bcb05d
      David Altobelli 提交于
      A driver for the HP iLO/iLO2 management processor, which allows userspace
      programs to query the management processor.  Programs can open a channel
      to the device (/dev/hpilo/dXccbN), and use this to send/receive queries.  
      The O_EXCL open flag is used to indicate that a particular channel cannot
      be shared between processes.  This driver will replace various packages
      HP has shipped, including hprsm and hp-ilo.
      Signed-off-by: NDavid Altobelli <david.altobelli@hp.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      89bcb05d
  21. 21 7月, 2008 1 次提交
    • H
      ACPI: thinkpad-acpi: add bluetooth and WWAN rfkill support · 0e74dc26
      Henrique de Moraes Holschuh 提交于
      Add a read/write rfkill interface to the bluetooth radio switch on the
      bluetooth submodule, and one for the wireless wan radio switch to the wan
      submodule.
      
      Since rfkill does care for when a switch changes state, use WLSW
      notifications to also check if the WWAN or Bluetooth switches did not
      change state (due to them being slaves of WLSW in firmware/hardware, but
      that reality not being always properly exported by the thinkpad firmware).
      Signed-off-by: NHenrique de Moraes Holschuh <hmh@hmh.eng.br>
      Cc: Ivo van Doorn <IvDoorn@gmail.com>
      Cc: John W. Linville <linville@tuxdriver.com>
      0e74dc26
  22. 17 7月, 2008 2 次提交
    • R
      fujitsu-laptop: depends on INPUT · c735ab7d
      Randy Dunlap 提交于
      fujitsu-laptop uses input_* functions, so it should depend on INPUT.
      
      drivers/built-in.o: In function `acpi_fujitsu_add':
      fujitsu-laptop.c:(.text+0xaaec7): undefined reference to `input_allocate_device'
      fujitsu-laptop.c:(.text+0xaaf39): undefined reference to `input_register_device'
      fujitsu-laptop.c:(.text+0xab025): undefined reference to `input_free_device'
      drivers/built-in.o: In function `acpi_fujitsu_notify':
      fujitsu-laptop.c:(.text+0xab0d8): undefined reference to `input_event'
      fujitsu-laptop.c:(.text+0xab0e5): undefined reference to `input_event'
      fujitsu-laptop.c:(.text+0xab0f5): undefined reference to `input_event'
      fujitsu-laptop.c:(.text+0xab102): undefined reference to `input_event'
      drivers/built-in.o: In function `acpi_fujitsu_hotkey_notify':
      fujitsu-laptop.c:(.text+0xab261): undefined reference to `input_event'
      drivers/built-in.o:fujitsu-laptop.c:(.text+0xab26e): more undefined references to `input_event' follow
      drivers/built-in.o: In function `acpi_fujitsu_hotkey_add':
      fujitsu-laptop.c:(.text+0xab49c): undefined reference to `input_allocate_device'
      fujitsu-laptop.c:(.text+0xab51a): undefined reference to `input_register_device'
      fujitsu-laptop.c:(.text+0xab5e4): undefined reference to `input_free_device'
      make[1]: *** [.tmp_vmlinux1] Error 1
      Signed-off-by: NRandy Dunlap <randy.dunlap@oracle.com>
      Signed-off-by: NAndi Kleen <ak@linux.intel.com>
      Acked-by: NJonathan Woithe <jwoithe@physics.adelaide.edu.au>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      c735ab7d
    • J
      Fujitsu-laptop update · 20b93734
      Jonathan Woithe 提交于
      Add additional capabilities to the Fujitsu-laptop driver.
      
       * Brightness hotkey actions are sent to userspace. This can be disabled
         using a module parameter if it causes issues with models which handle
         these keys transparently in the BIOS.
      
       * Actions of additional hotkeys found on some Fujitsu models (eg: the
         suspend key and the dedicated "power on passphrase" keys) are broadcast
         to userspace.
      
       * An alternative brightness control method used by some Fujitsu models
         (for example, the S6410) is now supported, enabling software brightness
         controls on models using this method.
      
       * DMI-based module aliases are configured for the S6410 and S7020.
      
       * The current LCD brightness after booting should now be reflected in the
         standard backlight interface sysfs file (previously it was always set to
         0).  The platform brightness sysfs interface has always been fine.
      
      Thanks go to Peter Gruber who provided a significant portion of this code
      and tested various iterations of the patch on his S6410.
      Signed-off-by: NPeter Gruber <nokos@gmx.net>
      Signed-off-by: NJonathan Woithe <jwoithe@physics.adelaide.edu.au>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      Signed-off-by: NAndi Kleen <ak@linux.intel.com>
      20b93734