linux-toradex.git/drivers/leds/trigger/ledtrig-cpu.c, branch v5.18

leds: trigger: ledtrig-cpu: Fix incorrectly documented param 'ledevt'

2021-05-28T09:38:53+00:00

Fixes the following W=1 kernel build warning(s):

 drivers/leds/trigger/ledtrig-cpu.c:52: warning: Function parameter or member 'ledevt' not described in 'ledtrig_cpu'
 drivers/leds/trigger/ledtrig-cpu.c:52: warning: Excess function parameter 'evt' description in 'ledtrig_cpu'

Cc: Pavel Machek 
Cc: Linus Walleij 
Cc: Bryan Wu 
Cc: linux-leds@vger.kernel.org
Signed-off-by: Lee Jones 
Signed-off-by: Pavel Machek

ledtrig-cpu: Limit to 8 CPUs

2020-09-30T17:15:40+00:00

Some machines have thousands of CPUs... and trigger mechanisms was not
really meant for thousands of triggers. I doubt anyone uses this
trigger on many-CPU machine; but if they do, they'll need to do it
properly.

Signed-off-by: Pavel Machek

treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 500

2019-06-19T15:09:55+00:00

Based on 2 normalized pattern(s):

  this program is free software you can redistribute it and or modify
  it under the terms of the gnu general public license version 2 as
  published by the free software foundation

  this program is free software you can redistribute it and or modify
  it under the terms of the gnu general public license version 2 as
  published by the free software foundation #

extracted by the scancode license scanner the SPDX license identifier

  GPL-2.0-only

has been chosen to replace the boilerplate/reference in 4122 file(s).

Signed-off-by: Thomas Gleixner 
Reviewed-by: Enrico Weigelt 
Reviewed-by: Kate Stewart 
Reviewed-by: Allison Randal 
Cc: linux-spdx@vger.kernel.org
Link: https://lkml.kernel.org/r/20190604081206.933168790@linutronix.de
Signed-off-by: Greg Kroah-Hartman

leds/trigger/cpu: Add LED trigger for all CPUs aggregated

2017-03-06T21:06:47+00:00

Currently there is one CPU led trigger per cpu ('cpu0', 'cpu1', ...)

This patch adds a new trigger, 'cpu', with brightness proportional to
the number of active CPUs.

If multiple brightness levels aren't supported on the LED,
it effectively indicates if there is any CPU active.

This is particularly useful on tiny linux boards with more CPU cores than LED pins.

Signed-off-by: Paulo Costa 
Acked-by: Pavel Machek 
Signed-off-by: Jacek Anaszewski

cpu/hotplug: Cleanup state names

2016-12-25T09:47:44+00:00

When the state names got added a script was used to add the extra argument
to the calls. The script basically converted the state constant to a
string, but the cleanup to convert these strings into meaningful ones did
not happen.

Replace all the useless strings with 'subsys/xxx/yyy:state' strings which
are used in all the other places already.

Signed-off-by: Thomas Gleixner 
Cc: Peter Zijlstra 
Cc: Sebastian Siewior 
Link: http://lkml.kernel.org/r/20161221192112.085444152@linutronix.de
Signed-off-by: Thomas Gleixner

ledtrig-cpu.c: fix english

2016-11-22T11:07:03+00:00

Fix english spelling.

Signed-off-by: Pavel Machek 
Signed-off-by: Jacek Anaszewski

leds/trigger/cpu: Move from CPU_STARTING to ONLINE level

2016-07-22T19:53:18+00:00

There is no need the ledtriger to be called *that* early in the hotplug
process (+ with disabled interrupts). As explained by Jacek Anaszewski [0]
there is no need for it.
Therefore this patch moves it to the ONLINE/PREPARE_DOWN level using the
dynamic registration for the id.

[0] https://lkml.kernel.org/r/578C92BC.2070603@samsung.com

Signed-off-by: Sebastian Andrzej Siewior 
Acked-by: Jacek Anaszewski 
Acked-by: Linus Walleij 
Cc: Peter Zijlstra 
Cc: Paul Gortmaker 
Cc: Richard Purdie 
Cc: rt@linutronix.de
Cc: Linus Torvalds 
Cc: linux-leds@vger.kernel.org
Link: http://lkml.kernel.org/r/1469028295-14702-1-git-send-email-bigeasy@linutronix.de
Signed-off-by: Thomas Gleixner

leds/trigger/cpu: Convert to hotplug state machine

2016-07-15T08:40:26+00:00

This is a straightforward conversion. We place this callback last
in the list so that the LED illuminates only after a successful
bring up sequence.

( NOTE: The patch adds a FIXME question about the callback used,
        this question should probably be revisited later on.)

Signed-off-by: Richard Cochran 
Signed-off-by: Anna-Maria Gleixner 
Reviewed-by: Sebastian Andrzej Siewior 
Acked-by: Jacek Anaszewski 
Cc: Linus Torvalds 
Cc: Linus Walleij 
Cc: Paul Gortmaker 
Cc: Peter Zijlstra 
Cc: Richard Purdie 
Cc: Thomas Gleixner 
Cc: linux-leds@vger.kernel.org
Cc: rt@linutronix.de
Link: http://lkml.kernel.org/r/20160713153336.465496902@linutronix.de
Signed-off-by: Ingo Molnar

leds: ledtrig-cpu: Make the driver explicitly non-modular

2016-01-04T08:57:39+00:00

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 
Cc: Richard Purdie 
Cc: linux-leds@vger.kernel.org
Signed-off-by: Paul Gortmaker 
Acked-by: Linus Walleij 
Signed-off-by: Jacek Anaszewski

drivers/leds: Replace __get_cpu_var use through this_cpu_ptr

2014-05-08T06:28:08+00:00

Use this_cpu_ptr for the address calculation instead of __get_cpu_var.

Signed-off-by: Christoph Lameter 
Signed-off-by: Bryan Wu