Searched hist:"9 dc9507f1880fb6225e3e058cb5219b152cbf198" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/include/linux/ |
| H A D | remoteproc.h | diff 9dc9507f1880fb6225e3e058cb5219b152cbf198 Fri Mar 12 10:24:47 CST 2021 Mathieu Poirier <mathieu.poirier@linaro.org> remoteproc: Properly deal with the resource table when detaching
If it is possible to detach the remote processor, keep an untouched
copy of the resource table. That way we can start from the same
resource table without having to worry about original values or what
elements the startup code has changed when re-attaching to the remote
processor.
Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>
Reviewed-by: Arnaud Pouliquen <arnaud.pouliquen@st.com>
Link: https://lore.kernel.org/r/20210312162453.1234145-12-mathieu.poirier@linaro.org
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
|
| /openbmc/linux/drivers/remoteproc/ |
| H A D | remoteproc_core.c | diff 9dc9507f1880fb6225e3e058cb5219b152cbf198 Fri Mar 12 10:24:47 CST 2021 Mathieu Poirier <mathieu.poirier@linaro.org> remoteproc: Properly deal with the resource table when detaching
If it is possible to detach the remote processor, keep an untouched
copy of the resource table. That way we can start from the same
resource table without having to worry about original values or what
elements the startup code has changed when re-attaching to the remote
processor.
Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>
Reviewed-by: Arnaud Pouliquen <arnaud.pouliquen@st.com>
Link: https://lore.kernel.org/r/20210312162453.1234145-12-mathieu.poirier@linaro.org
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
|