/* * Copyright (C) 2007 by Analog Devices, Inc. * * The Inventra Controller Driver for Linux 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. */ #ifndef __MUSB_BLACKFIN_H__ #define __MUSB_BLACKFIN_H__ /* * Blackfin specific definitions */ /* Anomalies notes: * * 05000450 - USB DMA Mode 1 Short Packet Data Corruption: * MUSB driver is designed to transfer buffer of N * maxpacket size * in DMA mode 1 and leave the rest of the data to the next * transfer in DMA mode 0, so we never transmit a short packet in * DMA mode 1. * * 05000463 - This anomaly doesn't affect this driver since it * never uses L1 or L2 memory as data destination. * * 05000464 - This anomaly doesn't affect this driver since it * never uses L1 or L2 memory as data source. * * 05000465 - The anomaly can be seen when SCLK is over 100 MHz, and there is * no way to workaround for bulk endpoints. Since the wMaxPackSize * of bulk is less than or equal to 512, while the fifo size of * endpoint 5, 6, 7 is 1024, the double buffer mode is enabled * automatically when these endpoints are used for bulk OUT. * * 05000466 - This anomaly doesn't affect this driver since it never mixes * concurrent DMA and core accesses to the TX endpoint FIFOs. * * 05000467 - The workaround for this anomaly will introduce another * anomaly - 05000465. */ /* The Mentor USB DMA engine on BF52x (silicon v0.0 and v0.1) seems to be * unstable in host mode. This may be caused by Anomaly 05000380. After * digging out the root cause, we will change this number accordingly. * So, need to either use silicon v0.2+ or disable DMA mode in MUSB. */ #if ANOMALY_05000380 && defined(CONFIG_BF52x) && \ !defined(CONFIG_MUSB_PIO_ONLY) # error "Please use PIO mode in MUSB driver on bf52x chip v0.0 and v0.1" #endif #undef DUMP_FIFO_DATA #ifdef DUMP_FIFO_DATA static void dump_fifo_data(u8 *buf, u16 len) { u8 *tmp = buf; int i; for (i = 0; i < len; i++) { if (!(i % 16) && i) pr_debug("\n"); pr_debug("%02x ", *tmp++); } pr_debug("\n"); } #else #define dump_fifo_data(buf, len) do {} while (0) #endif #define USB_DMA_BASE USB_DMA_INTERRUPT #define USB_DMAx_CTRL 0x04 #define USB_DMAx_ADDR_LOW 0x08 #define USB_DMAx_ADDR_HIGH 0x0C #define USB_DMAx_COUNT_LOW 0x10 #define USB_DMAx_COUNT_HIGH 0x14 #define USB_DMA_REG(ep, reg) (USB_DMA_BASE + 0x20 * ep + reg) /* Almost 1 second */ #define TIMER_DELAY (1 * HZ) static struct timer_list musb_conn_timer; #endif /* __MUSB_BLACKFIN_H__ */ linux/net-next.git/commit/net?id=e6e7b48b295afa5a5ab440de0a94d9ad8b3ce2d0'>net/rxrpc/sendmsg.c
diff options
context:
space:
mode:
authorDaniel Vetter <daniel.vetter@ffwll.ch>2017-01-12 17:15:56 +0100
committerDaniel Vetter <daniel.vetter@ffwll.ch>2017-01-30 10:17:32 +0100
commite6e7b48b295afa5a5ab440de0a94d9ad8b3ce2d0 (patch)
tree77cadb6d8aad1b52c34e4afa8c9deef603bbe2ed /net/rxrpc/sendmsg.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 'net/rxrpc/sendmsg.c')