1# SPDX-License-Identifier: GPL-2.0-only 2menu "Remoteproc drivers" 3 4config REMOTEPROC 5 bool "Support for Remote Processor subsystem" 6 depends on HAS_DMA 7 select CRC32 8 select FW_LOADER 9 select VIRTIO 10 select WANT_DEV_COREDUMP 11 help 12 Support for remote processors (such as DSP coprocessors). These 13 are mainly used on embedded systems. 14 15if REMOTEPROC 16 17config REMOTEPROC_CDEV 18 bool "Remoteproc character device interface" 19 help 20 Say y here to have a character device interface for the remoteproc 21 framework. Userspace can boot/shutdown remote processors through 22 this interface. 23 24 It's safe to say N if you don't want to use this interface. 25 26config AMD_MBV_BRAM_REMOTEPROC 27 tristate "AMD MicroBlaze/V BRAM-based remoteproc support" 28 depends on OF && COMMON_CLK && (GPIOLIB || COMPILE_TEST) 29 help 30 Say y or m here to support a MicroBlaze/V BRAM-based remote 31 processor managed through the remoteproc framework. 32 33 If unsure, say N. 34 35config IMX_REMOTEPROC 36 tristate "i.MX remoteproc support" 37 depends on ARCH_MXC 38 depends on HAVE_ARM_SMCCC 39 depends on IMX_SCMI_CPU_DRV || !IMX_SCMI_CPU_DRV 40 depends on IMX_SCMI_LMM_DRV || !IMX_SCMI_LMM_DRV 41 select MAILBOX 42 help 43 Say y here to support iMX's remote processors via the remote 44 processor framework. 45 46 It's safe to say N here. 47 48config IMX_DSP_REMOTEPROC 49 tristate "i.MX DSP remoteproc support" 50 depends on ARCH_MXC 51 depends on HAVE_ARM_SMCCC 52 select MAILBOX 53 help 54 Say y here to support iMX's DSP remote processors via the remote 55 processor framework. 56 57 It's safe to say N here. 58 59config INGENIC_VPU_RPROC 60 tristate "Ingenic JZ47xx VPU remoteproc support" 61 depends on MIPS || COMPILE_TEST 62 help 63 Say y or m here to support the VPU in the JZ47xx SoCs from Ingenic. 64 65 This can be either built-in or a loadable module. 66 If unsure say N. 67 68config MTK_SCP 69 tristate "Mediatek SCP support" 70 depends on ARCH_MEDIATEK || COMPILE_TEST 71 select RPMSG_MTK_SCP 72 help 73 Say y here to support Mediatek's System Companion Processor (SCP) via 74 the remote processor framework. 75 76 It's safe to say N here. 77 78config OMAP_REMOTEPROC 79 tristate "OMAP remoteproc support" 80 depends on ARCH_OMAP4 || SOC_OMAP5 || SOC_DRA7XX 81 depends on OMAP_IOMMU 82 select MAILBOX 83 select OMAP2PLUS_MBOX 84 help 85 Say y here to support OMAP's remote processors (dual M3 86 and DSP) via the remote processor framework. 87 88 Usually you want to say Y here, in order to enable multimedia 89 use-cases to run on your platform (multimedia codecs are 90 offloaded to remote DSP processors using this framework). 91 92 It's safe to say N here if you're not interested in multimedia 93 offloading or just want a bare minimum kernel. 94 95config OMAP_REMOTEPROC_WATCHDOG 96 bool "OMAP remoteproc watchdog timer" 97 depends on OMAP_REMOTEPROC 98 default n 99 help 100 Say Y here to enable watchdog timer for remote processors. 101 102 This option controls the watchdog functionality for the remote 103 processors in OMAP. Dedicated OMAP DMTimers are used by the remote 104 processors and triggers the timer interrupt upon a watchdog 105 detection. 106 107config WKUP_M3_RPROC 108 tristate "AMx3xx Wakeup M3 remoteproc support" 109 depends on SOC_AM33XX || SOC_AM43XX || COMPILE_TEST 110 help 111 Say y here to support Wakeup M3 remote processor on TI AM33xx 112 and AM43xx family of SoCs. 113 114 Required for Suspend-to-RAM on AM33xx and AM43xx SoCs. Also needed 115 for deep CPUIdle states on AM33xx SoCs. Allows for loading of the 116 firmware onto these remote processors. 117 If unsure say N. 118 119config DA8XX_REMOTEPROC 120 tristate "DA8xx/OMAP-L13x remoteproc support" 121 depends on ARCH_DAVINCI_DA8XX || COMPILE_TEST 122 depends on DMA_CMA 123 help 124 Say y here to support DA8xx/OMAP-L13x remote processors via the 125 remote processor framework. 126 127 You want to say y here in order to enable AMP 128 use-cases to run on your platform (multimedia codecs are 129 offloaded to remote DSP processors using this framework). 130 131 This module controls the name of the firmware file that gets 132 loaded on the DSP. This file must reside in the /lib/firmware 133 directory. It can be specified via the module parameter 134 da8xx_fw_name=<filename>, and if not specified will default to 135 "rproc-dsp-fw". 136 137 It's safe to say n here if you're not interested in multimedia 138 offloading. 139 140config KEYSTONE_REMOTEPROC 141 tristate "Keystone Remoteproc support" 142 depends on ARCH_KEYSTONE || COMPILE_TEST 143 help 144 Say Y here here to support Keystone remote processors (DSP) 145 via the remote processor framework. 146 147 It's safe to say N here if you're not interested in the Keystone 148 DSPs or just want to use a bare minimum kernel. 149 150config MESON_MX_AO_ARC_REMOTEPROC 151 tristate "Amlogic Meson6/8/8b/8m2 AO ARC remote processor support" 152 depends on HAS_IOMEM 153 depends on (ARM && ARCH_MESON) || COMPILE_TEST 154 select GENERIC_ALLOCATOR 155 help 156 Say m or y here to have support for the AO ARC remote processor 157 on Amlogic Meson6/Meson8/Meson8b/Meson8m2 SoCs. This is 158 typically used for system suspend. 159 If unsure say N. 160 161config PRU_REMOTEPROC 162 tristate "TI PRU remoteproc support" 163 depends on TI_PRUSS 164 default TI_PRUSS 165 help 166 Support for TI PRU remote processors present within a PRU-ICSS 167 subsystem via the remote processor framework. 168 169 Say Y or M here to support the Programmable Realtime Unit (PRU) 170 processors on various TI SoCs. It's safe to say N here if you're 171 not interested in the PRU or if you are unsure. 172 173config QCOM_PIL_INFO 174 tristate 175 176config QCOM_RPROC_COMMON 177 tristate 178 select AUXILIARY_BUS 179 180config QCOM_Q6V5_COMMON 181 tristate 182 depends on ARCH_QCOM 183 depends on QCOM_SMEM 184 185config QCOM_Q6V5_ADSP 186 tristate "Qualcomm ADSP Peripheral Image Loader" 187 depends on OF && ARCH_QCOM 188 depends on QCOM_SMEM 189 depends on RPMSG_QCOM_SMD || RPMSG_QCOM_SMD=n 190 depends on RPMSG_QCOM_GLINK_SMEM || RPMSG_QCOM_GLINK_SMEM=n 191 depends on QCOM_SYSMON || QCOM_SYSMON=n 192 depends on RPMSG_QCOM_GLINK || RPMSG_QCOM_GLINK=n 193 depends on QCOM_AOSS_QMP || QCOM_AOSS_QMP=n 194 select MFD_SYSCON 195 select QCOM_PIL_INFO 196 select QCOM_MDT_LOADER 197 select QCOM_Q6V5_COMMON 198 select QCOM_RPROC_COMMON 199 help 200 Say y here to support the Peripheral Image Loader 201 for the non-TrustZone part of Qualcomm Technology Inc. ADSP and CDSP 202 remote processors. The TrustZone part is handled by QCOM_Q6V5_PAS 203 driver. 204 205config QCOM_Q6V5_MSS 206 tristate "Qualcomm Hexagon V5 self-authenticating modem subsystem support" 207 depends on OF && ARCH_QCOM 208 depends on QCOM_SMEM 209 depends on RPMSG_QCOM_SMD || RPMSG_QCOM_SMD=n 210 depends on RPMSG_QCOM_GLINK_SMEM || RPMSG_QCOM_GLINK_SMEM=n 211 depends on QCOM_SYSMON || QCOM_SYSMON=n 212 depends on RPMSG_QCOM_GLINK || RPMSG_QCOM_GLINK=n 213 depends on QCOM_AOSS_QMP || QCOM_AOSS_QMP=n 214 select MFD_SYSCON 215 select QCOM_MDT_LOADER 216 select QCOM_PIL_INFO 217 select QCOM_Q6V5_COMMON 218 select QCOM_RPROC_COMMON 219 select QCOM_SCM 220 select QCOM_PAS 221 help 222 Say y here to support the Qualcomm self-authenticating modem 223 subsystem based on Hexagon V5. The TrustZone based system is 224 handled by QCOM_Q6V5_PAS driver. 225 226config QCOM_Q6V5_PAS 227 tristate "Qualcomm Peripheral Authentication Service support" 228 depends on OF && ARCH_QCOM 229 depends on QCOM_SMEM 230 depends on RPMSG_QCOM_SMD || RPMSG_QCOM_SMD=n 231 depends on RPMSG_QCOM_GLINK_SMEM || RPMSG_QCOM_GLINK_SMEM=n 232 depends on QCOM_SYSMON || QCOM_SYSMON=n 233 depends on RPMSG_QCOM_GLINK || RPMSG_QCOM_GLINK=n 234 depends on QCOM_AOSS_QMP || QCOM_AOSS_QMP=n 235 select MFD_SYSCON 236 select QCOM_PIL_INFO 237 select QCOM_MDT_LOADER 238 select QCOM_Q6V5_COMMON 239 select QCOM_QMI_TMD if NET 240 select QCOM_RPROC_COMMON 241 select QCOM_SCM 242 select QCOM_PAS 243 help 244 Say y here to support the TrustZone based Peripheral Image Loader for 245 the Qualcomm remote processors. This is commonly used to control 246 subsystems such as ADSP (Audio DSP), CDSP (Compute DSP), MPSS (Modem 247 Peripheral SubSystem), and SLPI (Sensor Low Power Island). 248 249config QCOM_Q6V5_WCSS 250 tristate "Qualcomm Hexagon based WCSS Peripheral Image Loader" 251 depends on OF && ARCH_QCOM 252 depends on QCOM_SMEM 253 depends on RPMSG_QCOM_SMD || RPMSG_QCOM_SMD=n 254 depends on RPMSG_QCOM_GLINK_SMEM || RPMSG_QCOM_GLINK_SMEM=n 255 depends on QCOM_SYSMON || QCOM_SYSMON=n 256 depends on RPMSG_QCOM_GLINK || RPMSG_QCOM_GLINK=n 257 depends on QCOM_AOSS_QMP || QCOM_AOSS_QMP=n 258 select MFD_SYSCON 259 select QCOM_MDT_LOADER 260 select QCOM_PIL_INFO 261 select QCOM_Q6V5_COMMON 262 select QCOM_RPROC_COMMON 263 select QCOM_SCM 264 help 265 Say y here to support the Qualcomm Peripheral Image Loader for the 266 Hexagon V5 based WCSS remote processors on e.g. IPQ8074. This is 267 a non-TrustZone wireless subsystem. 268 269config QCOM_SYSMON 270 tristate "Qualcomm sysmon driver" 271 depends on RPMSG 272 depends on ARCH_QCOM 273 depends on NET 274 select QCOM_QMI_HELPERS 275 help 276 The sysmon driver implements a sysmon QMI client and a handler for 277 the sys_mon SMD and GLINK channel, which are used for graceful 278 shutdown, retrieving failure information and propagating information 279 about other subsystems being shut down. 280 281 Say y here if your system runs firmware on any other subsystems, e.g. 282 modem or DSP. 283 284config QCOM_WCNSS_PIL 285 tristate "Qualcomm WCNSS Peripheral Image Loader" 286 depends on OF && ARCH_QCOM 287 depends on RPMSG_QCOM_SMD || RPMSG_QCOM_SMD=n 288 depends on RPMSG_QCOM_GLINK_SMEM || RPMSG_QCOM_GLINK_SMEM=n 289 depends on QCOM_SMEM 290 depends on QCOM_SYSMON || QCOM_SYSMON=n 291 depends on RPMSG_QCOM_GLINK || RPMSG_QCOM_GLINK=n 292 select QCOM_MDT_LOADER 293 select QCOM_PIL_INFO 294 select QCOM_RPROC_COMMON 295 select QCOM_PAS 296 help 297 Say y here to support the Peripheral Image Loader for loading WCNSS 298 firmware and boot the core on e.g. MSM8974, MSM8916. The firmware is 299 verified and booted with the help of the Peripheral Authentication 300 System (PAS) in TrustZone. 301 302config RCAR_REMOTEPROC 303 tristate "Renesas R-Car Gen3 remoteproc support" 304 depends on ARCH_RENESAS || COMPILE_TEST 305 help 306 Say y here to support R-Car realtime processor via the 307 remote processor framework. An ELF firmware can be loaded 308 thanks to sysfs remoteproc entries. The remote processor 309 can be started and stopped. 310 This can be either built-in or a loadable module. 311 If compiled as module (M), the module name is rcar_rproc. 312 313config ST_REMOTEPROC 314 tristate "ST remoteproc support" 315 depends on ARCH_STI 316 select MAILBOX 317 select STI_MBOX 318 help 319 Say y here to support ST's adjunct processors via the remote 320 processor framework. 321 This can be either built-in or a loadable module. 322 323config ST_SLIM_REMOTEPROC 324 tristate 325 326config STM32_RPROC 327 tristate "STM32 remoteproc support" 328 depends on ARCH_STM32 || COMPILE_TEST 329 select MAILBOX 330 help 331 Say y here to support STM32 MCU processors via the 332 remote processor framework. 333 334 You want to say y here in order to enable AMP 335 use-cases to run on your platform (dedicated firmware could be 336 offloaded to remote MCU processors using this framework). 337 338 This can be either built-in or a loadable module. 339 340config TI_K3_DSP_REMOTEPROC 341 tristate "TI K3 DSP remoteproc support" 342 depends on ARCH_K3 || COMPILE_TEST 343 depends on TI_SCI_PROTOCOL || (COMPILE_TEST && TI_SCI_PROTOCOL=n) 344 depends on OMAP2PLUS_MBOX 345 help 346 Say m here to support TI's C66x and C71x DSP remote processor 347 subsystems on various TI K3 family of SoCs through the remote 348 processor framework. 349 350 It's safe to say N here if you're not interested in utilizing 351 the DSP slave processors. 352 353config TI_K3_M4_REMOTEPROC 354 tristate "TI K3 M4 remoteproc support" 355 depends on ARCH_K3 || COMPILE_TEST 356 depends on TI_SCI_PROTOCOL || (COMPILE_TEST && TI_SCI_PROTOCOL=n) 357 depends on OMAP2PLUS_MBOX 358 help 359 Say m here to support TI's M4 remote processor subsystems 360 on various TI K3 family of SoCs through the remote processor 361 framework. 362 363 It's safe to say N here if you're not interested in utilizing 364 a remote processor. 365 366config TI_K3_R5_REMOTEPROC 367 tristate "TI K3 R5 remoteproc support" 368 depends on ARCH_K3 || COMPILE_TEST 369 depends on TI_SCI_PROTOCOL || (COMPILE_TEST && TI_SCI_PROTOCOL=n) 370 depends on OMAP2PLUS_MBOX 371 help 372 Say m here to support TI's R5F remote processor subsystems 373 on various TI K3 family of SoCs through the remote processor 374 framework. 375 376 It's safe to say N here if you're not interested in utilizing 377 a slave processor. 378 379config XLNX_R5_REMOTEPROC 380 tristate "Xilinx R5 remoteproc support" 381 depends on PM && ARCH_ZYNQMP 382 select ZYNQMP_FIRMWARE 383 select RPMSG_VIRTIO 384 select MAILBOX 385 select ZYNQMP_IPI_MBOX 386 help 387 Say y or m here to support Xilinx R5 remote processors via the remote 388 processor framework. 389 390 It's safe to say N if not interested in using RPU r5f cores. 391 392endif # REMOTEPROC 393 394endmenu 395