|From:||Fernando Guzman Lugo <email@example.com>|
|To:||<firstname.lastname@example.org>, <email@example.com>, <firstname.lastname@example.org>, <email@example.com>|
|Subject:||[PATCHv2 0/3] remoteproc: introduce rproc recovery|
|Date:||Thu, 30 Aug 2012 13:26:11 -0500|
|Cc:||Fernando Guzman Lugo <firstname.lastname@example.org>|
These set of patches make possible the remoteproc recover after a crash. This is a hard recovery, that means the remoteproc is reset and it will start from the beginning. When a crash happen all the virtio devices are destroyed. Therefore, both rpmsg drivers and devices are gracefully removed which also cause rproc users become 0 and the remoteproc is turned off. After the virtio devices are destroyed the crash handler function will read the virtio information from the firmware in order to recreate the virtio devices that will boot the remoteproc and everything will be functional again. -Version 2 * Wait untill there is no more rproc users before realoding the FW again in order to make sure the recovery will work fine. As suggested by Sjur BRENDELAND Fernando Guzman Lugo (3): remoteproc: add rproc_report_crash function to notify rproc crashes remoteproc: recover a remoteproc when it has crashed remoteproc: create debugfs entry to disable/enable recovery dynamically Documentation/remoteproc.txt | 7 ++ drivers/remoteproc/remoteproc_core.c | 116 ++++++++++++++++++++++++++++-- drivers/remoteproc/remoteproc_debugfs.c | 83 +++++++++++++++++++++ drivers/remoteproc/remoteproc_internal.h | 1 + include/linux/remoteproc.h | 22 ++++++ 5 files changed, 222 insertions(+), 7 deletions(-)
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds