Revert "ipm: imx: send firmware ready reply to check for fw boot completion"

This reverts commit 01ab719.

This is no longer needed, as we now have a scalable solution
using a vendor-specific resource table, which allows each vendor
to define its own supported features.

Signed-off-by: Iuliana Prodan <iuliana.prodan@nxp.com>

Author: iuliana-prodan

drivers/ipm/Kconfig.imx

@@ -58,9 +58,4 @@ config IPM_IMX_MAX_ID_VAL
 	default 1 if IPM_IMX_MAX_DATA_SIZE_8
 	default 0 if IPM_IMX_MAX_DATA_SIZE_16
 
-config IPM_IMX_FW_READY_REPLY
-	bool "Send FW_READY reply message"
-	help
-	  Send FW_READY reply to check for FW boot completion
-
 endif # IPM_IMX

drivers/ipm/ipm_imx.c

@@ -322,22 +322,6 @@ static int imx_mu_init(const struct device *dev)
 	MU_Init(MU(config));
 	config->irq_config_func(dev);
 
-#if defined(CONFIG_IPM_IMX_FW_READY_REPLY)
-	/* Send FW_READY reply message - this is used on host side,
-	 * for handshake communication.
-	 *
-	 * An example is in Linux, imx_dsp_rproc driver, where
-	 * after starting the remote processor, the host is waiting for a
-	 * FW_READY reply.
-	 */
-	MU_Type * base = MU(config);
-
-	MU_TriggerInterrupts(base, kMU_GenInt0InterruptTrigger |
-				   kMU_GenInt1InterruptTrigger |
-				   kMU_GenInt2InterruptTrigger |
-				   kMU_GenInt3InterruptTrigger);
-#endif
-
 	return 0;
 }