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 ADF24C47DA9 for ; Mon, 29 Jan 2024 12:31:37 +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:In-Reply-To: Content-Transfer-Encoding:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=1JHCyUNK3vyI2wZ/zYDDxFjQS9fWSbojIGSf/yNXOJ8=; b=dStDHgrdVQ8L6nDvW6ricu6abH BDNn2JPT3IwR9YUMnWhjsnfM8h6UaCIXbZ1JwYyTKBc4UCRltEyZZuzMh420T+spYQFqLUDy/ZwaE cpBNXtion/BbDhfz+uzqAiByhANuikFXJTVNLquh8X2dcU/OgL6/a5UmqXdgf3hI1hEE12cgOBHMK IhlAVd8AmuytSpqfPf5l4yO1sWCBiS2g8G3wZ1DhcJtIR8L2uWgkoqw8gl1HnVcb0zdciD5vVFOz7 DwOmSzZ0B+IzGAs2eDnTqzgK8is7b7vJu60NjpPPdsBF7qQNETedNNekyukE7z2xNDlYEI6tiCyWK HCW07r/w==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1rUQnZ-0000000CcEy-1PJR; Mon, 29 Jan 2024 12:31:37 +0000 Received: from sin.source.kernel.org ([145.40.73.55]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1rUQnW-0000000CcEB-175o for ath11k@lists.infradead.org; Mon, 29 Jan 2024 12:31:35 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sin.source.kernel.org (Postfix) with ESMTP id 89799CE1256; Mon, 29 Jan 2024 12:31:30 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id DD0F1C433F1; Mon, 29 Jan 2024 12:31:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1706531486; bh=tVQ5qaT9uy6sOSFMA/0IQv7M4Iyl2ka4MNiJs1OuVy4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=e5iPd9+pGha8Rc6MyJhx9PuKtk+gM2CZkDtpQbBvfLOLaeavRMYSgYknG37JMIP8T bL0Y0SBIbWea6DRJrOMckBJsFFv1GY8KqxG2WAuqTd6da0SCu1n3gexllaGZod0gVn 3ykV3PjCRVgGnwqKTPZonufxmvk6/Gv0RbJjsIs1Y64ZI1A5BTo1IC3oZ758RFcFWm DG5RLmga31dEB2aQZWREz4poW10CaQmFh8qPrt+IvVqebp2EkCOKJt/r74WewD/JeL k6qK/LjXQxLrgxL2226U7uN3abfXzoxNwcCWoSz7S6K9qK5v+Cr9pDUKMHplGf1J/n SXCI8zRKj+BQQ== Date: Mon, 29 Jan 2024 18:01:12 +0530 From: Manivannan Sadhasivam To: "Rafael J. Wysocki" Cc: Baochen Qiang , pavel@ucw.cz, Manivannan Sadhasivam , "Kalle Valo (QUIC)" , Jeff Johnson , linux-pm@vger.kernel.org, "kernel@quicinc.com" , linux-wireless@vger.kernel.org, ath11k@lists.infradead.org Subject: Re: ath11k resume fails due to kernel blocks probing MHI virtual devices Message-ID: <20240129123112.GA22617@thinkpad> References: <21cd2098-97e1-4947-a5bb-a97582902ead@quicinc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240129_043134_702762_64657C15 X-CRM114-Status: GOOD ( 23.00 ) X-BeenThere: ath11k@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "ath11k" Errors-To: ath11k-bounces+ath11k=archiver.kernel.org@lists.infradead.org On Mon, Jan 29, 2024 at 01:22:27PM +0100, Rafael J. Wysocki wrote: > On Mon, Jan 29, 2024 at 11:10 AM Baochen Qiang wrote: > > > > Hi Rafael and Pavel, > > > > Currently I am facing an ath11k (a kernel WLAN driver) resume issue > > related with kernel PM framework and MHI module. > > > > Before introducing the issue details, I'd like to summarize how ath11k > > interacts with MHI stack to download WLAN firmware to hardware target: > > 1. when booting/restarting, ath11k powers on MHI module and waits for > > MHI channels to be ready. > > 2. When power on, MHI stack creates some virtual MHI devices, which > > represents MHI hardware channels, and adds them to MHI bus. This > > triggers MHI client driver, named QRTR, to get matched and probe those > > MHI devices. In probe, QRTR initializes MHI channels and finally move > > them to ready state. > > 3. Once MHI channels ready, ath11k downloads WLAN firmware to hardware > > target, then WLAN is working. > > > > Such an flow works well in general, but introduces issues in hibernation > > cycle: when preparing for hibernation, ath11k powers down MHI, this > > results in MHI devices being destroyed thus QRTR resets MHI channels. > > When resuming back from hibernation, ath11k powers on MHI and waits for > > MHI channels to be ready in its resume callback. As said above, MHI > > creates and adds MHI devices to MHI bus, but they can't be probed at > > that time because device probe is prohibited in device_block_probing(), > > finally this results in ath11k resume timeout. > > > > Now there is an potential fix to this issue which would needs changes in > > MHI stack, i.e., don't destroy MHI devices while hibernating. > > Exactly. > During hibernation, the power to ath11k could be lost and in that case, there will be no channels available from the device. So keeping the "struct dev" when there is no real device attached to the system, goes against the driver model IMO since we would be messing with the refcount. For instance in the case of USB, if the device get's unplugged, would it make sense to keep the "struct dev" for the device in kernel in a hope that it would come back again? The driver model as I understood is, once the actual physical device gets removed, the refcount for "struct dev" should be decremented and it should be destroyed. - Mani -- மணிவண்ணன் சதாசிவம்