Re: [PATCH 2/4] usb: dwc3: add dwc3 glue layer for UniPhier SoCs

Hi, On Thu, 25 Jan 2018 11:09:30 +0900 wrote: > Hello Felipe, > > On Wed, 24 Jan 2018 14:58:12 +0200 wrote: > > > > > Hi, > > > > Kunihiko Hayashi writes: > > > Hello Felipe, > > > > > > Thank you for your

Darlehen Geld für Einzelpersonen und Fachleute in weniger als 72 Stunden

Hallo, Sind Sie in einer schwierigen Situation, für die Sie sich für ein Darlehen suchen? Benötigen Sie eine Finanzierung, um eine Schuld zu begleichen oder eine Aktivität zu finanzieren? Haben Sie einen Verbraucherkredit, eine Hypothek, einen persönlichen Kredit, eine Hypothek, Investition

Re: [PATCH 2/2] usb: chipidea: imx: Fix ULPI on imx53

On Wed, Jan 24, 2018 at 06:14:39PM +0100, Sebastian Reichel wrote: > Traditionally, PORTSC should be set before initializing ULPI phys. But > setting PORTSC before powering on the phy results in a kernel freeze > on imx53 based GE PPD. As a workaround this initializes the phy early > in the imx

Re: USB-C Devices only show up if connected at boot

On Thu, Jan 25, 2018 at 10:20:02PM +, Mike Lothian wrote: > I've just tried this and the USB-C device was detected :D This is the > first time it's ever been detected after boot > > 02:00.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge > [Alpine Ridge 2C 2015] >Kernel

Re: USB-C Devices only show up if connected at boot

On Thu, Jan 25, 2018 at 09:31:08PM +, Mike Lothian wrote: > I've tried with and without those being set, neither help, having > CONFIG_HOTPLUG_PCI_ACPI=y on causes my NVMe drive to disappear after > suspend You *must* have those set, othewise the xHCI will not work. Can you do so that you

Re: [PATCH v3 2/2] usb/gadget: Add driver for Aspeed SoC virtual hub

On Fri, Jan 26, 2018 at 10:58:56AM +1100, Benjamin Herrenschmidt wrote: On Wed, 2018-01-24 at 11:30 +0800, kbuild test robot wrote: Hi Benjamin, I love your patch! Perhaps something to improve: [auto build test WARNING on balbi-usb/next] [also build test WARNING on v4.15-rc9 next-20180119]

[resend] Questions about "usb usb8-port1: cannot disable (err = -32)"

I resent this email with adding Mathias, Alan and Greg as CC. -Original Message- From: Yoshihiro Shimoda, Sent: Thursday, January 18, 2018 6:03 PM To: linux-usb@vger.kernel.org Subject: Questions about "usb usb8-port1: cannot disable (err = -32)" Hi, My environment (R-Car H3) outputs

Re: [PATCH v3 2/2] usb/gadget: Add driver for Aspeed SoC virtual hub

