1menu "Remoteproc drivers" 2 3# REMOTEPROC gets selected by whoever wants it 4config REMOTEPROC 5 tristate 6 depends on HAS_DMA 7 select CRC32 8 select FW_LOADER 9 select VIRTIO 10 select VIRTUALIZATION 11 12config OMAP_REMOTEPROC 13 tristate "OMAP remoteproc support" 14 depends on HAS_DMA 15 depends on ARCH_OMAP4 || SOC_OMAP5 16 depends on OMAP_IOMMU 17 select REMOTEPROC 18 select MAILBOX 19 select OMAP2PLUS_MBOX 20 select RPMSG 21 help 22 Say y here to support OMAP's remote processors (dual M3 23 and DSP on OMAP4) via the remote processor framework. 24 25 Currently only supported on OMAP4. 26 27 Usually you want to say y here, in order to enable multimedia 28 use-cases to run on your platform (multimedia codecs are 29 offloaded to remote DSP processors using this framework). 30 31 It's safe to say n here if you're not interested in multimedia 32 offloading or just want a bare minimum kernel. 33 34config STE_MODEM_RPROC 35 tristate "STE-Modem remoteproc support" 36 depends on HAS_DMA 37 select REMOTEPROC 38 default n 39 help 40 Say y or m here to support STE-Modem shared memory driver. 41 This can be either built-in or a loadable module. 42 If unsure say N. 43 44config DA8XX_REMOTEPROC 45 tristate "DA8xx/OMAP-L13x remoteproc support" 46 depends on ARCH_DAVINCI_DA8XX 47 select CMA 48 select REMOTEPROC 49 select RPMSG 50 help 51 Say y here to support DA8xx/OMAP-L13x remote processors via the 52 remote processor framework. 53 54 You want to say y here in order to enable AMP 55 use-cases to run on your platform (multimedia codecs are 56 offloaded to remote DSP processors using this framework). 57 58 This module controls the name of the firmware file that gets 59 loaded on the DSP. This file must reside in the /lib/firmware 60 directory. It can be specified via the module parameter 61 da8xx_fw_name=<filename>, and if not specified will default to 62 "rproc-dsp-fw". 63 64 It's safe to say n here if you're not interested in multimedia 65 offloading. 66 67endmenu 68