summaryrefslogtreecommitdiff
path: root/include/dt-bindings/leds/leds-netxbig.h
blob: 92658b0310b2ec741e7bf4e84a7e902397504afc (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
/*
 * This header provides constants for netxbig LED bindings.
 *
 * This file is licensed under the terms of the GNU General Public
 * License version 2.  This program is licensed "as is" without any
 * warranty of any kind, whether express or implied.
 */

#ifndef _DT_BINDINGS_LEDS_NETXBIG_H
#define _DT_BINDINGS_LEDS_NETXBIG_H

#define NETXBIG_LED_OFF		0
#define NETXBIG_LED_ON		1
#define NETXBIG_LED_SATA	2
#define NETXBIG_LED_TIMER1	3
#define NETXBIG_LED_TIMER2	4

#endif /* _DT_BINDINGS_LEDS_NETXBIG_H */
8c8b79c321e4a1f31f98194e4f6b6cae7'>79c6f448c8b79c321e4a1f31f98194e4f6b6cae7 (patch) tree370efda701f03cccf21e02bb1fdd3b852547d75c /sound/soc/pxa/raumfeld.c parent0c744ea4f77d72b3dcebb7a8f2684633ec79be88 (diff)
tracing: Fix hwlat kthread migration
The hwlat tracer creates a kernel thread at start of the tracer. It is pinned to a single CPU and will move to the next CPU after each period of running. If the user modifies the migration thread's affinity, it will not change after that happens. The original code created the thread at the first instance it was called, but later was changed to destroy the thread after the tracer was finished, and would not be created until the next instance of the tracer was established. The code that initialized the affinity was only called on the initial instantiation of the tracer. After that, it was not initialized, and the previous affinity did not match the current newly created one, making it appear that the user modified the thread's affinity when it did not, and the thread failed to migrate again. Cc: stable@vger.kernel.org Fixes: 0330f7aa8ee6 ("tracing: Have hwlat trace migrate across tracing_cpumask CPUs") Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'sound/soc/pxa/raumfeld.c')