Re: [PATCH] usb: typec: tcpm: Try PD-2.0 if sink does not respond to 3.0 source-caps

Hi, On 15-03-19 17:53, Guenter Roeck wrote: On Fri, Mar 15, 2019 at 05:43:05PM +0100, Hans de Goede wrote: Hi, On 3/15/19 3:57 PM, Guenter Roeck wrote: On Fri, Mar 15, 2019 at 03:42:19PM +0100, Hans de Goede wrote: PD 2.0 sinks are supposed to accept src-capabilities with a 3.0 header and si

Re: Problem with USB2 devices connected to a hub

On 15.03.19 17:04, Georg Chini wrote: On 15.03.19 15:48, Mathias Nyman wrote: On 14.3.2019 20.39, Georg Chini wrote: On 14.03.19 15:00, Mathias Nyman wrote: On 14.3.2019 14.38, Georg Chini wrote: Hello, I have a problem with multiple USB2 devices. After purchasing a new motherboard, some US

[PATCH v2] usb: typec: tcpm: Try PD-2.0 if sink does not respond to 3.0 source-caps

PD 2.0 sinks are supposed to accept src-capabilities with a 3.0 header and simply ignore any src PDOs which the sink does not understand such as PPS but some 2.0 sinks instead ignore the entire PD_DATA_SOURCE_CAP message, causing contract negotiation to fail. This commit fixes such sinks not worki

g_dbgp + u_serial: WARNING when unloading g_dbgp module

Linux v5.0-11053-gebc551f2b8f9 of March 12, on x86_64: with CONFIG_USB_G_DBGP=m # CONFIG_USB_G_DBGP_PRINTK is not set CONFIG_USB_G_DBGP_SERIAL=y CONFIG_USB_U_SERIAL=m Loading g_dbgp module and then unloading it causes: WARNING: CPU: 0 PID: 24523 at ../drivers/usb/gadget/function/u_serial.c:1195

Re: [PATCH v2] usb: typec: tcpm: Try PD-2.0 if sink does not respond to 3.0 source-caps

On Sat, Mar 16, 2019 at 04:57:12PM +0100, Hans de Goede wrote: > PD 2.0 sinks are supposed to accept src-capabilities with a 3.0 header and > simply ignore any src PDOs which the sink does not understand such as PPS > but some 2.0 sinks instead ignore the entire PD_DATA_SOURCE_CAP message, > causin