1. 04 Apr, 2009 1 commit
    • Henrique de Moraes Holschuh's avatar
      thinkpad-acpi: restrict access to some firmware LEDs · a4d5effc
      Henrique de Moraes Holschuh authored
      Some of the ThinkPad LEDs indicate critical conditions that can cause
      data loss or cause hardware damage when ignored (e.g. force-ejecting
      a powered up bay; ignoring a failing battery, or empty battery; force-
      undocking with the dock buses still active, etc).
      On almost all ThinkPads, LED access is write-only, and the firmware
      usually does fire-and-forget signaling on them, so you effectively
      lose whatever message the firmware was trying to convey to the user
      when you override the LED state, without any chance to restore it.
      Restrict access to all LEDs that can convey important alarms, or that
      could mislead the user into incorrectly operating the hardware.  This
      will make the Lenovo engineers less unhappy about the whole issue.
      Allow users that really want it to still control all LEDs, it is the
      unaware user that we have to worry about.
      Signed-off-by: default avatarHenrique de Moraes Holschuh <hmh@hmh.eng.br>
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
  2. 03 Apr, 2009 1 commit
  3. 15 Mar, 2009 4 commits
  4. 18 Feb, 2009 2 commits
    • Randy Dunlap's avatar
      x86: dell-laptop: depends on POWER_SUPPLY · 310d8c93
      Randy Dunlap authored
      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: default avatarRandy 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: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
    • Alexey Dobriyan's avatar
      eeepc: should depend on INPUT · 3a5093ee
      Alexey Dobriyan authored
      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: default avatarAlexey Dobriyan <adobriyan@gmail.com>
      Cc: Len Brown <lenb@kernel.org>
      Cc: Ingo Molnar <mingo@elte.hu>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
  5. 20 Jan, 2009 1 commit
  6. 16 Jan, 2009 1 commit
  7. 15 Jan, 2009 1 commit
  8. 19 Dec, 2008 3 commits
  9. 12 Nov, 2008 2 commits
  10. 06 Nov, 2008 1 commit
    • Bjorn Helgaas's avatar
      ACPI: remove CONFIG_ACPI_EC · 8950d89a
      Bjorn Helgaas authored
      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: default avatarBjorn Helgaas <bjorn.helgaas@hp.com>
      Acked-by: default avatarAlexey Starikovskiy <astarikovskiy@suse.de>
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
  11. 22 Oct, 2008 1 commit
  12. 16 Oct, 2008 2 commits
  13. 08 Oct, 2008 1 commit
    • Carlos Corbacho's avatar
      acer-wmi: Add rfkill support for wireless and bluetooth · 0606e1ab
      Carlos Corbacho authored
      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: default avatarCarlos Corbacho <carlos@strangeworlds.co.uk>
      Acked-by: default avatarHenrique de Moraes Holschuh <hmh@hmh.eng.br>
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
  14. 24 Sep, 2008 1 commit
  15. 04 Aug, 2008 1 commit
  16. 01 Aug, 2008 2 commits
  17. 30 Jul, 2008 2 commits
  18. 25 Jul, 2008 4 commits
  19. 21 Jul, 2008 2 commits
    • David Altobelli's avatar
      HP iLO driver · 89bcb05d
      David Altobelli authored
      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: default avatarDavid Altobelli <david.altobelli@hp.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
    • Henrique de Moraes Holschuh's avatar
      ACPI: thinkpad-acpi: add bluetooth and WWAN rfkill support · 0e74dc26
      Henrique de Moraes Holschuh authored
      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
      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: default avatarHenrique de Moraes Holschuh <hmh@hmh.eng.br>
      Cc: Ivo van Doorn <IvDoorn@gmail.com>
      Cc: John W. Linville <linville@tuxdriver.com>
  20. 16 Jul, 2008 3 commits
    • Randy Dunlap's avatar
      fujitsu-laptop: depends on INPUT · c735ab7d
      Randy Dunlap authored
      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: default avatarRandy Dunlap <randy.dunlap@oracle.com>
      Signed-off-by: default avatarAndi Kleen <ak@linux.intel.com>
      Acked-by: default avatarJonathan Woithe <jwoithe@physics.adelaide.edu.au>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
    • Jonathan Woithe's avatar
      Fujitsu-laptop update · 20b93734
      Jonathan Woithe authored
      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: default avatarPeter Gruber <nokos@gmx.net>
      Signed-off-by: default avatarJonathan Woithe <jwoithe@physics.adelaide.edu.au>
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      Signed-off-by: default avatarAndi Kleen <ak@linux.intel.com>
    • Cezary Jackiewicz's avatar
      misc,acpi,backlight: compal Laptop Extras · 5411552c
      Cezary Jackiewicz authored
      This is driver for Compal Laptop: FL90/IFL90, based on MSI driver.
      This driver exports a few files in /sys/devices/platform/compal-laptop/:
       lcd_level - screen brightness: contains a single integer in the range 0..7 (rw)
       wlan - wlan subsystem state: contains 0 or 1 (rw)
       bluetooth - bluetooth subsystem state: contains 0 or 1 (rw)
       raw - raw value taken from embedded controller register (ro)
      In addition to these platform device attributes the driver registers itself
      in the Linux backlight control subsystem and is available to userspace under
      Signed-off-by: default avatarCezary Jackiewicz <cezary.jackiewicz@gmail.com>
      Signed-off-by: default avatarAndi Kleen <ak@linux.intel.com>
      Cc: Richard Purdie <rpurdie@rpsys.net>
      Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
      Cc: Len Brown <lenb@kernel.org>
      Cc: Alexey Starikovskiy <aystarik@gmail.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
  21. 29 Apr, 2008 4 commits