Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
切换分支/标签
  1. 25 5月, 2011 1 次提交
  3. 23 3月, 2011 1 次提交
  5. 31 1月, 2011 1 次提交
  7. 12 11月, 2010 1 次提交
  9. 26 5月, 2010 1 次提交
  11. 24 6月, 2009 3 次提交
    • R
      leds: Futher document blink_set · a1dd8c61
      由 Richard Purdie 提交于 
      Futher document blink_set function pointer
Signed-off-by: NRichard Purdie <rpurdie@linux.intel.com>
      a1dd8c61
    • T
      leds: Add options to have GPIO LEDs start on or keep their state · ed88bae6
      由 Trent Piepho 提交于 
      There already is a "default-on" trigger but there are problems with it.

For one, it's a inefficient way to do it and requires led trigger support
to be compiled in.

But the real reason is that is produces a glitch on the LED.  The GPIO is
allocate with the LED *off*, then *later* when the trigger runs it is
turned back on.  If the LED was already on via the GPIO's reset default or
action of the firmware, this produces a glitch where the LED goes from on
to off to on.  While normally this is fast enough that it wouldn't be
noticeable to a human observer, there are still serious problems.

One is that there may be something else on the GPIO line, like a hardware
alarm or watchdog, that is fast enough to notice the glitch.

Another is that the kernel may panic before the LED is turned back on, thus
hanging with the LED in the wrong state.  This is not just speculation, but
actually happened to me with an embedded system that has an LED which
should turn off when the kernel finishes booting, which was left in the
incorrect state due to a bug in the OF LED binding code.

We also let GPIO LEDs get their initial value from whatever the current
state of the GPIO line is.  On some systems the LEDs are put into some
state by the firmware or hardware before Linux boots, and it is desired to
have them keep this state which is otherwise unknown to Linux.

This requires that the underlying GPIO driver support reading the value of
output GPIOs.  Some drivers support this and some do not.

The platform device binding gains a field in the platform data
"default_state" that controls this.  There are three constants defined to
select from on, off, or keeping the current state.  The OpenFirmware
binding uses a property named "default-state" that can be set to "on",
"off", or "keep".  The default if the property isn't present is off.
Signed-off-by: NTrent Piepho <xyzzy@speakeasy.org>
Acked-by: NGrant Likely <grant.likely@secretlab.ca>
Acked-by: NWolfram Sang <w.sang@pengutronix.de>
Acked-by: NSean MacLennan <smaclennan@pikatech.com>
Signed-off-by: NRichard Purdie <rpurdie@linux.intel.com>
      ed88bae6
    • M
      leds: Further document parameters for blink_set() · 92722b1b
      由 Mark Brown 提交于 
      The documentation for the parameters of blink_set() was a bit hard
to find so put some where I'd expected to find it.
Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
Signed-off-by: NRichard Purdie <rpurdie@linux.intel.com>
      92722b1b
  13. 06 4月, 2009 2 次提交
  15. 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
  17. 08 1月, 2009 1 次提交
  19. 21 10月, 2008 1 次提交
    • T
      leds: Make default trigger fields const · 326bb8a5
      由 Trent Piepho 提交于 
      The default_trigger fields of struct gpio_led and thus struct
led_classdev are pretty much always assigned from a string literal,
which means the string can't be modified.  Which is fine, since there is
no reason to modify the string and in fact it never is.

But they should be marked const to prevent such code from being added,
to prevent warnings if -Wwrite-strings is used, when assigned from a
constant string other than a string literal (which produces a warning
under current kernel compiler flags), and for general good coding
practices.
Signed-off-by: NTrent Piepho <tpiepho@freescale.com>
Signed-off-by: NRichard Purdie <rpurdie@linux.intel.com>
      326bb8a5
  21. 23 7月, 2008 2 次提交
  23. 25 4月, 2008 3 次提交
  25. 20 4月, 2008 1 次提交
    • R
      PM: Remove destroy_suspended_device() · b844eba2
      由 Rafael J. Wysocki 提交于 
      After 2.6.24 there was a plan to make the PM core acquire all device
semaphores during a suspend/hibernation to protect itself from
concurrent operations involving device objects.  That proved to be
too heavy-handed and we found a better way to achieve the goal, but
before it happened, we had introduced the functions
device_pm_schedule_removal() and destroy_suspended_device() to allow
drivers to "safely" destroy a suspended device and we had adapted some
drivers to use them.  Now that these functions are no longer necessary,
it seems reasonable to remove them and modify their users to use the
normal device unregistration instead.
Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
Acked-by: NPavel Machek <pavel@ucw.cz>
Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      b844eba2
  27. 07 2月, 2008 1 次提交
  29. 06 2月, 2008 1 次提交
  31. 07 12月, 2007 1 次提交
  33. 12 9月, 2007 1 次提交
  35. 17 7月, 2007 1 次提交
  37. 16 7月, 2007 2 次提交
  39. 30 9月, 2006 1 次提交
  41. 11 4月, 2006 1 次提交
  43. 01 4月, 2006 3 次提交