Hello.
On 08/20/2016 11:32 PM, Randy Li wrote:
On the rk3288 USB host-only port (the one that's not the OTG-enabled
port) the PHY can get into a bad state when a wakeup is asserted (not
just a wakeup from full system suspend but also a wakeup from
autosuspend).
We can get the PHY out of its
It is a hardware bug in RK3288, the only way to solve it is to
reset the phy.
Signed-off-by: Randy Li
---
drivers/phy/phy-rockchip-usb.c | 20
1 file changed, 20 insertions(+)
diff --git a/drivers/phy/phy-rockchip-usb.c b/drivers/phy/phy-rockchip-usb.c
The "host1" port (AKA the dwc2 port that isn't the OTG port) on rk3288
has a hardware errata that causes everything to get confused when we get
a remote wakeup. We'll use the reset that's in the CRU to reset the
port when it's in a bad state.
Note that we add the reset to both dwc2 controllers
The only use for this is for solving a hardware design problem in
usb of Rockchip RK3288.
Signed-off-by: Randy Li
---
include/linux/phy/phy.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/phy/phy.h b/include/linux/phy/phy.h
index f08b672..4d34607 100644
On the rk3288 USB host-only port (the one that's not the OTG-enabled
port) the PHY can get into a bad state when a wakeup is asserted (not
just a wakeup from full system suspend but also a wakeup from
autosuspend).
We can get the PHY out of its bad state by asserting its "port reset",
but
Hello All:
This version would move reset into phy. I wanted to implement a hard
code version but I meet some problem with ioremap reset controller,
in order to keep my word, I offer this version this time.
Randy Li (4):
phy: Add reset callback
phy: rockchip-usb: use rockchip_usb_phy_reset to
I've just checked 4.8-rc2 - same behaviour.
2016-08-18 16:31 GMT+03:00 Matwey V. Kornilov :
> Any ideas?
>
> 2016-08-04 23:08 GMT+03:00 Matwey V. Kornilov :
>> When DMA is not used, I see the same behavior: lots of zero-length
>> packages received.
>>
>> Can
Fixes the following sparse warning:
drivers/usb/host/xhci-ring.c:608:6: warning:
symbol 'xhci_unmap_td_bounce_buffer' was not declared. Should it be static?
Signed-off-by: Wei Yongjun
---
drivers/usb/host/xhci-ring.c | 4 ++--
1 file changed, 2 insertions(+), 2
Hello.
On 8/20/2016 11:19 AM, Aleksandr Makarov wrote:
From: Aleksandr Makarov
USB: serial: option: add WeTelecom WM-D200
Don't duplicate the subject in the patch description please.
Add support for WeTelecom WM-D200.
T: Bus=03 Lev=01 Prnt=01 Port=01
On Sat, Aug 20, 2016 at 01:29:41PM +0300, Aleksandr Makarov wrote:
> From: Aleksandr Makarov
>
> USB: serial: option: add WeTelecom WM-D200
This does not belong in the commit message (mail body).
> Add support for WeTelecom WM-D200.
>
> T: Bus=03 Lev=01 Prnt=01
Hi John,
on bcm2835 in OTG mode the USB host function broken (USB devices don't
enumerate) with the following settings:
CONFIG_USB=y
CONFIG_USB_OTG=y
CONFIG_USB_DWC2=y
CONFIG_USB_DWC2_DUAL_ROLE=y
CONFIG_USB_PHY=y
CONFIG_NOP_USB_XCEIV=y
CONFIG_USB_GADGET=y
CONFIG_USB_ZERO=y
and DT don't provide
[ +CC: Karl and Konstantin ]
On Fri, Jul 22, 2016 at 11:33:15AM +0100, Martyn Welch wrote:
> This patch adds support for the GPIO found on the CP2105. Unlike the GPIO
> provided by some of the other devices supported by the cp210x driver, the
> GPIO on the CP2015 is muxed on pins otherwise used
>> Another example:
>>> 00 00 00 00 00 00 00 01
>> ...
>>> 01 00 00 00 00 00 00 00
>> ...
>>> 00 01 00 00 00 00 00 00
>> ...
>>> 00 00 01 00 00 00 00 00
>> after a random number of times, while usbmon shows the usb payload
>> "00 00 00 00 00 00 00 01".
>
> Hi, how many bytes does read() return?
>
USB: serial: option: add WeTelecom WM-D200
Add support for WeTelecom WM-D200.
T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 4 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=22de ProdID=6801 Rev=00.00
S: Manufacturer=WeTelecom Incorporated
S:
On Sat, 2016-08-20 at 05:40 +0200, Julio Guerra wrote:
> Another example:
> > 00 00 00 00 00 00 00 01
> ...
> > 01 00 00 00 00 00 00 00
> ...
> > 00 01 00 00 00 00 00 00
> ...
> > 00 00 01 00 00 00 00 00
> after a random number of times, while usbmon shows the usb payload
> "00 00 00 00 00 00 00
From: Aleksandr Makarov
USB: serial: option: add WeTelecom WM-D200
Add support for WeTelecom WM-D200.
T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 4 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=22de ProdID=6801
On Sat, Aug 20, 2016 at 11:19:37AM +0300, Aleksandr Makarov wrote:
> From: Aleksandr Makarov
>
> USB: serial: option: add WeTelecom WM-D200
>
> Add support for WeTelecom WM-D200.
>
> T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 4 Spd=12 MxCh= 0
> D: Ver=
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I am not sure if the logs ever reached the list. I've uploaded the logs here [1]
for convenience.
[1] https://people.debian.org/~rrs/tmp/usb-xhci-dmesg.txt.gz
On Fri, 2016-08-19 at 15:56 +0530, Ritesh Raj Sarraf wrote:
> Hello Mathia,
>
> On
From: Aleksandr Makarov
USB: serial: option: add WeTelecom WM-D200
Add support for WeTelecom WM-D200.
T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 4 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=22de ProdID=6801
19 matches
Mail list logo