[REGRESSION] Suspend to RAM does not work anymore with k3-am62-ti-ipc-firmware.dtsi

[Francesco Dolcini]

On Tue, Oct 21, 2025 at 12:06:32PM +0200, Matthias Schiffer wrote:
> On Tue, 2025-10-21 at 15:26 +0530, Beleswar Prasad Padhi wrote:
> > On 21/10/25 15:04, Francesco Dolcini wrote:
> > > 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.
> > 
> > 
> > If not having anything on M4 is the default use case, it should
> > be marked as "status=disabled" in the DT.
> > 
> > > 
> > > 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.
> > 
> > 
> > Having the node is fine, you can still choose to keep it
> > disabled by default.
> 
> I agree with Francenso that it would be nice to keep the node enabled by default
> - whether something is running on the M4 can be controlled via sysfs after all,
> and may change over the runtime of the OS.

In addition, from what I know, this is required even if you want to
to start the firmware of the M4 from U-Boot.

Francesco