<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/leds/trigger, branch v4.5</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v4.5</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v4.5'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2016-01-04T08:57:39Z</updated>
<entry>
<title>leds: ledtrig-ide-disk: Make the driver explicitly non-modular</title>
<updated>2016-01-04T08:57:39Z</updated>
<author>
<name>Paul Gortmaker</name>
<email>paul.gortmaker@windriver.com</email>
</author>
<published>2015-12-13T21:45:50Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=067a8f3cad97f7b7d21ea05cbd2289aaa0f259df'/>
<id>urn:sha1:067a8f3cad97f7b7d21ea05cbd2289aaa0f259df</id>
<content type='text'>
The Kconfig for this driver is currently:

config LEDS_TRIGGER_IDE_DISK
        bool "LED IDE Disk Trigger"

...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essentially orphaned, so that
when reading the driver there is no doubt it is builtin-only.

Since module_init translates to device_initcall in the non-modular
case, the init ordering remains unchanged with this commit.

We also delete the MODULE_LICENSE tag etc. since all that information
is already contained at the top of the file in the comments.

Cc: Bryan Wu &lt;cooloney@gmail.com&gt;
Cc: Richard Purdie &lt;rpurdie@rpsys.net&gt;
Cc: linux-leds@vger.kernel.org
Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;
Signed-off-by: Jacek Anaszewski &lt;j.anaszewski@samsung.com&gt;
</content>
</entry>
<entry>
<title>leds: ledtrig-cpu: Make the driver explicitly non-modular</title>
<updated>2016-01-04T08:57:39Z</updated>
<author>
<name>Paul Gortmaker</name>
<email>paul.gortmaker@windriver.com</email>
</author>
<published>2015-12-13T21:45:49Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=227a0ca17eadf339f489683ac2cf4eb33b2e5319'/>
<id>urn:sha1:227a0ca17eadf339f489683ac2cf4eb33b2e5319</id>
<content type='text'>
The Kconfig for this driver is currently:

config LEDS_TRIGGER_CPU
        bool "LED CPU Trigger"

...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essentially orphaned, so that
when reading the driver there is no doubt it is builtin-only.

Since module_init translates to device_initcall in the non-modular
case, the init ordering remains unchanged with this commit.

We also delete the MODULE_LICENSE tag etc. since all that information
is already contained at the top of the file in the comments.

Cc: Bryan Wu &lt;cooloney@gmail.com&gt;
Cc: Richard Purdie &lt;rpurdie@rpsys.net&gt;
Cc: linux-leds@vger.kernel.org
Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;
Acked-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;
Signed-off-by: Jacek Anaszewski &lt;j.anaszewski@samsung.com&gt;
</content>
</entry>
<entry>
<title>leds: triggers: oneshot: fix module license specification</title>
<updated>2016-01-04T08:57:36Z</updated>
<author>
<name>Uwe Kleine-König</name>
<email>u.kleine-koenig@pengutronix.de</email>
</author>
<published>2015-11-12T09:20:39Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=fb65ee94ee3ae8fde4922262f73dddea2172e3ef'/>
<id>urn:sha1:fb65ee94ee3ae8fde4922262f73dddea2172e3ef</id>
<content type='text'>
The header of this file fixes the license to GPL 2 only without the
option to use later version. So use the string "GPL v2" that is to be
used in this case.

Signed-off-by: Uwe Kleine-König &lt;u.kleine-koenig@pengutronix.de&gt;
Acked-by: Fabio Baltieri &lt;fabio.baltieri@gmail.com&gt;
Signed-off-by: Jacek Anaszewski &lt;j.anaszewski@samsung.com&gt;
</content>
</entry>
<entry>
<title>leds: ledtrig-transient: fix duration to be msec instead of jiffies</title>
<updated>2016-01-04T08:57:36Z</updated>
<author>
<name>Rob Herring</name>
<email>robh@kernel.org</email>
</author>
<published>2015-11-10T23:10:17Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=22f933add429523923360e3d0c171c7df1bd4981'/>
<id>urn:sha1:22f933add429523923360e3d0c171c7df1bd4981</id>
<content type='text'>
The transient trigger duration is documented to be in msec units, but is
actually in jiffies units. Other time based triggers are in msec units
as well. Fix the timer setup to convert from msec.

