Synopsis Designware USB3 IP earlier than v3.00a which is configured in silicon
with DWC_USB3_SUSPEND_ON_DISCONNECT_EN=1, would need a specific quirk to prevent
xhci host controller from dying when device is disconnected.
Since DWC_USB3_SUSPEND_ON_DISCONNECT_EN is an IP configuration whose state
This patch adds support for Synopsis DesignWare USB3 IP Core found
on Fujitsu Socs.
Signed-off-by: Sneeker Yeh sneeker@tw.fujitsu.com
---
.../devicetree/bindings/usb/fujitsu-dwc3.txt | 33
drivers/usb/dwc3/Kconfig | 11 ++
drivers/usb/dwc3/Makefile
If an xhci platform has Synopsis device disconnection errata then enable
XHCI_DISCONNECT_QUIRK quirk flag.
Signed-off-by: Sneeker Yeh sneeker@tw.fujitsu.com
---
drivers/usb/host/xhci-plat.c |3 +++
include/linux/usb/xhci_pdriver.h |4
2 files changed, 7 insertions(+)
diff
Add the contstant for v2.90a and v3.00a dwc3 IP detection
Signed-off-by: Sneeker Yeh sneeker@tw.fujitsu.com
---
drivers/usb/dwc3/core.h |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/usb/dwc3/core.h b/drivers/usb/dwc3/core.h
index 4bb9aa6..46f9f9a 100644
---
This issue is defined by a three-way race at disconnect, between
1) Class driver interrupt endpoint resheduling attempts if the ISR gave an ep
error event due to device detach (it would try 3 times)
2) Disconnect interrupt on PORTSC_CSC, which is cleared by hub thread
asynchronously
3) The
These patches add support for XHCI compliant Host controller found
on Fujitsu Socs, and are based on http://lwn.net/Articles/629162/
The first patch is to add Fujitsu glue layer of Synopsis DesignWare USB3 driver
and last four patch is about quirk implementation of errata in Synopsis
DesignWare
On 23 January 2015 at 17:47, Tony Lindgren t...@atomide.com wrote:
That's interesting info thanks :) Yeah it seems dm814x was done after
dm816x and that clears at least some of the clockdomain confusion
that I though was TRM copy-paste issue.
Well it is in some sense still a copy-paste issue
On Sat, Jan 24, 2015 at 04:23:42PM -0600, Felipe Balbi wrote:
yeah, I'll try a few older kernels, also see if I can reproduce on other
boards.
Perf works for me with CONFIG_FRAME_POINTER=y, but that's only for kernel
space, and for userspace where the programs have been built for ARM mode
with
On Sat, Jan 24, 2015 at 01:00:00PM +0100, Pali Rohár wrote:
Another regression for DT setup (which does not occur for board code):
omap_hsmmc driver does not export slot_name sysfs entry because
it not supported by DT yet. Entry slot_name is used by userspace
application to determinate if
Hi,
On Fri, Jan 23, 2015 at 02:15:56PM +0100, Pali Rohár wrote:
I'm getting these two errors when booting DT linux v3.19-rc5 in n900 qemu:
[0.309234] device-tree: Duplicate name in onenand@0,0, renamed to #1
[0.309417] device-tree: Duplicate name in onenand@0,0, renamed to #2
[
Hi,
On 01/22/2015 03:40 AM, Olof Johansson wrote:
Hi,
On Thu, Nov 27, 2014 at 2:41 AM, Peter Ujfalusi peter.ujfal...@ti.com wrote:
include/linux/platform_data/ is not a correct place to keep the API
definitions for edma, it is meant to be only for the pdata for the device.
Clean up this by
On Sat 2015-01-24 13:00:00, Pali Rohár wrote:
On Thursday 15 January 2015 15:25:36 Sebastian Reichel wrote:
On Tue, Jan 13, 2015 at 12:42:20PM -0800, Tony Lindgren wrote:
* Arnd Bergmann a...@arndb.de [150113 12:27]:
On Tuesday 13 January 2015 09:57:41 Tony Lindgren wrote:
It seems
On Sat 2015-01-24 23:08:00, Arnd Bergmann wrote:
On Saturday 24 January 2015 13:00:00 Pali Rohár wrote:
Another regression for DT setup (which does not occur for board code):
omap_hsmmc driver does not export slot_name sysfs entry because
it not supported by DT yet. Entry slot_name is
On Sun, Jan 25, 2015 at 10:22:58PM +0100, Pavel Machek wrote:
Another regression for DT setup (which does not occur for board code):
omap_hsmmc driver does not export slot_name sysfs entry because
it not supported by DT yet. Entry slot_name is used by userspace
application to
Hi
the references below are from SPRUHL7
On Fri, 23 Jan 2015, Felipe Balbi wrote:
Without hwmod data for DebugSS, performance monitors
have no chance of running on AM43xx devices.
Signed-off-by: Felipe Balbi ba...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_43xx_data.c | 40
Hi
On Sun, 25 Jan 2015, Lad, Prabhakar wrote:
From: Benoit Parrot bpar...@ti.com
this patch adds VPFE HWMOD data for AM43xx.
Signed-off-by: Benoit Parrot bpar...@ti.com
Signed-off-by: Darren Etheridge detheri...@ti.com
Signed-off-by: Felipe Balbi ba...@ti.com
Signed-off-by: Lad,
hw-assisted flow control support was added to the serial core
in v3.8 with commits,
dba05832cbe4f (SERIAL: core: add hardware assisted h/w flow control support)
2cbacafd7af0f (SERIAL: core: add hardware assisted s/w flow control support)
9aba8d5b01119 (SERIAL: core: add throttle/unthrottle
Hi Greg,
This patch series re-implements hw-assisted flow control support,
(aka autoRTS, autoCTS and auto XON/XOFF) in the serial core.
Out-of-tree driver maintainers please note this changes the UART
driver interface for flow control steering.
This series separates mode handling from the
tty_set_termios() is an internal helper intended for file scope use.
UART drivers which are capable of driving the RTS pin must
properly handle the tiocmset() method, regardless of termios settings.
A failure to do so is a UART driver bug and should be fixed there.
Do not use this interface to
The OMAP UART ignores MCR[1] (ie., RTS) when in autoRTS mode. This
makes it impossible for either the serial core or userspace to
manually flow control the sender.
Disable autoRTS mode when RTS is lowered and restore the previous
mode when RTS is raised.
Signed-off-by: Peter Hurley
Commit 88838d3112702 (serial: omap_8250: Fix RTS handling) fixed
RTS pin control when in autoRTS mode.
New support added in serial: core: Rework hw-assisted flow control support
enables a much simpler approach; rather than masking out autoRTS
whenever writing the EFR register, use the UPSTAT_*
From: Benoit Parrot bpar...@ti.com
this patch adds VPFE HWMOD data for AM43xx.
Signed-off-by: Benoit Parrot bpar...@ti.com
Signed-off-by: Darren Etheridge detheri...@ti.com
Signed-off-by: Felipe Balbi ba...@ti.com
Signed-off-by: Lad, Prabhakar prabhakar.cse...@gmail.com
---
Hi Paul,
You were
Hi Peter,
tty_set_termios() is an internal helper intended for file scope use.
UART drivers which are capable of driving the RTS pin must
properly handle the tiocmset() method, regardless of termios settings.
A failure to do so is a UART driver bug and should be fixed there.
Do not use
23 matches
Mail list logo
