<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/leds/led-triggers.c, branch v2.6.39-rc2</title>
<subtitle>Linux Kernel (branches are rebased on master from time to time)</subtitle>
<id>https://sre.ring0.de/linux/atom?h=v2.6.39-rc2</id>
<link rel='self' href='https://sre.ring0.de/linux/atom?h=v2.6.39-rc2'/>
<link rel='alternate' type='text/html' href='https://sre.ring0.de/linux/'/>
<updated>2011-01-31T13:30:24Z</updated>
<entry>
<title>leds: Add ability to blink via simple trigger</title>
<updated>2011-01-31T13:30:24Z</updated>
<author>
<name>Vasily Khoruzhick</name>
<email>anarsoul@gmail.com</email>
</author>
<published>2011-01-07T16:28:16Z</published>
<link rel='alternate' type='text/html' href='https://sre.ring0.de/linux/commit/?id=0b9536c957095eb1497828aa51b34ac695f67eae'/>
<id>urn:sha1:0b9536c957095eb1497828aa51b34ac695f67eae</id>
<content type='text'>
As blink API is now available, it's possible to add ability to blink via
simple trigger.

Signed-off-by: Vasily Khoruzhick &lt;anarsoul@gmail.com&gt;
Signed-off-by: Anton Vorontsov &lt;cbouatmailru@gmail.com&gt;
</content>
</entry>
<entry>
<title>led-class: always implement blinking</title>
<updated>2010-11-12T15:55:32Z</updated>
<author>
<name>Johannes Berg</name>
<email>johannes.berg@intel.com</email>
</author>
<published>2010-11-11T22:05:21Z</published>
<link rel='alternate' type='text/html' href='https://sre.ring0.de/linux/commit/?id=5ada28bf76752e33dce3d807bf0dfbe6d1b943ad'/>
<id>urn:sha1:5ada28bf76752e33dce3d807bf0dfbe6d1b943ad</id>
<content type='text'>
Currently, blinking LEDs can be awkward because it is not guaranteed that
all LEDs implement blinking.  The trigger that wants it to blink then
needs to implement its own timer solution.

Rather than require that, add led_blink_set() API that triggers can use.
This function will attempt to use hw blinking, but if that fails
implements a timer for it.  To stop blinking again, brightness_set() also
needs to be wrapped into API that will stop the software blink.

As a result of this, the timer trigger becomes a very trivial one, and
hopefully we can finally see triggers using blinking as well because it's
always easy to use.

Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
Acked-by: Richard Purdie &lt;rpurdie@linux.intel.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h</title>
<updated>2010-03-30T13:02:32Z</updated>
<author>
<name>Tejun Heo</name>
<email>tj@kernel.org</email>
</author>
<published>2010-03-24T08:04:11Z</published>
<link rel='alternate' type='text/html' href='https://sre.ring0.de/linux/commit/?id=5a0e3ad6af8660be21ca98a971cd00f331318c05'/>
<id>urn:sha1:5a0e3ad6af8660be21ca98a971cd00f331318c05</id>
<content type='text'>
percpu.h is included by sched.h and module.h and thus ends up being
included when building most .c files.  percpu.h includes slab.h which
in turn includes gfp.h making everything defined by the two files
universally available and complicating inclusion dependencies.

percpu.h -&gt; slab.h dependency is about to be removed.  Prepare for
this change by updating users of gfp and slab facilities include those
headers directly instead of assuming availability.  As this conversion
needs to touch large number of source files, the following script is
used as the basis of conversion.

  http://userweb.kernel.org/~tj/misc/slabh-sweep.py

The script does the followings.

* Scan files for gfp and slab usages and update includes such that
  only the necessary includes are there.  ie. if only gfp is used,
  gfp.h, if slab is used, slab.h.

* When the script inserts a new include, it looks at the include
  blocks and try to put the new include such that its order conforms
  to its surrounding.  It's put in the include block which contains
  core kernel includes, in the same order that the rest are ordered -
  alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
  doesn't seem to be any matching order.

* If the script can't find a place to put a new include (mostly
  because the file doesn't have fitting include block), it prints out
  an error message indicating which .h file needs to be added to the
  file.

The conversion was done in the following steps.