This could break an existing userspace that worked around this problem,
but exposing jiffies to userspace is just wrong and would break anyway
if HZ is changed.

Signed-off-by: Rob Herring &lt;robh@kernel.org&gt;
Cc: Shuah Khan &lt;shuahkhan@gmail.com&gt;
Cc: Richard Purdie &lt;rpurdie@rpsys.net&gt;
Cc: linux-leds@vger.kernel.org
Signed-off-by: Jacek Anaszewski &lt;j.anaszewski@samsung.com&gt;
</content>
</entry>
<entry>
<title>leds: core: Add led_set_brightness_nosleep{nopm} functions</title>
<updated>2016-01-04T08:57:30Z</updated>
<author>
<name>Jacek Anaszewski</name>
<email>j.anaszewski@samsung.com</email>
</author>
<published>2015-10-07T09:10:41Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=81fe8e5b73e3f4de578ac7f53c1d956d4f58b8d4'/>
<id>urn:sha1:81fe8e5b73e3f4de578ac7f53c1d956d4f58b8d4</id>
<content type='text'>
This patch adds led_set_brightness_nosleep() and led_set_brightness_nopm()
functions, that guarantee setting LED brightness in a non-blocking way.
The latter is used from pm_ops context and doesn't modify the brightness
cached in the struct led_classdev. Its execution always ends up with
a call to brightness setting op - either directly or through
a set_brightness_work, regardless of LED_SUSPENDED flag state.

The patch also replaces led_set_brightness_async() with
led_set_brightness_nosleep() in all places where the most vital was setting
brightness in a non sleeping way but not necessarily asynchronously, which
is not needed for non-blocking drivers.

Signed-off-by: Jacek Anaszewski &lt;j.anaszewski@samsung.com&gt;
Acked-by: Sakari Ailus &lt;sakari.ailus@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>leds: triggers: add invert to heartbeat</title>
<updated>2015-11-03T07:59:23Z</updated>
<author>
<name>Jiri Prchal</name>
<email>jiri.prchal@aksignal.cz</email>
</author>
<published>2015-10-08T08:32:26Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=1c7b9d0edf5ada916fd02e66355f79f2089ee095'/>
<id>urn:sha1:1c7b9d0edf5ada916fd02e66355f79f2089ee095</id>
<content type='text'>
This patch adds possibility to invert heartbeat blinking.
The inverted LED is more time ON then OFF. It's because it looks
better when the heartbeat LED is next to other LED which is most
time ON. The invert value is exported same way via sysfs in file
invert like oneshot. I get inspiration from this trigger.

Signed-off-by: Jiri Prchal &lt;jiri.prchal@aksignal.cz&gt;
Signed-off-by: Jacek Anaszewski &lt;j.anaszewski@samsung.com&gt;
</content>
</entry>
<entry>
<title>leds: Allow compile test of GPIO consumers if !GPIOLIB</title>
<updated>2015-08-28T12:05:57Z</updated>
<author>
<name>Geert Uytterhoeven</name>
<email>geert@linux-m68k.org</email>
</author>
<published>2015-05-05T16:32:25Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=823227419588001f2d4accf3c5660cd99442a0f8'/>
<id>urn:sha1:823227419588001f2d4accf3c5660cd99442a0f8</id>
<content type='text'>
The GPIO subsystem provides dummy GPIO consumer functions if GPIOLIB is
not enabled. Hence drivers that depend on GPIOLIB, but use GPIO consumer
functionality only, can still be compiled if GPIOLIB is not enabled.

Relax the dependency on GPIOLIB if COMPILE_TEST is enabled, where
appropriate.

Signed-off-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;
Cc: Richard Purdie &lt;rpurdie@rpsys.net&gt;
Cc: linux-leds@vger.kernel.org
Signed-off-by: Jacek Anaszewski &lt;j.anaszewski@samsung.com&gt;
</content>
</entry>
<entry>
<title>leds: Add support for setting brightness in a synchronous way</title>
<updated>2014-11-14T22:29:35Z</updated>
<author>
<name>Jacek Anaszewski</name>
<email>j.anaszewski@samsung.com</email>
</author>
<published>2014-11-14T10:50:18Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=4d71a4a12b130ad033219e6f58c74a64059415eb'/>
<id>urn:sha1:4d71a4a12b130ad033219e6f58c74a64059415eb</id>
<content type='text'>
There are use cases when setting a LED brightness has to
have immediate effect (e.g. setting a torch LED brightness).
This patch extends LED subsystem to support such operations.
The LED subsystem internal API __led_set_brightness is changed
to led_set_brightness_async and new led_set_brightness_sync API
is added.

