kernel/linux.git/drivers/usb/mtu3, branch linux-4.20.y

usb: mtu3: fix the issue about SetFeature(U1/U2_Enable)

2019-02-12T19:02:14+00:00

[ Upstream commit a0678e2eed41e81004308693ac84ea95614b0920 ] Fix the issue: device doesn't accept LGO_U1/U2: 1. set SW_U1/U2_ACCEPT_ENABLE to eanble controller to accept LGO_U1/U2 by default; 2. enable/disable controller to initiate requests for transition into U1/U2 by SW_U1/U2_REQUEST_ENABLE instead of SW_U1/U2_ACCEPT_ENABLE; Signed-off-by: Chunfeng Yun Signed-off-by: Felipe Balbi Signed-off-by: Sasha Levin

Merge 4.19-rc4 into usb-next

2018-09-16T20:44:14+00:00

We need the USB fixes in here as well. Signed-off-by: Greg Kroah-Hartman

usb: mtu3: disable vbus rise/fall interrupts of ltssm

2018-09-10T18:09:09+00:00

The vbus rise & fall interrupts are used to enable and disable U3 function of device automatically, this cause some issues when class driver is initialized as deactivated, and will skip over software-controlled connect by pullup(), but UDC wants to keep disconnect until usb_gadget_activate() is called which calls pullup() if needed. So we disable vbus rise & fall interrupts and just use pullup() to enable & disable U3 function, and reset mtu3 state when disconnect instead when vbus fall. Signed-off-by: Chunfeng Yun Signed-off-by: Greg Kroah-Hartman

usb: mtu3: fix error of xhci port id when enable U3 dual role

2018-09-05T11:27:07+00:00

If dual role mode is enabled, when switch u3port0 to device mode, it will affect port id calculation of host(xHCI), specially when host supports multi U2 ports or U3 ports, so need enable its dual role mode, and fix it here. Signed-off-by: Chunfeng Yun Cc: stable Signed-off-by: Greg Kroah-Hartman

USB: mtu3: no need to check return value of debugfs_create_dir()

2018-05-31T10:54:21+00:00

When calling debugfs functions, there is no need to ever check the return value. The function can work or not, but the code logic should never do something different based on this. Cc: Chunfeng Yun Signed-off-by: Greg Kroah-Hartman

usb: mtu3: fix warning of sleep in atomic context in notifier callback

2018-05-24T16:09:37+00:00

The notifier callbacks of extcon are called in atomic context, but the callbacks will call regulator_enable()/regulator_disable() which may sleep caused by mutex, so use work queue to call the sleep functions. Signed-off-by: Chunfeng Yun Signed-off-by: Greg Kroah-Hartman

usb: mtu3: reset gadget when VBUS_FALL interrupt arises

2018-05-24T16:09:37+00:00

When VBUS_FALL interrupt arises, it means U3 device is disconnected with host, so need reset status of gadget Signed-off-by: Chunfeng Yun Signed-off-by: Greg Kroah-Hartman

usb: mtu3: avoid sleep in atomic context when enter test mode

2018-05-24T16:09:37+00:00

Use readl_poll_timeout_atomic() instead of readl_poll_timeout() in atomic context Signed-off-by: Chunfeng Yun Signed-off-by: Greg Kroah-Hartman

usb: mtu3: clear test_mode flag when reset

2018-05-24T16:09:37+00:00

Clear test_mode flag when the gadget is reset by host, otherwise will affect the next test item. Signed-off-by: Chunfeng Yun Signed-off-by: Greg Kroah-Hartman

usb: mtu3: fix uncontinuous SeqN issue after disable EP

2018-05-24T16:09:37+00:00

Reset EP when disable it to reset data toggle for U2 EP, and SeqN, flow control status etc for U3 EP, this can avoid issue of uncontinuous SeqN Signed-off-by: Chunfeng Yun Signed-off-by: Greg Kroah-Hartman