From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 BA56B4248D7; Thu, 30 Jul 2026 12:09:14 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785413355; cv=none; b=bEaYmOfdgZKJBziwsYlcBnNUOArQEZ2bBDPaRDezL+ZYQiXU6HrqdXAh7YO6L6saQQqBMyYvCn6YndUHSuw+p4VMpJpyWxzBIHXkE+u7a2CbSx5mW6b2y+xVvizl6DNmzYBm8Qm1E2lO3zWcJVVd6vMzx7UWQ9LUPH/BGRpYLgA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785413355; c=relaxed/simple; bh=ZvYUsM4e52yTkwCy0PNeaZyw5oO7MwAywxbhRwB79f0=; h=Date:From:To:Cc:Subject:Message-ID:MIME-Version:Content-Type: Content-Disposition:In-Reply-To; b=Qv/uUE6UWtwDfiuD+D9BSrshrpBrKT1EmkEIM35xJcchjkq4UET/OoolrI2XqWSvvUErolAq74FHplKsT/VejFEPgQInOY9r6m76sath9zU/Bm1ucLRETG0bYPy5JlXRGG7AB7Qb4eoqGqfVtm4VqUn1Q7tAwZILGN6/NIuHWUI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=XZL1tGeF; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="XZL1tGeF" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3C6441F000E9; Thu, 30 Jul 2026 12:09:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1785413354; bh=kaxbb4hGIxen8PCLgFdLGDy/QkX3XGfhGMt8egYsPCA=; h=Date:From:To:Cc:Subject:In-Reply-To; b=XZL1tGeFIup4XVQ5QJHQ0Rwt91LpypNnes9DTDM4JVhjHUmOx4F0DoLiQ0t0vfUO+ zGSxp/o0/1igl6HlfM/WToSRFzDsW2WEs1clcOEhevrJlt3Eoxo/N5Qw7WKMoR+cWM 9OPgFipM94aW40XNVtzKzQJzea/IvFEKQT6L6tyJO8KNkC04NoBFQmvUx/v+KS6+LC mKtvs+3Ksn3E0rz5MH8EWlyHNDIn9c84eB7J0yRPVHWPyrMywFtTU7aPfnHI4O3O8J ONONLp/V/NyBhYjIHs0jX1U+AzyC9df1FuS6JSITwfugzkLMrdm621T30gT5c8Z5DM W+qHiMbfgEVng== Date: Thu, 30 Jul 2026 07:09:13 -0500 From: Bjorn Helgaas To: "Hongxing Zhu (OSS)" Cc: Frank Li , "l.stach@pengutronix.de" , "lpieralisi@kernel.org" , "kwilczynski@kernel.org" , "mani@kernel.org" , "robh@kernel.org" , "bhelgaas@google.com" , "s.hauer@pengutronix.de" , "kernel@pengutronix.de" , "festevam@gmail.com" , "linux-pci@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "imx@lists.linux.dev" , "linux-kernel@vger.kernel.org" , Hongxing Zhu Subject: Re: [PATCH v2] PCI: dwc: Add suspend_poweroff flag for platforms with RC power loss Message-ID: <20260730120913.GA1497203@bhelgaas> Precedence: bulk X-Mailing-List: imx@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Thu, Jul 30, 2026 at 08:16:36AM +0000, Hongxing Zhu (OSS) wrote: > > -----Original Message----- > > From: Bjorn Helgaas > > Sent: Thursday, July 30, 2026 6:30 AM > ... > > On Fri, Jul 17, 2026 at 03:41:21PM +0800, hongxing.zhu@oss.nxp.com wrote: > > > From: Richard Zhu > > > > > > Some platforms like i.MX power off their PCIe RC controllers during > > > system suspend, requiring full re-initialization on resume. These > > > platforms need to enter L2 state to properly notify endpoints before > > > power loss. > > > > > > According to PCIe base spec r7.0, sec 5.2, the system software should > > > transition the device into D3Hot before broadcasting the PME_Turn_Off > > > message to initiate L2 entry. However, some endpoint devices fail the > > > D3cold capability check in pci_host_common_d3cold_possible(), which > > > would normally prevent L2 entry. > > > > Wakeup devices that don't support PME from D3cold will fail the > > D3cold capability check, but I don't think those are the problem > > you're solving. > > > You're right. > > > This appears to handle devices that are not in D3hot, and that's > > not a property of the endpoint; it's a property of its driver. Is > > the problem here that some driver didn't put its device in D3hot? > > > I observed some endpoint devices failing the D3cold capability > check, but I haven't identified the root cause. Seems like some instrumentation in pci_host_common_d3cold_possible() could tell us which devices/drivers are relevant. > > > For platforms where the RC loses power during suspend, L2 entry > > > is essential regardless of D3cold support, as the link will be > > > lost anyway. Add a suspend_poweroff flag to force L2 entry in > > > such cases, and enable it for i.MX PCIe controllers. > > > > > > Note: This violates the spec requirement that devices be in > > > D3Hot before PME_Turn_Off, but is necessary for proper operation > > > on platforms with RC power loss during suspend. > > > > If the device isn't in D3hot, it may still be active, and I think > > the PME_Turn_Off will abort any DMAs in progress, which doesn't > > sound like proper operation of the endpoint. > > You're correct - this isn't ideal for endpoint operation. However, > on i.MX platforms, the RC controller will lose power during system > suspend regardless. Without sending PME_Turn_Off, endpoints would > have no notification before the link abruptly goes down. The PME_Turn_Off is some notification, but I don't think the endpoint can do DMA or MSI, so its driver won't be involved. It may be able to do things internally, e.g., write caches to an SSD or transmit packets from its internal buffers. But I think it might still lose power in the middle of operations like that, so it doesn't sound reliable. > This patch adds a flag to force L2 entry for such platforms, > choosing to notify endpoints (even if not ideal) rather than having > the link drop unexpectedly. I'm appreciated for suggestions if > there's a better approach to handle this scenario. Mani recently added pci_suspend_retains_context(), and I think it returns "true" on i.MX. But if the RC is powered off and all the devices need full re-initialization on resume, it sounds like it *should* return "false".