Signed-off-by: Jacek Anaszewski &lt;j.anaszewski@samsung.com&gt;
Acked-by: Kyungmin Park &lt;kyungmin.park@samsung.com&gt;
Cc: Richard Purdie &lt;rpurdie@rpsys.net&gt;
Signed-off-by: Bryan Wu &lt;cooloney@gmail.com&gt;
</content>
</entry>
<entry>
<title>leds: trigger: gpio: fix warning in gpio trigger for gpios whose accessor function may sleep</title>
<updated>2014-09-11T23:57:51Z</updated>
<author>
<name>Lothar Waßmann</name>
<email>LW@karo-electronics.de</email>
</author>
<published>2014-09-09T07:40:32Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=914ae25a62e77ebbfa0ce7cbc60edd01cc4d1d31'/>
<id>urn:sha1:914ae25a62e77ebbfa0ce7cbc60edd01cc4d1d31</id>
<content type='text'>
When using a GPIO driver whose accessor functions may sleep (e.g. an
I2C GPIO extender like PCA9554) the following warning is issued:
WARNING: CPU: 0 PID: 665 at drivers/gpio/gpiolib.c:2274 gpiod_get_raw_value+0x3c/0x48()
Modules linked in:
CPU: 0 PID: 665 Comm: kworker/0:2 Not tainted 3.16.0-karo+ #115
Workqueue: events gpio_trig_work
[&lt;c00142cc&gt;] (unwind_backtrace) from [&lt;c00118f8&gt;] (show_stack+0x10/0x14)
[&lt;c00118f8&gt;] (show_stack) from [&lt;c001bf10&gt;] (warn_slowpath_common+0x64/0x84)
[&lt;c001bf10&gt;] (warn_slowpath_common) from [&lt;c001bf4c&gt;] (warn_slowpath_null+0x1c/0x24)
[&lt;c001bf4c&gt;] (warn_slowpath_null) from [&lt;c020a1b8&gt;] (gpiod_get_raw_value+0x3c/0x48)
[&lt;c020a1b8&gt;] (gpiod_get_raw_value) from [&lt;c02f68a0&gt;] (gpio_trig_work+0x1c/0xb0)
[&lt;c02f68a0&gt;] (gpio_trig_work) from [&lt;c0030c1c&gt;] (process_one_work+0x144/0x38c)
[&lt;c0030c1c&gt;] (process_one_work) from [&lt;c0030ef8&gt;] (worker_thread+0x60/0x5cc)
[&lt;c0030ef8&gt;] (worker_thread) from [&lt;c0036dd4&gt;] (kthread+0xb4/0xd0)
[&lt;c0036dd4&gt;] (kthread) from [&lt;c000f0f0&gt;] (ret_from_fork+0x14/0x24)
---[ end trace cd51a1dad8b86c9c ]---

Fix this by using the _cansleep() variant of gpio_get_value().

Signed-off-by: Lothar Waßmann &lt;LW@KARO-electronics.de&gt;
Signed-off-by: Bryan Wu &lt;cooloney@gmail.com&gt;
</content>
</entry>
<entry>
<title>drivers/leds: Replace __get_cpu_var use through this_cpu_ptr</title>
<updated>2014-05-08T06:28:08Z</updated>
<author>
<name>Christoph Lameter</name>
<email>cl@linux.com</email>
</author>
<published>2014-05-05T16:48:38Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=24c9301ffd21356bcd865a5155a501e5059c4c6f'/>
<id>urn:sha1:24c9301ffd21356bcd865a5155a501e5059c4c6f</id>
<content type='text'>
Use this_cpu_ptr for the address calculation instead of __get_cpu_var.

Signed-off-by: Christoph Lameter &lt;cl@linux.com&gt;
Signed-off-by: Bryan Wu &lt;cooloney@gmail.com&gt;
</content>
</entry>
</feed>
