summaryrefslogtreecommitdiff
path: root/sound/drivers
diff options
context:
space:
mode:
authorPatrice Chotard <patrice.chotard@st.com>2017-01-27 15:45:11 +0100
committerPatrice Chotard <patrice.chotard@st.com>2017-01-27 16:17:13 +0100
commit8413299cb3933dade6186bbee8363f190032107e (patch)
tree896aae78c4c48d89d56da8544db2b1f76239536c /sound/drivers
parent7ce7d89f48834cefece7804d38fc5d85382edf77 (diff)
ARM: dts: STiH407-family: set snps,dis_u3_susphy_quirk
Since v4.10-rc1, the following logs appears in loop : [ 801.953836] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? [ 801.960455] xhci-hcd xhci-hcd.0.auto: Cannot set link state. [ 801.966611] usb usb6-port1: cannot disable (err = -32) [ 806.083772] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? [ 806.090370] xhci-hcd xhci-hcd.0.auto: Cannot set link state. [ 806.096494] usb usb6-port1: cannot disable (err = -32) After analysis, xhci try to set link in U3 and returns an error. Using snps,dis_u3_susphy_quirk fix this issue. Signed-off-by: Patrice Chotard <patrice.chotard@st.com>
Diffstat (limited to 'sound/drivers')
0 files changed, 0 insertions, 0 deletions
s can occur on power failure even though user called fsync(2). The other three patches change locking of DAX faults so that ->iomap_begin() is called in a more relaxed locking context and we are safe to start a transaction there for ext4" These have received a build success notification from the kbuild robot, and pass the latest libnvdimm unit tests. There have not been any -next releases since -rc1, so they have not appeared there" * 'libnvdimm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm: ext4: Simplify DAX fault path dax: Call ->iomap_begin without entry lock during dax fault dax: Finish fault completely when loading holes dax: Avoid page invalidation races and unnecessary radix tree traversals mm: Invalidate DAX radix tree entries only if appropriate ext2: Return BH_New buffers for zeroed blocks
Diffstat (limited to 'kernel/nsproxy.c')