From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-172.mta0.migadu.com (out-172.mta0.migadu.com [91.218.175.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 20716307494 for ; Wed, 14 Jan 2026 17:31:27 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.172 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768411892; cv=none; b=BP1kQWiZ5cH5TVshBkGGjMykF95k6wIIZQAxqzH7L5pEz4bQBpymwcKek+snKCV6E+AxhGWgoStaz2m8RVBDw24pTa3E5JBjRLOKvHwSXGpzVr7GS3Ngf10AHRfl15oLqRVqeSuZ6oBexRXgDeMCGFQR+BuvW2rsk2bA/pfWIK8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768411892; c=relaxed/simple; bh=ejwhFcDiVubKmUTMYvEWonwx6kfulx8UA93XLL0QL9g=; h=Mime-Version:Content-Type:Date:Message-Id:Subject:From:To:Cc: References:In-Reply-To; b=U8vmvrEvcme0d/iXOuXicShB+mg7TxOJ3FilasUUQzAL0wBHaXMNz7YGtJH4NPGJjoPSzBtL+ty/k44WZ5bC1xPVJiz7zNzMJq39IU1Itz8+tqmVLG01ZQixuacgT7u0sUsFHkj9Vpz19QxuugMTgOEet8+8b43MoZnLgeGiLD8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=cknow-tech.com; spf=pass smtp.mailfrom=cknow-tech.com; dkim=pass (2048-bit key) header.d=cknow-tech.com header.i=@cknow-tech.com header.b=AaxY7tfn; arc=none smtp.client-ip=91.218.175.172 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=cknow-tech.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=cknow-tech.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=cknow-tech.com header.i=@cknow-tech.com header.b="AaxY7tfn" Precedence: bulk X-Mailing-List: linux-usb@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cknow-tech.com; s=key1; t=1768411885; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=0YPRVG2Kt3RIzXwQiUJV9LIgvxAOvSvPHT6ORBbUlgE=; b=AaxY7tfnwX2HhjTNbqdTaSETNtcnp69xmApYFC0xRLe1aYNrAkN36g4+U1K71jPkz/mZnT 5XCGPSsZpGk6qK6lXUbZ/EPRL6GjsNdx10ERPBvdviA9nu2FPKWc4yyLCs/VVBvSbOB56f Rz9U6ZUh6HVlBVg5wN+5TYiwgJFe2Ou4ccK0yZARQ3E+DVrty8bjgmyaMOVeXWJW+WcGxK bTBr8PpUar2hX6gmqZGa+LKM0mNksI9B2A7OkD8s5IriaCnwQMQK7zhQpmPBGL08fEeDwY GjxemZpCwft0F+ZbxxFUht8HDLB/eXdiyfalUTyNlOZtIFUtWGxO7SYKfhkbug== Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Wed, 14 Jan 2026 18:31:23 +0100 Message-Id: Subject: Re: Track down EHCI and companion errors on rk3xxx systems X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: "Diederik de Haas" To: "Alan Stern" Cc: "USB mailing list" , References: <073879e4-aea8-4625-bc83-c4b6dd9c9231@rowland.harvard.edu> <38365c37-b125-4ffb-8ce7-bd4f3f7596ba@rowland.harvard.edu> <91fb697a-7bfa-4e26-85cd-40810a8d2be5@rowland.harvard.edu> In-Reply-To: X-Migadu-Flow: FLOW_OUT On Wed Jan 14, 2026 at 5:07 PM CET, Alan Stern wrote: > However, I agree: 30 seconds is _much_ longer than it should take to=20 > detect a newly plugged-in device. It should take less than one second. = =20 > One possibility is that something involved in waking up the EHCI host=20 > controller from its runtime suspend may have caused the delay -- that's= =20 > why I asked you to try turning off the controller's runtime suspend.=20 It may be completely natural, but I was surprised runtime suspend was involved at all. So I'll definitely do a test by turning it off. > Also, I'm not at all familiar with the particular hardware used by your= =20 > platform for receiving wakeup signals. It's possible that a GPIO=20 > responsible for this wasn't working right and that's why you were=20 > getting all those warning messages. Another reason for wanting to know= =20 > what will happen if you take suspends and wakeups out of the picture. I think GPIO is involved with wakeup signals ... sometimes at least. I added the linux-rockchip ML precisely because I (strongly) suspect there is Rockchip specific part to all this. Cheers, Diederik PS: I very much appreciate you taking the time for this 'debugging' session :-)