drivers: i3c: stm32: Fix issue with DAA command

The TXFNF needs to be disabled for additional I3C targets
during the DAA process. Otherwise the TX interrupt might be triggered
before receiving full PID for target.

Signed-off-by: Adam BERLINGER <[email protected]>

Author: ABESTM

drivers/i3c/i3c_stm32.c

@@ -1090,14 +1090,14 @@ static int i3c_stm32_do_daa(const struct device *dev)
 
 	if (data->msg_state == STM32_I3C_MSG_ERR) {
 		i3c_stm32_clear_err(dev, false);
-		/* Enable TXFNF interrupt in case an error occurred before it was enabled by RXFNE
-		 */
-		LL_I3C_EnableIT_TXFNF(i3c);
 		ret = -EIO;
 		goto i3c_stm32_do_daa_ending;
 	}
 
 i3c_stm32_do_daa_ending:
+	/* We enable TX interrupt again in any case */
+	LL_I3C_EnableIT_TXFNF(i3c);
+
 	k_mutex_unlock(&data->bus_mutex);
 
 	return ret;
@@ -1622,6 +1622,11 @@ static void i3c_stm32_event_isr_tx(const struct device *dev)
 		dcr = data->pid & 0xFF;
 		data->pid >>= 16;
 
+		/* Disable TXFNF interrupt, the RXFNE interrupt will enable it once all PID bytes
+		 * are received for next I3C target, or in i3c_stm32_do_daa after frame complete
+		 */
+		LL_I3C_DisableIT_TXFNF(i3c);
+
 		/* Find the device in the device list */
 		ret = i3c_dev_list_daa_addr_helper(&data->drv_data.attached_dev.addr_slots,
 						   &config->drv_cfg.dev_list, data->pid, false,