From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 3AEACC2BD09 for ; Mon, 24 Jun 2024 18:17:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Content-Type:MIME-Version: Message-ID:Date:References:In-Reply-To:Subject:Cc:To:From:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=h/iPmOTkGjykZ4AMKtYHGBwt7zSsm/N1pTR71po1nYQ=; b=ec6xPee0g1WELh3k2wi7X4A2Fk jEhq3+4z711WCEMXje2jjlSegXFHjyMysPMh5MDuK9dFZak5mzrCbMYNlbnf3TV/8HesklDkNTDto w5GlyPPXjvFq0itXhugcKD4B/5LvIBnyhnhZcN9CUMQOQHkaNGJGrO1xDktSWW9nfzfkNLzpaGIrw vn24aDzH7SfJZZFIM788v3VwwOU1N5bKcGv3yxp2xS65nz2D6Pu9HAPrRWgTBwCMkFN8A+mwh1MPr zY6qy9x/JR49EoR3leCK34aHLGnE0Ldb15Su1AgfCa74Zpxpq8qHHjpZeS+/pXQjx/IN3Ejrh0+or slB72a1Q==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1sLoG8-00000000GHw-13tB; Mon, 24 Jun 2024 18:17:44 +0000 Received: from galois.linutronix.de ([193.142.43.55]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1sLoG1-00000000GGr-1Bla for linux-arm-kernel@lists.infradead.org; Mon, 24 Jun 2024 18:17:40 +0000 From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1719253055; 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: in-reply-to:in-reply-to:references:references; bh=h/iPmOTkGjykZ4AMKtYHGBwt7zSsm/N1pTR71po1nYQ=; b=OwNBbgoaFD8FoYEU63bvSEkTqPvLTUe/pmzgfMOtmO13w5aOWUw4OttQAqhFFiaRMpatHR l8lpyFWPosP89TlchbuQL9hrGws6FePtV2VD3HCyjUtsZvWqi3XXl8sYa/gmYMTRoBHC0l RMx8/+ptkM9E4vktPNJNcgyTRFzaH8Mhwgx/JSP6zweCwqx4kEGLic60o29YO7Xq7W+U3L PvJxsHuIZaFhBo0ZZelNTJ47WInKsv8ggl5WOckekPOzIoG7pGYmzohhsceXaop1Dg43Z4 RY+FLSbc/2jwrhFT3ujRiJNglRkbnlaTt8cb8P5XDNcjDMvSpYzoJvl++J3S/g== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1719253055; 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: in-reply-to:in-reply-to:references:references; bh=h/iPmOTkGjykZ4AMKtYHGBwt7zSsm/N1pTR71po1nYQ=; b=VnOsdav4Xy6Q4tA9dBdOuZXEnqAhBN2E1fZCWg8u1p9Zt5Jk6AH3Pq2eAc8uPAuOLAALU9 aChSJ8Wqmb+3bSDA== To: Stefan Wahren , Lukas Wunner , Minas Harutyunyan Cc: Florian Fainelli , "linux-usb@vger.kernel.org" , Linux ARM , bcm-kernel-feedback-list@broadcom.com, Ray Jui , Scott Branden , Marc Zyngier Subject: Re: dwc2: irq 66: nobody cared triggered on resume In-Reply-To: <3fd0c2fb-4752-45b3-94eb-42352703e1fd@gmx.net> References: <2bcf7fac-8e8f-4d7a-a837-08805a0076e3@gmx.net> <3fd0c2fb-4752-45b3-94eb-42352703e1fd@gmx.net> Date: Mon, 24 Jun 2024 20:17:34 +0200 Message-ID: <87y16u6w8x.ffs@tglx> MIME-Version: 1.0 Content-Type: text/plain X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240624_111737_543378_96ACCC58 X-CRM114-Status: UNSURE ( 7.34 ) X-CRM114-Notice: Please train this message. X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Mon, Jun 24 2024 at 19:02, Stefan Wahren wrote: > > Is disabling the IRQ via the upper layers an expected behavior instead > of letting the DWC2 controller driver resolve the situation? It can't because it's an interrupt storm, i.e. 100k unhandled interrupts in a row. So the system would just stay there forever. So one way to solve this is to disable the interrupt accross suspend resume and only reenable it once everything is in functional state again. Thanks, tglx