I didn't find very accurate notify named to host side. but you can enable the debug prints in fwsignal.c when meeting issues.
then to see if the logs can figure out where the problem happened.
OK, I understood. Than you for your answer.
Excuse me for an additional question.
Rebooting the entire host system being the last resort, what procedures should be taken to recover device/driver from malfunction? Rmmod and then insmod the related kernel modules again?
1 of 1 people found this helpful
yes, if your module is not built-in, you need to insmod the module again with a right sequence .