summaryrefslogtreecommitdiff
path: root/include/dt-bindings/leds/leds-pca9532.h
blob: 4d917aab7e1ea5beb62028ff22854dcdf755116f (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
/*
 * This header provides constants for pca9532 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_PCA9532_H
#define _DT_BINDINGS_LEDS_PCA9532_H

#define PCA9532_TYPE_NONE         0
#define PCA9532_TYPE_LED          1
#define PCA9532_TYPE_N2100_BEEP   2
#define PCA9532_TYPE_GPIO         3
#define PCA9532_LED_TIMER2        4

#endif /* _DT_BINDINGS_LEDS_PCA9532_H */
href='/cgit.cgi/linux/net-next.git/commit/tools/lib/traceevent?id=4e5b54f127426c82dc2816340c26d951a5bb3429'>4e5b54f127426c82dc2816340c26d951a5bb3429 (diff)
drm: Don't race connector registration
I was under the misconception that the sysfs dev stuff can be fully set up, and then registered all in one step with device_add. That's true for properties and property groups, but not for parents and child devices. Those must be fully registered before you can register a child. Add a bit of tracking to make sure that asynchronous mst connector hotplugging gets this right. For consistency we rely upon the implicit barriers of the connector->mutex, which is taken anyway, to ensure that at least either the connector or device registration call will work out. Mildly tested since I can't reliably reproduce this on my mst box here. Reported-by: Dave Hansen <dave.hansen@intel.com> Cc: Dave Hansen <dave.hansen@intel.com> Acked-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Chris Wilson <chris@chris-wilson.co.uk> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com> Link: http://patchwork.freedesktop.org/patch/msgid/1484237756-2720-1-git-send-email-daniel.vetter@ffwll.ch
Diffstat (limited to 'tools/lib/traceevent')