starfive-tech/linux.git/drivers/usb, branch VF2_v3.4.5

usb: xhci: using dma_alloc_noncoherent to alloc low memory pool

2023-07-03T09:16:55+00:00

For RISCV_NONCACHEHERENT is set, using dma_alloc_noncoherent to alloc cached large block low memory buffer. And set default size to 4M. (largest size of continuous memory can be supported) Signed-off-by: Minda Chen

Merge branch 'CR_3137_usb_hiber_notify_minda' into 'jh7110-5.15.y-devel'

2023-02-03T11:51:36+00:00

CR_3137 usb: cdns3: add hibernation pm notifier to set roothub wakeup See merge request sdk/linux!679

usb: cdns3: add hibernation pm notifier to set roothub wakeup

2023-02-01T06:48:04+00:00

In hibernation resume case. usb devices maybe not emulated, roothub is suspended, In this case, usb devices will be resume fail. Set roothub active while hibernation resume. Signed-off-by: minda.chen

usb:xhci:To improve performance,usb using lowmem for bulk xfer.

2023-01-29T01:17:24+00:00

Generate an usb low memory pool for usb 3.0 host read/write transfer, default size is 8M. Signed-off-by: minda.chen

usb: phy: init phy in resume function

2023-01-11T09:41:12+00:00

usb phy will be reset in suspend procedure. After resume. Some devices can not work. In usb resume, init phy again. Signed-off-by: minda.chen

USB: core: Fix bug in resuming hub's handling of wakeup requests

2022-11-10T09:05:37+00:00

Bugzilla #213839 reports a 7-port hub that doesn't work properly when devices are plugged into some of the ports; the kernel goes into an unending disconnect/reinitialize loop as shown in the bug report. This "7-port hub" comprises two four-port hubs with one plugged into the other; the failures occur when a device is plugged into one of the downstream hub's ports. (These hubs have other problems too. For example, they bill themselves as USB-2.0 compliant but they only run at full speed.) It turns out that the failures are caused by bugs in both the kernel and the hub. The hub's bug is that it reports a different bmAttributes value in its configuration descriptor following a remote wakeup (0xe0 before, 0xc0 after -- the wakeup-support bit has changed). The kernel's bug is inside the hub driver's resume handler. When hub_activate() sees that one of the hub's downstream ports got a wakeup request from a child device, it notes this fact by setting the corresponding bit in the hub->change_bits variable. But this variable is meant for connection changes, not wakeup events; setting it causes the driver to believe the downstream port has been disconnected and then connected again (in addition to having received a wakeup request). Because of this, the hub driver then tries to check whether the device currently plugged into the downstream port is the same as the device that had been attached there before. Normally this check succeeds and wakeup handling continues with no harm done (which is why the bug remained undetected until now). But with these dodgy hubs, the check fails because the config descriptor has changed. This causes the hub driver to reinitialize the child device, leading to the disconnect/reinitialize loop described in the bug report. The proper way to note reception of a downstream wakeup request is to set a bit in the hub->event_bits variable instead of hub->change_bits. That way the hub driver will realize that something has happened to the port but will not think the port and child device have been disconnected. This patch makes that change. Cc: Tested-by: Jonathan McDowell Signed-off-by: Alan Stern Link: https://lore.kernel.org/r/YdCw7nSfWYPKWQoD@rowland.harvard.edu Signed-off-by: Greg Kroah-Hartman Signed-off-by: minda.chen

usb: cdns: add pm and runtume pm ops

2022-10-27T05:56:12+00:00

add starfive pm supend/resume and runtime pm runtime suspend and resume ops Signed-off-by: minda.chen

usb: gadget: add usb device mass storage and functinfs support

2022-08-01T02:06:41+00:00

USB mass storage and functionfs activated by configfs. Support both 2.0 and 3.0. Signed-off-by: minda.chen

usb: cdns3: Enable LS keep-alive signal

2022-07-29T03:43:13+00:00

The default naneng phy setting of LS keep-alive is not enabled, that will cause some usb mouse (Lenovo sm8823) does not work properly. Also some usb keyboards can not enumerated. Signed-off-by: mason.huo

usb: cdns3: Configuare phy as down-spread-spectrum

2022-07-08T05:15:28+00:00

The default phy spread-spectrum mode is up-spread-spectrum, which is violated the usb3 spec. The up-spread-spectrum mode leads to phy buffers overrun. Signed-off-by: mason.huo