Phil-Engljaehringer commented on PR #21114: URL: https://github.com/apache/nuttx/pull/21114#issuecomment-6577995595
Thanks @CV-Bowen. Yes, on the Linux side our `imx_rproc` patch handles that: when the doorbell arrives and the vdev status in the resource table is not `DRIVER_OK`, it detaches and attaches again. That removes the old virtio/rpmsg devices and sets the vrings up again from the fresh resource table. About `ops->start`: in PX4's 12.12-based fork, `rptun_dev_start()` calls `remoteproc_start()` only after `remoteproc_create_virtio()` has returned, i.e. after the host has already set `DRIVER_OK`. A doorbell in `start` would come too late there, just like in `register_callback`, so we would have to change the rptun framework in PX4 as well. So unless @xiaoxiang781216 objects, I'll go ahead with the `get_resource` variant, test it on the i.MX95 and update the PR. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
