Don't complain on -EPROBE_DEFER when no PHY found, the driver
probe will be retried later.
Signed-off-by: Ladislav Michl
Acked-by: Tony Lindgren
Acked-by: Roger Quadros
---
Changes:
- v2: None, just added Tony's ack
- v3: Fixed commit message typo spotted by Jaejoong Kim, added Roger's ack
Hi,
My environment (R-Car H3) outputs the following error when I disconnected
a usb 3.0 SSD device from the xhci host controller.
[ 267.755777] xhci-hcd ee00.usb: Cannot set link state.
[ 267.761188] usb usb8-port1: cannot disable (err = -32)
[ 267.772166] usb 8-1: USB disconnect, device n
This devices drops random bytes from messages if you talk to it
too fast.
Signed-off-by:
CC: sta...@vger.kernel.org
---
drivers/usb/class/cdc-acm.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/usb/class/cdc-acm.c b/drivers/usb/class/cdc-acm.c
index 8e0636c963a7..349aac4472bd 10
Hi Roger,
On 1/17/2018 4:16 PM, Roger Quadros wrote:
> Manu,
>
> On 16/01/18 08:26, Manu Gautam wrote:
>
[snip]
> After these changes applied, I could get suspend/resume working properly on
> dra7x-evm
> for host, device and dual-role cases.
>
Thanks Roger. I will incorporate these changes as
Commit 689bf72c6e0d ("usb: dwc3: Don't reinitialize core during
host bus-suspend/resume") updated suspend/resume routines to not
power_off and reinit PHYs/core for host mode.
It broke platforms that rely on DWC3 core to power_off PHYs to
enter low power state on system suspend.
Perform dwc3_core_e
On 18/01/18 13:24, Manu Gautam wrote:
> Commit 689bf72c6e0d ("usb: dwc3: Don't reinitialize core during
> host bus-suspend/resume") updated suspend/resume routines to not
> power_off and reinit PHYs/core for host mode.
> It broke platforms that rely on DWC3 core to power_off PHYs to
> enter low pow
Dear Gerg,
Many thanks to your comment.
I've checked all of them and here are some questions need your help.
> +Example:
> +rt1711h@4e {
> +status = "ok";
> +compatible = "richtek,typec_rt1711h";
> +reg = <0x4e>;
> +rt,intr_gpio = <&gpio26 0 0x0>;
> +rt,name = "rt1711h";
> +rt,port_type = <2>
On Wed, Jan 17, 2018 at 12:21:49PM -0800, Matthew Wilcox wrote:
> From: Matthew Wilcox
>
> The reada_lock in struct btrfs_device was only initialised, and not
> actually used. That's good because there's another lock also called
> reada_lock in the btrfs_fs_info that was quite heavily used. Rem
From: Hayes Wang
Date: Thu, 18 Jan 2018 03:04:08 +
> [...]
>> > r8153 on Dell TB15/16 dock corrupts rx packets.
>> >
>> > This change is suggested by Realtek. They guess that the XHCI
>> > controller doesn't have enough buffer, and their guesswork is correct,
>> > once the RX aggregation gets
On 18.01.2018 09:27, Tung Vuong Nguyen wrote:
On Tue, Jan 16, 2018 at 9:50 PM, Mathias Nyman
wrote:
Hi, Sorry about the delay
On 04.01.2018 07:17, Thang Q. Nguyen wrote:
Hi,
On Sat, Dec 16, 2017 at 10:45 AM, Thang Q. Nguyen wrote:
From: Tung Nguyen
Currently, hcd->shared_hcd always c
On Thu, 18 Jan 2018, Ladislav Michl wrote:
> Don't complain on -EPROBE_DEFER when no PHY found, the driver
> probe will be retried later.
>
> Signed-off-by: Ladislav Michl
> Acked-by: Tony Lindgren
> Acked-by: Roger Quadros
> ---
> Changes:
> - v2: None, just added Tony's ack
> - v3: Fixed
My laptop just died horribly and I'm picking through the pieces.
I'm running Debian testing, and it was kernel 4.13.0-1-amd64 #1 Debian
4.13.13-1 although now I've rebooted to 4.14.0-2-amd64 #1 SMP Debian
4.14.7-1
It seems that the original cause of the problem was usbfs going mad and
spraying th
On 17.01.2018 18:46, Michael Tretter wrote:
Hello,
I am using a Magewell XI100DUSB-HDMI frame grabber which by itself works
fine. However, I get a "Not enough bandwidth for new device state."
error for any other USB device that is plugged after the frame grabber.
This error is caused by the xHC
On Wed, Jan 17, 2018 at 12:20:24PM -0800, Matthew Wilcox wrote:
> From: Matthew Wilcox
>
> This version of the XArray has no known bugs.
I've booted this patchset on 2 boxes, both had random problems during
boot. On one I was not able to diagnose what went wrong. On the other
one the system boot
On Thu, Jan 18, 2018 at 05:07:50PM +0100, David Sterba wrote:
> On Wed, Jan 17, 2018 at 12:20:24PM -0800, Matthew Wilcox wrote:
> > From: Matthew Wilcox
> >
> > This version of the XArray has no known bugs.
>
> I've booted this patchset on 2 boxes, both had random problems during
> boot. On one
2018-01-17 22:46 GMT+01:00 Brian Norris :
> On Fri, Jan 12, 2018 at 12:00:16PM +0800, William Wu wrote:
>> The dwc3_core_init() gets the PHYs and initializes the PHYs with
>> the usb_phy_init() and phy_init() functions before initializing
>> core, and power on the PHYs after core initialization is
> On 18 Jan 2018, at 10:50 PM, David Miller wrote:
>
> From: Hayes Wang
> Date: Thu, 18 Jan 2018 03:04:08 +
>
>> [...]
r8153 on Dell TB15/16 dock corrupts rx packets.
This change is suggested by Realtek. They guess that the XHCI
controller doesn't have enough buffer,
On Thu, Jan 18, 2018 at 08:48:43AM -0800, Matthew Wilcox wrote:
> Thank you! I shall attempt to debug. Was this with a btrfs root
> filesystem? I'm most suspicious of those patches right now, since they've
> received next to no testing. I'm going to put together a smaller patchset
> which just
On Thu, Jan 18, 2018 at 10:18:41AM -0500, Alan Stern wrote:
> On Thu, 18 Jan 2018, Ladislav Michl wrote:
>
> > Don't complain on -EPROBE_DEFER when no PHY found, the driver
> > probe will be retried later.
> >
> > Signed-off-by: Ladislav Michl
> > Acked-by: Tony Lindgren
> > Acked-by: Roger Qua
On Thu, Jan 18, 2018 at 05:56:12PM +0100, David Sterba wrote:
> On Thu, Jan 18, 2018 at 08:48:43AM -0800, Matthew Wilcox wrote:
> > Thank you! I shall attempt to debug. Was this with a btrfs root
> > filesystem? I'm most suspicious of those patches right now, since they've
> > received next to n
> -Original Message-
> From: Kai Heng Feng [mailto:kai.heng.f...@canonical.com]
> Sent: Thursday, January 18, 2018 10:57 AM
> To: David Miller
> Cc: Hayes Wang ; gre...@linuxfoundation.org; linux-
> u...@vger.kernel.org; net...@vger.kernel.org; linux-ker...@vger.kernel.org;
> Limonciello,
The USB_PHY_CTRL_FUNC is used specific for OTG port as described
in user manual. EVDO need to be set only for index 0 that
correspond to OTG port
Signed-off-by: Michael Trimarchi
---
Changes v1->v2
- %s/corrispond/correspond/
---
drivers/usb/chipidea/usbmisc_imx.c | 3 +++
1 file changed
The register write can be done outside the if and else condition
Signed-off-by: Michael Trimarchi
---
Changes v1->v2:
- None
---
drivers/usb/chipidea/usbmisc_imx.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/usb/chipidea/usbmisc_imx.c
b/drivers/usb/chip
evdo bit can be set or reset. We can not trust evdo bit
status after bootloader stage
Signed-off-by: Michael Trimarchi
---
Changes v1->v2:
- None
---
drivers/usb/chipidea/usbmisc_imx.c | 20
1 file changed, 12 insertions(+), 8 deletions(-)
diff --git a/drivers/usb/c
On Thu, 18 Jan 2018, Ladislav Michl wrote:
> On Thu, Jan 18, 2018 at 10:18:41AM -0500, Alan Stern wrote:
> > On Thu, 18 Jan 2018, Ladislav Michl wrote:
> >
> > > Don't complain on -EPROBE_DEFER when no PHY found, the driver
> > > probe will be retried later.
> > >
> > > Signed-off-by: Ladislav M
On Mon, Jan 15, 2018 at 6:06 PM, Benjamin Herrenschmidt
wrote:
> Commit 4642d34a439f80e16af0d56ed6258a33abae257a
> "usb/uhci: Add support for Aspeed BMC SoCs" added
> support for a new #ports property, along with
> Aspeed specific compatible strings. This adds
> documentation for them.
>
> Signed-
Don't complain on -EPROBE_DEFER when no PHY found, the driver
probe will be retried later.
Signed-off-by: Ladislav Michl
Acked-by: Tony Lindgren
Acked-by: Roger Quadros
Acked-by: Alan Stern
---
Changes:
- v2: None, just added Tony's ack
- v3: Fixed commit message typo spotted by Jaejoong Ki
Simplify return logic and avoid unnecessary variable assignment.
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/gadget/legacy/ncm.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/usb/gadget/legacy/ncm.c b/drivers/usb/gadget/legacy/ncm.c
index fcee1ee0..8465
Commit 2f2d0088eb93
("usbip: prevent vhci_hcd driver from leaking a socket pointer address")
in the /sys/devices/platform/vhci_hcd/status.
Fix the header and field alignment to reflect the changes and make it
easier to read.
Signed-off-by: Shuah Khan
---
drivers/usb/usbip/vhci_sysfs.c | 12
Commit dde634057da7 ("xhci: Fix use-after-free in xhci debugfs") causes a
null pointer dereference while fixing xhci-debugfs usage of ring pointers
that were freed during hibernate.
The fix passed addresses to ring pointers instead, but forgot to do this
change for the xhci_ring_trb_show function.
Hi
> -Original Message-
> From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb-
> ow...@vger.kernel.org] On Behalf Of ShuFanLee
> Sent: Wednesday, January 10, 2018 2:59 PM
> To: heikki.kroge...@linux.intel.com
> Cc: cy_hu...@richtek.com; shufan_...@richtek.com; linux-
> ker...@vger.kerne
Hi Jun,
For now, RT1711H is not fully compatible with TCPCI. So the existing tcpci.c
may not work for it.
Best Regards,
*
Shu-Fan Lee
Richtek Technology Corporation
TEL: +886-3-5526789 #2359
FAX: +886-3-5526612
*
-Original Message---
>
> Signed-off-by: Michael Trimarchi
> ---
> Changes v1->v2:
> - None
> ---
> drivers/usb/chipidea/usbmisc_imx.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/usb/chipidea/usbmisc_imx.c
> b/drivers/usb/chipidea/usbmisc_imx.c
> index 1f47ef6..34ad5
On 19.01.2018 04:13, Zhengjun Xing wrote:
Commit dde634057da7 ("xhci: Fix use-after-free in xhci debugfs") causes a
null pointer dereference while fixing xhci-debugfs usage of ring pointers
that were freed during hibernate.
The fix passed addresses to ring pointers instead, but forgot to do this
34 matches
Mail list logo
