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 IMX_REMOTEPROC
27	tristate "IMX6/7 remoteproc support"
28	depends on ARCH_MXC
29	help
30	  Say y here to support iMX's remote processors (Cortex M4
31	  on iMX7D) via the remote processor framework.
32
33	  It's safe to say N here.
34
35config INGENIC_VPU_RPROC
36	tristate "Ingenic JZ47xx VPU remoteproc support"
37	depends on MIPS || COMPILE_TEST
38	help
39	  Say y or m here to support the VPU in the JZ47xx SoCs from Ingenic.
40
41	  This can be either built-in or a loadable module.
42	  If unsure say N.
43
44config MTK_SCP
45	tristate "Mediatek SCP support"
46	depends on ARCH_MEDIATEK || COMPILE_TEST
47	select RPMSG_MTK_SCP
48	help
49	  Say y here to support Mediatek's System Companion Processor (SCP) via
50	  the remote processor framework.
51
52	  It's safe to say N here.
53
54config OMAP_REMOTEPROC
55	tristate "OMAP remoteproc support"
56	depends on ARCH_OMAP4 || SOC_OMAP5 || SOC_DRA7XX
57	depends on OMAP_IOMMU
58	select MAILBOX
59	select OMAP2PLUS_MBOX
60	help
61	  Say y here to support OMAP's remote processors (dual M3
62	  and DSP on OMAP4) via the remote processor framework.
63
64	  Currently only supported on OMAP4.
65
66	  Usually you want to say Y here, in order to enable multimedia
67	  use-cases to run on your platform (multimedia codecs are
68	  offloaded to remote DSP processors using this framework).
69
70	  It's safe to say N here if you're not interested in multimedia
71	  offloading or just want a bare minimum kernel.
72
73config OMAP_REMOTEPROC_WATCHDOG
74	bool "OMAP remoteproc watchdog timer"
75	depends on OMAP_REMOTEPROC
76	default n
77	help
78	  Say Y here to enable watchdog timer for remote processors.
79
80	  This option controls the watchdog functionality for the remote
81	  processors in OMAP. Dedicated OMAP DMTimers are used by the remote
82	  processors and triggers the timer interrupt upon a watchdog
83	  detection.
84
85config WKUP_M3_RPROC
86	tristate "AMx3xx Wakeup M3 remoteproc support"
87	depends on SOC_AM33XX || SOC_AM43XX
88	help
89	  Say y here to support Wakeup M3 remote processor on TI AM33xx
90	  and AM43xx family of SoCs.
91
92	  Required for Suspend-to-RAM on AM33xx and AM43xx SoCs. Also needed
93	  for deep CPUIdle states on AM33xx SoCs. Allows for loading of the
94	  firmware onto these remote processors.
95	  If unsure say N.
96
97config DA8XX_REMOTEPROC
98	tristate "DA8xx/OMAP-L13x remoteproc support"
99	depends on ARCH_DAVINCI_DA8XX
100	depends on DMA_CMA
101	help
102	  Say y here to support DA8xx/OMAP-L13x remote processors via the
103	  remote processor framework.
104
105	  You want to say y here in order to enable AMP
106	  use-cases to run on your platform (multimedia codecs are
107	  offloaded to remote DSP processors using this framework).
108
109	  This module controls the name of the firmware file that gets
110	  loaded on the DSP.  This file must reside in the /lib/firmware
111	  directory.  It can be specified via the module parameter
112	  da8xx_fw_name=<filename>, and if not specified will default to
113	  "rproc-dsp-fw".
114
115	  It's safe to say n here if you're not interested in multimedia
116	  offloading.
117
118config KEYSTONE_REMOTEPROC
119	tristate "Keystone Remoteproc support"
120	depends on ARCH_KEYSTONE
121	help
122	  Say Y here here to support Keystone remote processors (DSP)
123	  via the remote processor framework.
124
125	  It's safe to say N here if you're not interested in the Keystone
126	  DSPs or just want to use a bare minimum kernel.
127
128config QCOM_PIL_INFO
129	tristate
130
131config QCOM_RPROC_COMMON
132	tristate
133
134config QCOM_Q6V5_COMMON
135	tristate
136	depends on ARCH_QCOM
137	depends on QCOM_SMEM
138
139config QCOM_Q6V5_ADSP
140	tristate "Qualcomm Technology Inc ADSP Peripheral Image Loader"
141	depends on OF && ARCH_QCOM
142	depends on QCOM_SMEM
143	depends on RPMSG_QCOM_SMD || (COMPILE_TEST && RPMSG_QCOM_SMD=n)
144	depends on RPMSG_QCOM_GLINK_SMEM || RPMSG_QCOM_GLINK_SMEM=n
145	depends on QCOM_SYSMON || QCOM_SYSMON=n
146	select MFD_SYSCON
147	select QCOM_PIL_INFO
148	select QCOM_MDT_LOADER
149	select QCOM_Q6V5_COMMON
150	select QCOM_RPROC_COMMON
151	help
152	  Say y here to support the Peripheral Image Loader
153	  for the Qualcomm Technology Inc. ADSP remote processors.
154
155config QCOM_Q6V5_MSS
156	tristate "Qualcomm Hexagon V5 self-authenticating modem subsystem support"
157	depends on OF && ARCH_QCOM
158	depends on QCOM_SMEM
159	depends on RPMSG_QCOM_SMD || (COMPILE_TEST && RPMSG_QCOM_SMD=n)
160	depends on RPMSG_QCOM_GLINK_SMEM || RPMSG_QCOM_GLINK_SMEM=n
161	depends on QCOM_SYSMON || QCOM_SYSMON=n
162	select MFD_SYSCON
163	select QCOM_MDT_LOADER
164	select QCOM_PIL_INFO
165	select QCOM_Q6V5_COMMON
166	select QCOM_RPROC_COMMON
167	select QCOM_SCM
168	help
169	  Say y here to support the Qualcomm self-authenticating modem
170	  subsystem based on Hexagon V5.
171
172config QCOM_Q6V5_PAS
173	tristate "Qualcomm Hexagon v5 Peripheral Authentication Service support"
174	depends on OF && ARCH_QCOM
175	depends on QCOM_SMEM
176	depends on RPMSG_QCOM_SMD || (COMPILE_TEST && RPMSG_QCOM_SMD=n)
177	depends on RPMSG_QCOM_GLINK_SMEM || RPMSG_QCOM_GLINK_SMEM=n
178	depends on QCOM_SYSMON || QCOM_SYSMON=n
179	select MFD_SYSCON
180	select QCOM_PIL_INFO
181	select QCOM_MDT_LOADER
182	select QCOM_Q6V5_COMMON
183	select QCOM_RPROC_COMMON
184	select QCOM_SCM
185	help
186	  Say y here to support the TrustZone based Peripherial Image Loader
187	  for the Qualcomm Hexagon v5 based remote processors. This is commonly
188	  used to control subsystems such as ADSP, Compute and Sensor.
189
190config QCOM_Q6V5_WCSS
191	tristate "Qualcomm Hexagon based WCSS Peripheral Image Loader"
192	depends on OF && ARCH_QCOM
193	depends on QCOM_SMEM
194	depends on RPMSG_QCOM_SMD || (COMPILE_TEST && RPMSG_QCOM_SMD=n)
195	depends on RPMSG_QCOM_GLINK_SMEM || RPMSG_QCOM_GLINK_SMEM=n
196	depends on QCOM_SYSMON || QCOM_SYSMON=n
197	select MFD_SYSCON
198	select QCOM_MDT_LOADER
199	select QCOM_PIL_INFO
200	select QCOM_Q6V5_COMMON
201	select QCOM_RPROC_COMMON
202	select QCOM_SCM
203	help
204	  Say y here to support the Qualcomm Peripheral Image Loader for the
205	  Hexagon V5 based WCSS remote processors.
206
207config QCOM_SYSMON
208	tristate "Qualcomm sysmon driver"
209	depends on RPMSG
210	depends on ARCH_QCOM
211	depends on NET
212	select QCOM_QMI_HELPERS
213	help
214	  The sysmon driver implements a sysmon QMI client and a handler for
215	  the sys_mon SMD and GLINK channel, which are used for graceful
216	  shutdown, retrieving failure information and propagating information
217	  about other subsystems being shut down.
218
219	  Say y here if your system runs firmware on any other subsystems, e.g.
220	  modem or DSP.
221
222config QCOM_WCNSS_PIL
223	tristate "Qualcomm WCNSS Peripheral Image Loader"
224	depends on OF && ARCH_QCOM
225	depends on RPMSG_QCOM_SMD || (COMPILE_TEST && RPMSG_QCOM_SMD=n)
226	depends on RPMSG_QCOM_GLINK_SMEM || RPMSG_QCOM_GLINK_SMEM=n
227	depends on QCOM_SMEM
228	depends on QCOM_SYSMON || QCOM_SYSMON=n
229	select QCOM_MDT_LOADER
230	select QCOM_PIL_INFO
231	select QCOM_RPROC_COMMON
232	select QCOM_SCM
233	help
234	  Say y here to support the Peripheral Image Loader for the Qualcomm
235	  Wireless Connectivity Subsystem.
236
237config ST_REMOTEPROC
238	tristate "ST remoteproc support"
239	depends on ARCH_STI
240	select MAILBOX
241	select STI_MBOX
242	help
243	  Say y here to support ST's adjunct processors via the remote
244	  processor framework.
245	  This can be either built-in or a loadable module.
246
247config ST_SLIM_REMOTEPROC
248	tristate
249
250config STM32_RPROC
251	tristate "STM32 remoteproc support"
252	depends on ARCH_STM32
253	depends on REMOTEPROC
254	select MAILBOX
255	help
256	  Say y here to support STM32 MCU processors via the
257	  remote processor framework.
258
259	  You want to say y here in order to enable AMP
260	  use-cases to run on your platform (dedicated firmware could be
261	  offloaded to remote MCU processors using this framework).
262
263	  This can be either built-in or a loadable module.
264
265config TI_K3_DSP_REMOTEPROC
266	tristate "TI K3 DSP remoteproc support"
267	depends on ARCH_K3
268	select MAILBOX
269	select OMAP2PLUS_MBOX
270	help
271	  Say m here to support TI's C66x and C71x DSP remote processor
272	  subsystems on various TI K3 family of SoCs through the remote
273	  processor framework.
274
275	  It's safe to say N here if you're not interested in utilizing
276	  the DSP slave processors.
277
278config TI_K3_R5_REMOTEPROC
279	tristate "TI K3 R5 remoteproc support"
280	depends on ARCH_K3
281	select MAILBOX
282	select OMAP2PLUS_MBOX
283	help
284	  Say m here to support TI's R5F remote processor subsystems
285	  on various TI K3 family of SoCs through the remote processor
286	  framework.
287
288	  It's safe to say N here if you're not interested in utilizing
289	  a slave processor.
290
291endif # REMOTEPROC
292
293endmenu
294