1. 06 4月, 2009 1 次提交
    • T
      leds: Add openfirmware platform device support · a7d878af
      Trent Piepho 提交于
      Add bindings to support LEDs defined as of_platform devices in addition to
      the existing bindings for platform devices.
      
      New options in Kconfig allow the platform binding code and/or the
      of_platform code to be turned on.  The of_platform code is of course only
      available on archs that have OF support.
      
      The existing probe and remove methods are refactored to use new functions
      create_gpio_led(), to create and register one led, and delete_gpio_led(),
      to unregister and free one led.  The new probe and remove methods for the
      of_platform driver can then share most of the common probe and remove code
      with the platform driver.
      
      The suspend and resume methods aren't shared, but they are very short.  The
      actual led driving code is the same for LEDs created by either binding.
      
      The OF bindings are based on patch by Anton Vorontsov
      <avorontsov@ru.mvista.com>.  They have been extended to allow multiple LEDs
      per device.
      Signed-off-by: NTrent Piepho <tpiepho@freescale.com>
      Acked-by: NGrant Likely <grant.likely@secretlab.ca>
      Acked-by: NSean MacLennan <smaclennan@pikatech.com>
      Signed-off-by: NRichard Purdie <rpurdie@linux.intel.com>
      a7d878af
  2. 09 1月, 2009 1 次提交
    • R
      leds: Add suspend/resume to the core class · 859cb7f2
      Richard Purdie 提交于
      Add suspend/resume to the core class and remove all the now unneeded
      code from various drivers. Originally the class code couldn't support
      suspend/resume but since class_device can there is no reason for
      each driver doing its own suspend/resume anymore.
      859cb7f2
  3. 25 4月, 2008 1 次提交
  4. 16 4月, 2008 1 次提交
  5. 01 4月, 2008 2 次提交
  6. 07 2月, 2008 1 次提交
  7. 06 11月, 2007 1 次提交
    • D
      leds: bugfixes for leds-gpio · 199fb21d
      David Brownell 提交于
      Three bugfixes to the leds-gpio driver, plus minor whitespace tweaks:
      
       - Do the INIT_WORK() before registering each LED, so if its trigger
         becomes immediately active it can schedule work without oopsing..
      
       - Use normal registration, not platform_driver_probe(), so that
         devices appearing "late" (hotplug type) can still be bound.
      
       - Mark the driver remove code as "__devexit", preventing oopses
         when the underlying device is removed.
      
      These issues came up when using this driver with some GPIO expanders
      living on serial busses, which act unlike "normal" platform devices:
      they can appear and vanish along with the serial bus driver.
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: NRichard Purdie <rpurdie@rpsys.net>
      199fb21d
  8. 16 7月, 2007 2 次提交