1. The initial automatic conversion of all .c files updated slightly
   over 4000 files, deleting around 700 includes and adding ~480 gfp.h
   and ~3000 slab.h inclusions.  The script emitted errors for ~400
   files.

2. Each error was manually checked.  Some didn't need the inclusion,
   some needed manual addition while adding it to implementation .h or
   embedding .c file was more appropriate for others.  This step added
   inclusions to around 150 files.

3. The script was run again and the output was compared to the edits
   from #2 to make sure no file was left behind.

4. Several build tests were done and a couple of problems were fixed.
   e.g. lib/decompress_*.c used malloc/free() wrappers around slab
   APIs requiring slab.h to be added manually.

5. The script was run on all .h files but without automatically
   editing them as sprinkling gfp.h and slab.h inclusions around .h
   files could easily lead to inclusion dependency hell.  Most gfp.h
   inclusion directives were ignored as stuff from gfp.h was usually
   wildly available and often used in preprocessor macros.  Each
   slab.h inclusion directive was examined and added manually as
   necessary.

6. percpu.h was updated not to include slab.h.

7. Build test were done on the following configurations and failures
   were fixed.  CONFIG_GCOV_KERNEL was turned off for all tests (as my
   distributed build env didn't work with gcov compiles) and a few
   more options had to be turned off depending on archs to make things
   build (like ipr on powerpc/64 which failed due to missing writeq).

   * x86 and x86_64 UP and SMP allmodconfig and a custom test config.
   * powerpc and powerpc64 SMP allmodconfig
   * sparc and sparc64 SMP allmodconfig
   * ia64 SMP allmodconfig
   * s390 SMP allmodconfig
   * alpha SMP allmodconfig
   * um on x86_64 SMP allmodconfig

8. percpu.h modifications were reverted so that it could be applied as
   a separate patch and serve as bisection point.

Given the fact that I had only a couple of failures from tests on step
6, I'm fairly confident about the coverage of this conversion patch.
If there is a breakage, it's likely to be something in one of the arch
headers which should be easily discoverable easily on most builds of
the specific arch.

Signed-off-by: Tejun Heo &lt;tj@kernel.org&gt;
Guess-its-ok-by: Christoph Lameter &lt;cl@linux-foundation.org&gt;
Cc: Ingo Molnar &lt;mingo@redhat.com&gt;
Cc: Lee Schermerhorn &lt;Lee.Schermerhorn@hp.com&gt;
</content>
</entry>
<entry>
<title>leds: Prevent multiple LED triggers with the same name</title>
<updated>2009-04-06T15:06:26Z</updated>
<author>
<name>Adam Nielsen</name>
<email>a.nielsen@shikadi.net</email>
</author>
<published>2009-02-17T22:18:04Z</published>
<link rel='alternate' type='text/html' href='https://sre.ring0.de/linux/commit/?id=700c6ea2242cf04ba3612fa7cf74763fffcc04fd'/>
<id>urn:sha1:700c6ea2242cf04ba3612fa7cf74763fffcc04fd</id>
<content type='text'>
Signed-off-by: Adam Nielsen &lt;a.nielsen@shikadi.net&gt;
Signed-off-by: Richard Purdie &lt;rpurdie@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>leds: Ensure led-&gt;trigger is set earlier</title>
<updated>2008-07-23T08:49:56Z</updated>
<author>
<name>Dmitry Baryshkov</name>
<email>dbaryshkov@gmail.com</email>
</author>
<published>2008-07-16T21:51:14Z</published>
<link rel='alternate' type='text/html' href='https://sre.ring0.de/linux/commit/?id=fe3025b55c8ed06929afe94e9c9095fc19d15aa0'/>
<id>urn:sha1:fe3025b55c8ed06929afe94e9c9095fc19d15aa0</id>
<content type='text'>
Make sure led-&gt;trigger is valid before calling trigger-&gt;activate

Signed-off-by: Dmitry Baryshkov &lt;dbaryshkov@gmail.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Richard Purdie &lt;rpurdie@rpsys.net&gt;
</content>
</entry>
<entry>
<title>leds: Cleanup various whitespace and code style issues</title>
<updated>2008-04-24T22:37:42Z</updated>
<author>
<name>Németh Márton</name>
<email>nm127@freemail.hu</email>
</author>
<published>2008-03-09T20:59:57Z</published>
<link rel='alternate' type='text/html' href='https://sre.ring0.de/linux/commit/?id=4d404fd5c51772720e9c72aa3185bd5119bc6e69'/>
<id>urn:sha1:4d404fd5c51772720e9c72aa3185bd5119bc6e69</id>
<content type='text'>
Break the lines which were more than 80 characters into more
lines; replace SPACEs with TABs; correct ident at switch-case;
change character encoding from ISO-8859-2 to UTF-8.

The order of the functions in led-triggers.c changed in order
the similar functions can still be together under titles
"Used by LED Class", "LED Trigger Interface" and "Simple
LED Tigger Interface" as was grouped before when exported
with EXPORT_SYMBOL.

Signed-off-by: Márton Németh &lt;nm127@freemail.hu&gt;
Signed-off-by: Richard Purdie &lt;rpurdie@rpsys.net&gt;
</content>
</entry>
<entry>
<title>leds: disable triggers on brightness set</title>
<updated>2008-04-24T22:34:18Z</updated>
<author>
<name>Németh Márton</name>
<email>nm127@freemail.hu</email>
</author>
<published>2008-03-09T20:54:37Z</published>
<link rel='alternate' type='text/html' href='https://sre.ring0.de/linux/commit/?id=0013b23d66a2768f5babbb0ea9f03ab067a990d8'/>
<id>urn:sha1:0013b23d66a2768f5babbb0ea9f03ab067a990d8</id>
<content type='text'>
Disable any active triggers when the brightness attribute is
set to zero.

Signed-off-by: Henrique de Moraes Holschuh &lt;hmh@hmh.eng.br&gt;
Signed-off-by: Márton Németh &lt;nm127@freemail.hu&gt;
Signed-off-by: Richard Purdie &lt;rpurdie@rpsys.net&gt;
</content>
</entry>
<entry>
<title>leds: Fix leds_list_lock locking issues</title>
<updated>2007-12-31T23:09:44Z</updated>
<author>
<name>Richard Purdie</name>
<email>rpurdie@rpsys.net</email>
</author>
<published>2007-12-31T23:09:44Z</published>
<link rel='alternate' type='text/html' href='https://sre.ring0.de/linux/commit/?id=72f8da329e07ad8a72c1f0e96b8955cfeb7c7329'/>
<id>urn:sha1:72f8da329e07ad8a72c1f0e96b8955cfeb7c7329</id>
<content type='text'>
Covert leds_list_lock to a rw_sempahore to match previous LED trigger
locking fixes, fixing lock ordering.

Signed-off-by: Richard Purdie &lt;rpurdie@rpsys.net&gt;
</content>
</entry>
<entry>
<title>leds: Fix led trigger locking bugs</title>
<updated>2007-12-07T09:06:53Z</updated>
<author>
<name>Richard Purdie</name>
<email>rpurdie@rpsys.net</email>
</author>
<published>2007-11-10T13:29:04Z</published>
<link rel='alternate' type='text/html' href='https://sre.ring0.de/linux/commit/?id=dc47206e552c0850ad11f7e9a1fca0a3c92f5d65'/>
<id>urn:sha1:dc47206e552c0850ad11f7e9a1fca0a3c92f5d65</id>
<content type='text'>
Convert part of the led trigger core from rw spinlocks to rw
semaphores. We're calling functions which can sleep from invalid
contexts otherwise. Fixes bug #9264.

Signed-off-by: Richard Purdie &lt;rpurdie@rpsys.net&gt;
</content>
</entry>
<entry>
<title>leds: Convert from struct class_device to struct device</title>
<updated>2007-07-16T00:15:51Z</updated>
<author>
<name>Richard Purdie</name>
<email>rpurdie@rpsys.net</email>
</author>
<published>2007-07-08T22:19:31Z</published>
<link rel='alternate' type='text/html' href='https://sre.ring0.de/linux/commit/?id=f8a7c6fe14f556ca8eeddce258cb21392d0c3a2f'/>
<id>urn:sha1:f8a7c6fe14f556ca8eeddce258cb21392d0c3a2f</id>
<content type='text'>
Convert the LEDs class from struct class_device to struct device
since class_device is scheduled for removal.

Signed-off-by: Richard Purdie &lt;rpurdie@rpsys.net&gt;
Acked-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
</feed>
