Hello all, I want to start this thread in order to clarify what assumptions a remoteproc driver is able to make about a firmware loaded on a remote processor. Discussion is generated by this thread: [1] https://www.spinics.net/lists/kernel/msg4857733.html imx_dsp_rproc driver assumes that the remote firmware will send a notification once it has booted up and this is the default behavior. This doesn't work well with Zephyr samples which do not send such notification! I want to get an agreement for the following questions: 1) What should be the default behavior of a remote proc driver? In my opinion it should not make any assumption about the remote part. Thus by default the driver should not wait for any message! 2) How can we support various "protocols" of starting up. Eg (wait for firmware / no wait for firmware). In patch [1] Iulia proposed to add a flag that will select the correct behavior. As per Mathieu's comments this doesn't scale up, for next flags. How can we solve this? In my opinion using a kernel module parameter OR a device tree property should be enough. What do you think? thanks, Daniel.
