summaryrefslogtreecommitdiffstats
path: root/drivers/remoteproc/Makefile
diff options
context:
space:
mode:
authorJulien Massot <julien.massot@iot.bzh>2021-12-07 17:58:29 +0100
committerMathieu Poirier <mathieu.poirier@linaro.org>2021-12-13 19:30:55 +0100
commit285892a74f1370a12249f765c6a4e3b16194852e (patch)
treed40344c96ec701f79df0b029ec62dff2755a37ed /drivers/remoteproc/Makefile
parentdt-bindings: remoteproc: Add Renesas R-Car (diff)
downloadlinux-285892a74f1370a12249f765c6a4e3b16194852e.tar.xz
linux-285892a74f1370a12249f765c6a4e3b16194852e.zip
remoteproc: Add Renesas rcar driver
Renesas Gen3 platform includes a Cortex-r7 processor. Both: the application cores (A5x) and the realtime core (CR7) share access to the RAM and devices with the same address map, so device addresses are equal to the Linux physical addresses. In order to initialize this remote processor we need to: - power on the realtime core - put the firmware in a RAM area - set the boot address for this firmware (reset vector) - Deassert the reset This initial driver allows to start and stop the Cortex R7 processor. Signed-off-by: Julien Massot <julien.massot@iot.bzh> Link: https://lore.kernel.org/r/20211207165829.195537-3-julien.massot@iot.bzh Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>
Diffstat (limited to 'drivers/remoteproc/Makefile')
-rw-r--r--drivers/remoteproc/Makefile1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/remoteproc/Makefile b/drivers/remoteproc/Makefile
index 0ac256b6c977..5478c7cb9e07 100644
--- a/drivers/remoteproc/Makefile
+++ b/drivers/remoteproc/Makefile
@@ -32,6 +32,7 @@ obj-$(CONFIG_QCOM_SYSMON) += qcom_sysmon.o
obj-$(CONFIG_QCOM_WCNSS_PIL) += qcom_wcnss_pil.o
qcom_wcnss_pil-y += qcom_wcnss.o
qcom_wcnss_pil-y += qcom_wcnss_iris.o
+obj-$(CONFIG_RCAR_REMOTEPROC) += rcar_rproc.o
obj-$(CONFIG_ST_REMOTEPROC) += st_remoteproc.o
obj-$(CONFIG_ST_SLIM_REMOTEPROC) += st_slim_rproc.o
obj-$(CONFIG_STM32_RPROC) += stm32_rproc.o