| author | Sarangdhar Joshi <spjoshi@codeaurora.org> | |
| Fri, 26 May 2017 23:51:00 +0000 (16:51 -0700) | ||
| committer | Bjorn Andersson <bjorn.andersson@linaro.org> | |
| Sat, 27 May 2017 01:11:31 +0000 (18:11 -0700) | ||
| commit | 1efa30d0895e7e9a58a59b0880b330b38245be68 | |
| tree | 565fb8e298f188d6bb783a6e84b6972bec6e2754 | tree | snapshot (tar.xz tar.gz zip) |
| parent | 2ea659a9ef488125eb46da6eb571de5eae5c43f6 | commit | diff |
remoteproc: Introduce rproc_{start,stop}() functions
In the context of recovering from crash, rproc_trigger_recovery() does
rproc_shutdown() followed by rproc_boot(). The remoteproc resources are
cleaned up in rproc_shutdown() and immediately reallocated in
rproc_boot() which is an unnecessary overhead. Furthermore, we want the
memory regions to be accessible after stopping the remote processor, to
be able to extract the memory content for a coredump.
This patch factors out the code in rproc_boot() and rproc_shutdown()
path and introduces rproc_{start,stop}() in order to avoid resource
allocation overhead.
Signed-off-by: Sarangdhar Joshi <spjoshi@codeaurora.org>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
In the context of recovering from crash, rproc_trigger_recovery() does
rproc_shutdown() followed by rproc_boot(). The remoteproc resources are
cleaned up in rproc_shutdown() and immediately reallocated in
rproc_boot() which is an unnecessary overhead. Furthermore, we want the
memory regions to be accessible after stopping the remote processor, to
be able to extract the memory content for a coredump.
This patch factors out the code in rproc_boot() and rproc_shutdown()
path and introduces rproc_{start,stop}() in order to avoid resource
allocation overhead.
Signed-off-by: Sarangdhar Joshi <spjoshi@codeaurora.org>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
| drivers/remoteproc/remoteproc_core.c | diff | blob | history |