summaryrefslogtreecommitdiff
path: root/drivers/usb/serial/Makefile-keyspan_pda_fw
blob: c20baf7280115785725ed9e49281ce5eb26f3d11 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16

# some rules to handle the quirks of the 'as31' assembler, like
# insisting upon fixed suffixes for the input and output files,
# and its lack of preprocessor support

all: keyspan_pda_fw.h

%.asm: %.S
	gcc -x assembler-with-cpp -P -E -o $@ $<

%.hex: %.asm
	as31 -l $<
	mv $*.obj $@

%_fw.h: %.hex ezusb_convert.pl
	perl ezusb_convert.pl $* < $< > $@
rDaniel Vetter <daniel.vetter@ffwll.ch>2017-01-30 10:17:32 +0100 commite6e7b48b295afa5a5ab440de0a94d9ad8b3ce2d0 (patch) tree77cadb6d8aad1b52c34e4afa8c9deef603bbe2ed /kernel/futex.c parent4e5b54f127426c82dc2816340c26d951a5bb3429 (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 'kernel/futex.c')