From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail11.truemail.it (mail11.truemail.it [217.194.8.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A7C3E231845; Tue, 21 Oct 2025 09:42:11 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=217.194.8.81 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1761039735; cv=none; b=h/mXmkEa0NIxguFqqnTJVnFi3oTApNXPOq3cCVjVE3/uhKls5pNWcPbILz1XWLCt4v/aL0BbLEGUR9hmNl3tFkwhk92WucrpPgvHWoGo3l8pbtV5bvq9ZyIlR8JP2D0GUA6tFAAVXWrNegBLYt3wYEP6n0upyZFr74YEbgJBsUs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1761039735; c=relaxed/simple; bh=B3Jy7cA+N4KH4QnWIOx/sol3r3bRZVymO5EXRRR8cSA=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=R5RP/Bm44SEHnvcVva8DTBN7yZaNOhZYcsfML3J9RPe32XHnaa/uLAaWVIsDwaVCnLzmc4Pbb0/WH3CFD8ka/+EC3tB8Qp7VcouzEzgJ/McR16gvHf6ehyvBDeuBOwhyOayXxkTVOko9zSAzgdkBWHVWxtT7PH6eSl7Yi3Nawkc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=dolcini.it; spf=pass smtp.mailfrom=dolcini.it; dkim=pass (2048-bit key) header.d=dolcini.it header.i=@dolcini.it header.b=YfPu/PPl; arc=none smtp.client-ip=217.194.8.81 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=dolcini.it Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=dolcini.it Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=dolcini.it header.i=@dolcini.it header.b="YfPu/PPl" Received: from francesco-nb (248.201.173.83.static.wline.lns.sme.cust.swisscom.ch [83.173.201.248]) by mail11.truemail.it (Postfix) with ESMTPA id EB6942125B; Tue, 21 Oct 2025 11:34:23 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dolcini.it; s=default; t=1761039265; bh=8o+wETYksP8ccjEosz8Cbz5sDcAm+lKn1MXus85N6hk=; h=From:To:Subject; b=YfPu/PPlq2HCEYCkZ6DMBbfM0yvF6ZC7n12d9hkKdj1MW9iFrUpGbN65nH0cIiBv5 7g9HNVFSTM6pKIk+d95YldohlYU6EfMAPBOgbGMVJRp7T0C86mFnTpfUDxI0VJIT5h yTQD8LLRTku7cjc8PtWy0zOQum5BXOFH5Y+Z6zrXwcOy2wWPGksj8QCK/ZIAK4x9si c/2knDKelHt2/GZva+si3bcwSwa4sjZflo1rrU6vuGbV7rZoCJYN2D/wS/kKb3tjHY NSdliuWB8h9HyN7JwSfMiQ8sYo9r4hkLvNhB4zAN8cwQ4vj1oz3Eo6cHiKWw6MaNZm 7KZrWVWc24MRA== Date: Tue, 21 Oct 2025 11:34:20 +0200 From: Francesco Dolcini To: Beleswar Prasad Padhi Cc: Hiago De Franco , nm@ti.com, vigneshr@ti.com, kristo@kernel.org, robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org, afd@ti.com, u-kumar1@ti.com, hnagalla@ti.com, jm@ti.com, d-gole@ti.com, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Robert Nelson , =?iso-8859-1?Q?Jo=E3o_Paulo_Gon=E7alves?= , Emanuele Ghidoli , Francesco Dolcini , Matthias Schiffer , Logan Bristol , Josua Mayer , John Ma , Nathan Morrisson , Garrett Giordano , Matt McKee , Wadim Egorov , Max Krummenacher , Stefan Eichenberger , Hiago De Franco , Diogo Ivo , Li Hua Qian , Jan Kiszka , Baocheng Su , Benedikt Niedermayr , regressions@lists.linux.dev Subject: Re: [REGRESSION] Suspend to RAM does not work anymore with k3-am62-ti-ipc-firmware.dtsi Message-ID: <20251021093420.GA28462@francesco-nb> References: Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: On Tue, Oct 21, 2025 at 02:33:10PM +0530, Beleswar Prasad Padhi wrote: > On 20/10/25 19:47, Hiago De Franco wrote: > > DM R5 sends a message that is never consumed, since no firmware is > > running on the M4 (the core is offline). > > > May I know why you are not running any firmware on the M4 > rproc? If the intention is just to run the DM R5 core on the SoC, > you can disable the IPC by NOT including the > "k3-am62-ti-ipc-firmware.dtsi". That was the motivation for the > refactoring. Verdin AM62 and AM62P are generic SoMs, that can be used for a multitude of different use cases. And not having anything running on the M4 is the default use case. I think having the node in the DT is the correct way forward, if you want to start the M4 firmware you need such a node, so this is enabling a valid and useful use case. > List of suggestions/solutions in order of preference: > 1. If no intention to enable IPC on rprocs: >       Do _not_ include k3-am62-ti-ipc-firmware.dtsi > 2. If intention is to enable IPC on rprocs: >       Make sure rproc firmware is available in rootfs. >       rproc would boot up and consume the mbox >       msg, suspend would be successful. Tested this >       on TI AM62x-sk with commit 1d6161617c, works > 3. Add support in mbox driver to flush the pending >     queues. 2 is not applicable here, and 1 to me is not a good solution. So this means that we need #3. > > #regzbot introduced: 1d6161617c > > Would not see this as a regression, but rather a new > bug for the omap-mailbox driver... As a user this is just a regression. It worked fine before, it's not working anymore now. The fact that the solution might not be in the same file that introduced the issue is not a reason for this not being considered a regression. Francesco