1. 08 1月, 2011 1 次提交
  2. 16 8月, 2010 1 次提交
  3. 03 8月, 2010 2 次提交
    • A
      compal-laptop/fujitsu-laptop/msi-laptop: make dmi_check_cb to return 1 instead of 0 · 80183a4b
      Axel Lin 提交于
      dmi_check_system() walks the table running matching functions until
      someone returns non zero or we hit the end.
      
      This patch makes dmi_check_cb to return 1 so dmi_check_system() return
      immediately when a match is found.
      Signed-off-by: NAxel Lin <axel.lin@gmail.com>
      Acked-by: NJonathan Woithe <jwoithe@physics.adelaide.edu.au>
      Cc: Matthew Garrett <mjg@redhat.com>a
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NMatthew Garrett <mjg@redhat.com>
      80183a4b
    • R
      compal-laptop: add JHL90, battery & hwmon interface · 9be0fcb5
      Roald Frederickx 提交于
      The driver now supports the Compal JHL90 (which I use) and it has some
      added features.  The biggest novelties are a battery interface
      (power_supply) and a temperature and fan control interface (hmwon).  It
      also adds a power-off feature to the backlight subsystem and it exports a
      few files that can enable/disable wake_on_XXX events.
      
      Much of the original code of the old features is still there, but I've
      changed some names to keep the naming more coherent with the added
      functionalities.  (Sorry for the huge patch)
      
      Some technical stuff about the new driver:
      
      First of all, I'm not sure if the extra features also work on the other
      Compal boards.  Currently they only get enabled if the DMI data indicates
      you are on a JHL90 board.
      
      Secondly, I've noticed a quirk in my fan controller.  I have to re-send
      the wanted pwm-level to the controller every so often.  If I don't do
      this, the fanspeed will slowly rise until after a couple of minutes it's
      at full speed.  (Note that every normal userland application will probably
      update the pwm-level every so often anyway, based on temperature readings,
      so this might not be an issue in practice) If this turns out to be a
      problem with all the controllers, maybe we should implement a kernel timer
      and have the driver re-send the pwm level every XX seconds to make this
      transparent to userspace?  (However, I couldn't immediately find a way to
      do this cleanly.)
      
      Additional information can be found in the source comments.
      
      [akpm@linux-foundation.org: coding-style fixes]
      [akpm@linux-foundation.org: add missing semicolon]
      Signed-off-by: NRoald Frederickx <roald.frederickx@gmail.com>
      Cc: Matthew Garrett <mjg59@srcf.ucam.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NMatthew Garrett <mjg@redhat.com>
      9be0fcb5
  4. 17 3月, 2010 1 次提交
  5. 26 2月, 2010 2 次提交
  6. 12 12月, 2009 1 次提交
  7. 19 12月, 2008 1 次提交
    • L
      create drivers/platform/x86/ from drivers/misc/ · 41b16dce
      Len Brown 提交于
      Move x86 platform specific drivers from drivers/misc/
      to a new home under drivers/platform/x86/.
      
      The community has been maintaining x86 vendor-specific
      platform specific drivers under /drivers/misc/ for a few years.
      The oldest ones started life under drivers/acpi.
      They moved out of drivers/acpi/ because they don't actually
      implement the ACPI specification, but either simply
      use ACPI, or implement vendor-specific ACPI extensions.
      
      In the future we anticipate...
      drivers/misc/ will go away.
      other architectures will create drivers/platform/<arch>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      41b16dce
  8. 08 11月, 2008 1 次提交
  9. 17 7月, 2008 2 次提交