StarFive Tech Linux Kernel for VisionFive (JH7110) boards (mirror) https://git.radix-linux.su/starfive-tech/linux.git/atom?h=VF2_v2.5.0 2022-11-10T09:05:37+00:00 2022-11-10T09:05:37+00:00 Alan Stern stern@rowland.harvard.edu 2022-01-01T19:52:14+00:00 urn:sha1:1ffe8d94b711c207eb2857159d8aecf3ef42ad9f 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: <stable@vger.kernel.org> Tested-by: Jonathan McDowell <noodles@earth.li> Signed-off-by: Alan Stern <stern@rowland.harvard.edu> Link: https://lore.kernel.org/r/YdCw7nSfWYPKWQoD@rowland.harvard.edu Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: minda.chen <minda.chen@starfivetech.com> 2022-10-27T05:56:12+00:00 minda.chen minda.chen@starfivetech.com 2022-10-08T11:07:06+00:00 urn:sha1:7f10362dfcf51fe7018d9b0b26db8d9b0baf7e39 add starfive pm supend/resume and runtime pm runtime suspend and resume ops Signed-off-by: minda.chen <minda.chen@starfivetech.com> 2022-08-01T02:06:41+00:00 minda.chen minda.chen@starfivetech.com 2022-07-29T05:29:18+00:00 urn:sha1:2039c204733705acb39bf35e32f756d0c6fa67db USB mass storage and functionfs activated by configfs. Support both 2.0 and 3.0. Signed-off-by: minda.chen <minda.chen@starfivetech.com> 2022-07-29T03:43:13+00:00 mason.huo mason.huo@starfivetech.com 2022-07-29T02:44:45+00:00 urn:sha1:b531495da231905b67b730f69be7075b896799df 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 <mason.huo@starfivetech.com> 2022-07-08T05:15:28+00:00 mason.huo mason.huo@starfivetech.com 2022-07-08T03:24:21+00:00 urn:sha1:0660567dc11b608575834adbc6c5cebf27e6fba8 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 <mason.huo@starfivetech.com> 2022-06-24T02:46:44+00:00 mason.huo mason.huo@starfivetech.com 2022-06-23T11:07:03+00:00 urn:sha1:15bc1016780c65dabc695840a7ad1258ba73f244 2022-06-24T02:46:44+00:00 mason.huo mason.huo@starfivetech.com 2022-06-23T10:36:40+00:00 urn:sha1:bd7aab33423ada46459c5d60bbbed1991e91316c Since the USB_125M clock is divided from pll0 clock, and the pll0 clock changes per the cpu frequency. So, needs to set the clock explicitly. Signed-off-by: mason.huo <mason.huo@starfivetech.com> 2022-05-26T05:53:50+00:00 yanhong.wang yanhong.wang@starfivetech.com 2022-05-26T05:53:50+00:00 urn:sha1:244c458925345e4fbc08ac7d93b18f46e9adf06d Update cdns3-starfive usb control driver, default support usb2.0 and usb3.0. Signed-off-by: yanhong.wang <yanhong.wang@starfivetech.com> 2022-05-05T10:29:07+00:00 yanhong.wang yanhong.wang@starfivetech.com 2022-05-05T09:23:58+00:00 urn:sha1:503056efb8b03b00a6b815eae2c5d2255b789128 Add driver to handle StarFive specific wrapper for Cadence USB3 controller present on JH7110 SoC. Signed-off-by: yanhong.wang <yanhong.wang@starfivetech.com> 2021-10-15T13:04:02+00:00 Greg Kroah-Hartman gregkh@linuxfoundation.org 2021-10-15T13:04:02+00:00 urn:sha1:cd932c2a1ecc8f261ecb8d140fa431c16379931f Johan writes: USB-serial fixes for 5.15-rc6 Here are some new modem device ids. All have been in linux-next with no reported issues. * tag 'usb-serial-5.15-rc6' of https://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-serial: USB: serial: qcserial: add EM9191 QDL support USB: serial: option: add Quectel EC200S-CN module support USB: serial: option: add prod. id for Quectel EG91 USB: serial: option: add Telit LE910Cx composition 0x1204