On Wed, 2018-01-24 at 11:30 +0800, kbuild test robot wrote: > Hi Benjamin, > > I love your patch! Perhaps something to improve: > > [auto build test WARNING on balbi-usb/next] > [also build test WARNING on v4.15-rc9 next-20180119] > [if your patch is applied to the wrong git tree, please drop us

[PATCH v4 2/2] usb/gadget: Add driver for Aspeed SoC virtual hub

The Aspeed BMC SoCs support a "virtual hub" function. It provides some HW support for a top-level USB2 hub behind which sit 5 gadget "ports". This driver adds support for the full functionality, emulating the hub standard requests and exposing 5 UDC gadget drivers corresponding to the ports. The

[PATCH v4 1/2] usb/gadget: Add an EP dispose() callback for EP lifetime tracking

Some UDC may want to allocate endpoints dynamically, either because the HW supports an arbitrary large number or because (like the Aspeed BMC SoCs), the pool of HW endpoints is shared between multiple gadgets. The allocation side can be done rather easily using the existing match_ep() UDC hook.

Re: USB-C Devices only show up if connected at boot

On 25 January 2018 at 21:31, Mike Lothian wrote: > > Hi > > I've tried with and without those being set, neither help, having > CONFIG_HOTPLUG_PCI_ACPI=y on causes my NVMe drive to disappear after > suspend > > I'll switch back into windows and check I've the latest firmware

Re: USB-C Devices only show up if connected at boot

On Thu, 25 Jan 2018 at 10:52 Mika Westerberg wrote: > > On Thu, Jan 25, 2018 at 12:35:49PM +0200, Heikki Krogerus wrote: > > +Mika > > > > On Tue, Jan 23, 2018 at 05:43:27PM +, Mike Lothian wrote: > > > On Tue, 23 Jan 2018 at 17:30 Greg KH

Re: [PATCH 2/4] usb: dwc3: add dwc3 glue layer for UniPhier SoCs

Hi Kunihiko, Thank you for the patch! Yet something to improve: [auto build test ERROR on robh/for-next] [also build test ERROR on v4.15-rc9 next-20180119] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [RFC/RFT usb-next v1 1/6] usb: mtu3: remove custom USB PHY handling

Hi, On Thu, Jan 25, 2018 at 3:47 AM, Chunfeng Yun wrote: > Hi, > > On Thu, 2018-01-25 at 01:16 +0100, Martin Blumenstingl wrote: >> The new PHY wrapper is now wired up in the core HCD code. This means >> that PHYs are now controlled (initialized, enabled, disabled,

[PATCH 4.4 0/4] Backport missing sccurity and deadlock fix

As I started backporting security fixes, I found a deadlock bug that was fixed in a later release. This patch series contains backports for all these problems. Andrew Goodbody (1): usb: usbip: Fix possible deadlocks reported by lockdep Shuah Khan (3): usbip: fix stub_rx: get_pipe() to

[PATCH 4.4 1/4] usb: usbip: Fix possible deadlocks reported by lockdep

From: Andrew Goodbody Upstream commit 21619792d1ec ("usb: usbip: Fix possible deadlocks reported by lockdep") Change spin_lock calls to spin_lock_irqsave to prevent attmpted recursive lock taking in interrupt context. This patch fixes Bug 109351

[PATCH 4.4 2/4] usbip: fix stub_rx: get_pipe() to validate endpoint number

Upstream commit 635f545a7e8b ("usbip: fix stub_rx: get_pipe() to validate endpoint number") get_pipe() routine doesn't validate the input endpoint number and uses to reference ep_in and ep_out arrays. Invalid endpoint number can trigger BUG(). Range check the epnum and returning error instead of

[PATCH 4.4 4/4] usbip: prevent leaking socket pointer address in messages

Upstream commit 90120d15f4c3 ("usbip: prevent leaking socket pointer address in messages") usbip driver is leaking socket pointer address in messages. Remove the messages that aren't useful and print sockfd in the ones that are useful for debugging. Signed-off-by: Shuah Khan

[PATCH 4.4 3/4] usbip: fix stub_rx: harden CMD_SUBMIT path to handle malicious input

Upstream commit c6688ef9f297 ("usbip: fix stub_rx: harden CMD_SUBMIT path to handle malicious input") Harden CMD_SUBMIT path to handle malicious input that could trigger large memory allocations. Add checks to validate transfer_buffer_length and number_of_packets to protect against bad input

Re: [PATCH 1/2] usb: misc: xapea00x: add driver for Xaptum ENF Access Card

On Thu, Jan 25, 2018 at 10:34 AM, David R. Bild wrote: > On Thu, Jan 11, 2018 at 4:27 AM, Oliver Neukum wrote: >> >> Am Mittwoch, den 10.01.2018, 10:58 -0600 schrieb David R. Bild : > >> > +static void xapea00x_tpm_probe(struct work_struct *work) >> > +{

uvcvideo: Failed to resubmit video URB (-1).

Hello, Open bug in bugzilla.kernel.org https://bugzilla.kernel.org/show_bug.cgi?id=198575 dmesg: [ 6529.509530] uvcvideo: Failed to resubmit video URB (-1). Regards, -- Cristian [0.00] microcode: microcode updated early to revision 0x29, date = 2013-06-12 [0.00] Linux version

Re: [PATCH 1/2] usb: misc: xapea00x: add driver for Xaptum ENF Access Card

On Thu, Jan 11, 2018 at 4:27 AM, Oliver Neukum wrote: > > Am Mittwoch, den 10.01.2018, 10:58 -0600 schrieb David R. Bild : > > This commit adds a driver for the Xaptum ENF Access Card, a TPM2.0 > > hardware module for authenticating IoT devices and gateways. > > Thanks for the

Re: [PATCHv2] musb_host: fix lockup on rxcsr_h_error

Maxim, On Thu, Jan 25, 2018 at 07:24:02PM +0300, Maxim Uvarov wrote: > [1] says that issue is with back ported driver to 3.12.10. Can the > latest kernel be tested on the same hw? Agreed that it should be tested with the latest kernel. But my concern now is if stopping scheduling urbs on errors

Re: MUSB patch (don't start next rx urb if current one failed)

Hi Bin, thanks. I have reverted commit https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/drivers/usb/musb/musb_host.c?id=dbac5d07d13e330e6706813c9fde477140fb5d80 and communication with both RT2800 and SMSC9500 was much more stable, but we still had less frequent

Re: [PATCHv2] musb_host: fix lockup on rxcsr_h_error

[1] says that issue is with back ported driver to 3.12.10. Can the latest kernel be tested on the same hw? Maxim. 2018-01-25 18:45 GMT+03:00 Bin Liu : > Hi Yegor and Max, > > On Tue, May 03, 2016 at 04:25:58PM +0200, Yegor Yefremov wrote: >> On Tue, May 3, 2016 at 3:48 PM, Bin Liu

Re: [PATCH 2/2] usb: dwc3: drd: Fix lock-up on ID change during system suspend/resume

Hi, On 24/01/18 14:19, Roger Quadros wrote: > On 23/01/18 14:41, Roger Quadros wrote: >> Hi Manu, >> >> On 23/01/18 05:45, Manu Gautam wrote: >>> Hi, >>> >>> >>> On 1/22/2018 6:31 PM, Roger Quadros wrote: Adding/removing host/gadget controller before .pm_complete() causes a lock-up.

Re: [RFC/RFT usb-next v1 3/6] usb: host: ehci-platform: remove custom USB PHY handling

On Thu, 25 Jan 2018, Martin Blumenstingl wrote: > The new PHY wrapper is now wired up in the core HCD code. This means > that PHYs are now controlled (initialized, enabled, disabled, exited) > without requiring any host-driver specific code. > Remove the custom USB PHY handling from the

Re: [BUG] SD card reader disappears after suspend

On Thu, 25 Jan 2018, Samuel Sadok wrote: > 2018-01-23 17:31 GMT+01:00 Alan Stern : > > On Tue, 23 Jan 2018, Samuel Sadok wrote: > > > >> Thanks Alan, > >> > >> While I was at it I also enabled debug logs for xhci_hcd and xhci_pci. > >> > >> $ echo module usbcore =p >

Re: Tracepoints

Hi, On Thu, Jan 25, 2018 at 10:13:02AM -0500, Tyler Howell wrote: > Hey Bin, > > Thanks for replying back. I'm not sure, but it might have been because I > compiled the musb as a module (and hadn't loaded it!). I re-configured my > kernel and was able to get the musb events to show up under >

Re: [PATCHv2] musb_host: fix lockup on rxcsr_h_error

Hi Yegor and Max, On Tue, May 03, 2016 at 04:25:58PM +0200, Yegor Yefremov wrote: > On Tue, May 3, 2016 at 3:48 PM, Bin Liu wrote: > > Hi, > > > > On Tue, May 03, 2016 at 12:03:52PM +0200, Yegor Yefremov wrote: > >> On Thu, Apr 28, 2016 at 4:37 PM, Bin Liu wrote: >

Re: Tracepoints

+ cc:linux-usb Hi Tyler, On Wed, Jan 24, 2018 at 05:29:16PM -0500, Tyler Howell wrote: > Hey Bin, > > I've looking to learn how the musb system works, but for the life of me > can't figure out how to enable the tracepoints for my kernel. Is there a > specific kernel config I need to enable for

Re: MUSB patch (don't start next rx urb if current one failed)

+ cc:linux-usb Hi Tomas, It is always a good idea to cc linux-usb list when sending emails to an individual. (otherwise, for example in my setup the emails go to the Junk folder if a mailing list is not in to/cc.) On Thu, Jan 18, 2018 at 03:47:12PM +0100, Tomas Paukrt wrote: > Hi Bin, > > I

Re: [BUG] SD card reader disappears after suspend

2018-01-23 17:31 GMT+01:00 Alan Stern : > On Tue, 23 Jan 2018, Samuel Sadok wrote: > >> Thanks Alan, >> >> While I was at it I also enabled debug logs for xhci_hcd and xhci_pci. >> >> $ echo module usbcore =p > /sys/kernel/debug/dynamic_debug/control >> $ echo module

Re: USB-C Devices only show up if connected at boot

On Thu, Jan 25, 2018 at 12:35:49PM +0200, Heikki Krogerus wrote: > +Mika > > On Tue, Jan 23, 2018 at 05:43:27PM +, Mike Lothian wrote: > > On Tue, 23 Jan 2018 at 17:30 Greg KH wrote: > > > > > > On Tue, Jan 23, 2018 at 05:12:03PM +, Mike Lothian wrote: > > > >

Re: USB-C Devices only show up if connected at boot

+Mika On Tue, Jan 23, 2018 at 05:43:27PM +, Mike Lothian wrote: > On Tue, 23 Jan 2018 at 17:30 Greg KH wrote: > > > > On Tue, Jan 23, 2018 at 05:12:03PM +, Mike Lothian wrote: > > > Hi > > > > > > I raised https://bugzilla.kernel.org/show_bug.cgi?id=198557 but

Re: Request to add new VID/PID to PL2303 driver

On Thu, Jan 25, 2018 at 09:37:16AM +, Chu.Mike [朱堅宜] wrote: > Thanks, guys! Do you know what kernel version will I find this addition? It will get merged into Linus's tree in the 4.16-rc1 merge window, and then get backported to all of the stable kernel trees within a week or so after that

Re: [PATCH 3/3] firmware: Fix up docs referring to FIRMWARE_IN_KERNEL

On Wed, Jan 24, 2018 at 08:41:30AM +0100, Ingo Molnar wrote: > > * Benjamin Gilbert wrote: > > > We've removed the option, so stop talking about it. > > > > Signed-off-by: Benjamin Gilbert > > Cc: Borislav Petkov > > Cc:

Re: [PATCH] usb: serial: keyspan: remove unused USB_SERIAL_KEYSPAN_X firmware kconfig

On Mon, Jan 22, 2018 at 01:31:32PM +0100, Corentin Labbe wrote: > All USB_SERIAL_KEYSPAN_X are not used anywhere in kernel tree. > Furthermore all firmware files was removed since commit 2971c579f93bi > ("keyspan: use request_firmware()") > So let's clean thoses unused symbols. > >

RE: Request to add new VID/PID to PL2303 driver

Thanks, guys! Do you know what kernel version will I find this addition? -Original Message- From: Johan Hovold [mailto:jhov...@gmail.com] On Behalf Of Johan Hovold Sent: Thursday, January 25, 2018 4:55 PM To: 'g...@kroah.com' Cc: Chu.Mike [朱堅宜]; Johan Hovold; linux-usb@vger.kernel.org

Re: Request to add new VID/PID to PL2303 driver

On Thu, Jan 25, 2018 at 09:51:11AM +0100, Greg Kroah-Hartman wrote: > On Thu, Jan 25, 2018 at 03:44:46AM +, Chu.Mike [朱堅宜] wrote: > > Dear Johan / Greg, > > > > We have a new customer who wants to add their VID/PID to the PL2303 driver > > source. > > Can you help me? > > > > Customer:

Re: Request to add new VID/PID to PL2303 driver

On Thu, Jan 25, 2018 at 03:44:46AM +, Chu.Mike [朱堅宜] wrote: > Dear Johan / Greg, > > We have a new customer who wants to add their VID/PID to the PL2303 driver > source. > Can you help me? > > Customer: Chilitag > VID: 067B > PID: AAA8 > > { USB_DEVICE(PL2303_VENDOR_ID,