ASPEED EHCI error: "controller refused to start: -110"
Hi,
I started to see below EHCI probe failure on my AST2500 and AST2600 BMC platforms since commit 280a9045bb18 ("ehci: fix EHCI host controller initialization sequence"):
Quoted 1 line
ehci-platform 1e6a3000.usb: USB 2.0, controller refused to start: -110
The error happens because USBSTS.HCHalted stays at 1. But if I ignore the error at probe time, the downstream USB devices can still be enumerated without problems (even though USBSTS.HCHalted is still 1).
My questions are: why USBSTS.HCHalted stays at 1 on ASPEED platforms? Do we need extra configuration at EHCI probe time for ASPEED SoC?
CC Ryan @ASPEED for more comments.
Cheers,
Tao
Hello,
ASPEED EHCI design for HALT bit effect is depend on Asynchronous/Periodic Schedule enable or not. If Asynchronous/Periodic Schedule not enable, but run bit is setting, Halt still = 1.
Ryan Chen
Tel : 886-3-5751185 ext:8857
Quoted 29 lines
-----Original Message-----
From: Tao Ren <[email protected]>
Sent: Wednesday, August 25, 2021 2:24 PM
To: [email protected]
Cc: [email protected]; [email protected]; Ryan Chen <[email protected]>
Subject: ASPEED EHCI error: "controller refused to start: -110"Hi,
I started to see below EHCI probe failure on my AST2500 and AST2600 BMC platforms since commit
280a9045bb18("ehci: fix EHCI host controller initialization sequence"):Quoted 1 line
ehci-platform 1e6a3000.usb: USB 2.0, controller refused to start: -110
The error happens because USBSTS.HCHalted stays at 1. But if I ignore the error at probe time, the downstream USB devices can still be enumerated without problems (even though USBSTS.HCHalted is still 1).
My questions are: why USBSTS.HCHalted stays at 1 on ASPEED platforms? Do we need extra configuration at EHCI probe time for ASPEED SoC?
CC Ryan @ASPEED for more comments.
Cheers,
Tao
Hi Ryan,
Quoted 5 lines · Ryan Chen
Hello,
ASPEED EHCI design for HALT bit effect is depend on Asynchronous/Periodic Schedule enable or not. If Asynchronous/Periodic Schedule not enable, but run bit is setting, Halt still = 1.Ryan Chen
Thanks for the inputs.
What is your recommendation? Enabling Async/Periodic schedule to make USBSTS.HCHalted handshake happy? Or ignoring HCHalted check for ASPEED platforms? Can you please send out a patch to fix the failure? The EHCI driver stops working on ASPEED platforms since v5.10.
Cheers,
Tao
Quoted 32 lines
Tel : 886-3-5751185 ext:8857
Quoted 29 lines
-----Original Message-----
From: Tao Ren <[email protected]>
Sent: Wednesday, August 25, 2021 2:24 PM
To: [email protected]
Cc: [email protected]; [email protected]; Ryan Chen <[email protected]>
Subject: ASPEED EHCI error: "controller refused to start: -110"Hi,
I started to see below EHCI probe failure on my AST2500 and AST2600 BMC platforms since commit
280a9045bb18("ehci: fix EHCI host controller initialization sequence"):Quoted 1 line
ehci-platform 1e6a3000.usb: USB 2.0, controller refused to start: -110
The error happens because USBSTS.HCHalted stays at 1. But if I ignore the error at probe time, the downstream USB devices can still be enumerated without problems (even though USBSTS.HCHalted is still 1).
My questions are: why USBSTS.HCHalted stays at 1 on ASPEED platforms? Do we need extra configuration at EHCI probe time for ASPEED SoC?
CC Ryan @ASPEED for more comments.
Cheers,
Tao
Quoted 17 lines
-----Original Message-----
From: Tao Ren <[email protected]>
Sent: Thursday, August 26, 2021 9:53 AM
To: Ryan Chen <[email protected]>
Cc: [email protected]; [email protected]; [email protected]; Neal Liu <[email protected]>; Joppa Tsao <[email protected]>
Subject: Re: ASPEED EHCI error: "controller refused to start: -110"Hi Ryan,
Quoted 2 lines · Ryan Chen
Hello,
ASPEED EHCI design for HALT bit effect is depend onAsynchronous/Periodic Schedule enable or not.
Quoted 1 line
If Asynchronous/Periodic Schedule not enable, but run bit is setting, Halt
still = 1.
Quoted 1 line
Quoted 9 lines
Quoted 1 line
Ryan Chen
Thanks for the inputs.
What is your recommendation? Enabling Async/Periodic schedule to make USBSTS.HCHalted handshake happy? Or ignoring HCHalted check for ASPEED platforms? Can you please send out a patch to fix the failure? The EHCI driver stops working on ASPEED platforms since v5.10.
I think it should ignoring the HCHalted check for ASPEED platform. I need think about how to patch for fix this.
Quoted 38 lines
Cheers,
Tao
Quoted 26 lines
Tel : 886-3-5751185 ext:8857
Quoted 23 lines
-----Original Message-----
From: Tao Ren <[email protected]>
Sent: Wednesday, August 25, 2021 2:24 PM
To: [email protected]
Cc: [email protected]; [email protected]; Ryan Chen <[email protected]>
Subject: ASPEED EHCI error: "controller refused to start: -110"Hi,
I started to see below EHCI probe failure on my AST2500 and AST2600 BMC platforms since commit
280a9045bb18("ehci: fix EHCI host controller initialization sequence"):Quoted 2 lines
ehci-platform 1e6a3000.usb: USB 2.0, controller refused to start:
-110The error happens because USBSTS.HCHalted stays at 1. But if I ignore the error at probe time, the downstream USB devices can still be enumerated without problems (even though USBSTS.HCHalted is still 1).
My questions are: why USBSTS.HCHalted stays at 1 on ASPEED platforms? Do we need extra configuration at EHCI probe time for ASPEED
SoC?
Quoted 7 lines
Quoted 7 lines
CC Ryan @ASPEED for more comments.
Cheers,
Tao