Home
last modified time | relevance | path

Searched full:remoteproc (Results 1 – 25 of 143) sorted by relevance

123456

/kernel/linux/linux-5.10/drivers/remoteproc/
DKconfig2 menu "Remoteproc drivers"
4 config REMOTEPROC config
15 if REMOTEPROC
18 bool "Remoteproc character device interface"
20 Say y here to have a character device interface for the remoteproc
27 tristate "IMX6/7 remoteproc support"
36 tristate "Ingenic JZ47xx VPU remoteproc support"
55 tristate "OMAP remoteproc support"
74 bool "OMAP remoteproc watchdog timer"
86 tristate "AMx3xx Wakeup M3 remoteproc support"
[all …]
DMakefile6 obj-$(CONFIG_REMOTEPROC) += remoteproc.o
7 remoteproc-y := remoteproc_core.o
8 remoteproc-y += remoteproc_coredump.o
9 remoteproc-y += remoteproc_debugfs.o
10 remoteproc-y += remoteproc_sysfs.o
11 remoteproc-y += remoteproc_virtio.o
12 remoteproc-y += remoteproc_elf_loader.o
Domap_remoteproc.c28 #include <linux/remoteproc.h>
99 * @fck: functional clock for the remoteproc
141 * omap_rproc_request_timer() - request a timer for a remoteproc
147 * a remoteproc. The returned handle is stored in the .odt field of the
173 /* clean counter, remoteproc code will set the value */ in omap_rproc_request_timer()
180 * omap_rproc_start_timer() - start a timer for a remoteproc
183 * This helper function is used to start a timer associated with a remoteproc,
196 * omap_rproc_stop_timer() - stop a timer for a remoteproc
200 * remoteproc, and needs to be called either during a device shutdown
213 * omap_rproc_release_timer() - release a timer for a remoteproc
[all …]
Dqcom_common.c14 #include <linux/remoteproc.h>
15 #include <linux/remoteproc/qcom_rproc.h>
65 * @ssr_name: identifier of the associated remoteproc for ssr notifications
107 * @rproc: remoteproc handle
110 * Register all segments of the ELF in the remoteproc coredump segment list
233 * remoteproc associated with @name. The notifier block's callback
326 * registered listeners for the remoteproc when it's SSR events occur
362 MODULE_DESCRIPTION("Qualcomm Remoteproc helper driver");
Dkeystone_remoteproc.c3 * TI Keystone DSP remoteproc driver
20 #include <linux/remoteproc.h>
44 * @rproc: remoteproc device handle
99 * Process the remoteproc exceptions
107 * to the remoteproc driver core, to trigger a recovery.
121 * This function is executed upon scheduling of the keystone remoteproc
246 * can be used either by the remoteproc core for loading (when using kernel
247 * remoteproc loader), or by any rpmsg bus drivers.
459 dev_err(dev, "failed to add register device with remoteproc core, status = %d\n", in keystone_rproc_probe()
514 MODULE_DESCRIPTION("TI Keystone DSP Remoteproc driver");
Dremoteproc_sysfs.c6 #include <linux/remoteproc.h>
97 * default: When the remoteproc crashes the entire coredump will be
276 .name = "remoteproc",
282 /* create remoteproc device class for sysfs */ in rproc_init_sysfs()
286 pr_err("remoteproc: unable to register class\n"); in rproc_init_sysfs()
Dremoteproc_cdev.c3 * Character device interface driver for Remoteproc framework.
12 #include <linux/remoteproc.h>
121 ret = alloc_chrdev_region(&rproc_major, 0, NUM_RPROC_DEVICES, "remoteproc"); in rproc_init_cdev()
Dti_k3_dsp_remoteproc.c16 #include <linux/remoteproc.h>
67 * @rproc: remoteproc device handle
104 * and we let remoteproc core handle it.
123 * remoteproc detected an exception, but error recovery is not in k3_dsp_rproc_mbox_callback()
224 * internal RAMs. The .prepare() ops is invoked by remoteproc core before any
249 * by the remoteproc core after the remoteproc is stopped to balance the global
354 * can be used either by the remoteproc core for loading (when using kernel
355 * remoteproc loader), or by any rpmsg bus drivers.
691 dev_err(dev, "failed to add register device with remoteproc core, status = %d\n", in k3_dsp_rproc_probe()
787 MODULE_DESCRIPTION("TI K3 DSP Remoteproc driver");
Dst_slim_rproc.c17 #include <linux/remoteproc.h>
18 #include <linux/remoteproc/st_slim_rproc.h>
110 * Remoteproc slim specific device handlers
289 /* Register as a remoteproc device */ in st_slim_rproc_alloc()
292 dev_err(dev, "registration of slim remoteproc failed\n"); in st_slim_rproc_alloc()
/kernel/linux/linux-4.19/drivers/remoteproc/
DKconfig1 menu "Remoteproc drivers"
3 config REMOTEPROC config
14 if REMOTEPROC
17 tristate "IMX6/7 remoteproc support"
26 tristate "OMAP remoteproc support"
45 tristate "AMx3xx Wakeup M3 remoteproc support"
57 tristate "DA8xx/OMAP-L13x remoteproc support"
78 tristate "Keystone Remoteproc support"
172 tristate "ST remoteproc support"
184 endif # REMOTEPROC
DMakefile6 obj-$(CONFIG_REMOTEPROC) += remoteproc.o
7 remoteproc-y := remoteproc_core.o
8 remoteproc-y += remoteproc_debugfs.o
9 remoteproc-y += remoteproc_sysfs.o
10 remoteproc-y += remoteproc_virtio.o
11 remoteproc-y += remoteproc_elf_loader.o
Dkeystone_remoteproc.c2 * TI Keystone DSP remoteproc driver
28 #include <linux/remoteproc.h>
52 * @rproc: remoteproc device handle
107 * Process the remoteproc exceptions
115 * to the remoteproc driver core, to trigger a recovery.
129 * This function is executed upon scheduling of the keystone remoteproc
254 * can be used either by the remoteproc core for loading (when using kernel
255 * remoteproc loader), or by any rpmsg bus drivers.
471 dev_err(dev, "failed to add register device with remoteproc core, status = %d\n", in keystone_rproc_probe()
526 MODULE_DESCRIPTION("TI Keystone DSP Remoteproc driver");
Dremoteproc_sysfs.c14 #include <linux/remoteproc.h>
140 .name = "remoteproc",
146 /* create remoteproc device class for sysfs */ in rproc_init_sysfs()
150 pr_err("remoteproc: unable to register class\n"); in rproc_init_sysfs()
Dqcom_common.c22 #include <linux/remoteproc.h>
91 * @rproc: remoteproc handle
94 * Register all segments of the ELF in the remoteproc coredump segment list
225 * registered listeners in the system as the remoteproc is shut down.
248 MODULE_DESCRIPTION("Qualcomm Remoteproc helper driver");
Dst_slim_rproc.c21 #include <linux/remoteproc.h>
22 #include <linux/remoteproc/st_slim_rproc.h>
114 * Remoteproc slim specific device handlers
293 /* Register as a remoteproc device */ in st_slim_rproc_alloc()
296 dev_err(dev, "registration of slim remoteproc failed\n"); in st_slim_rproc_alloc()
/kernel/linux/linux-5.10/include/linux/remoteproc/
Dqcom_rproc.h9 * enum qcom_ssr_notify_type - Startup/Shutdown events related to a remoteproc
12 * @QCOM_SSR_BEFORE_POWERUP: Remoteproc about to start (prepare stage)
13 * @QCOM_SSR_AFTER_POWERUP: Remoteproc is running (start stage)
14 * @QCOM_SSR_BEFORE_SHUTDOWN: Remoteproc crashed or shutting down (stop stage)
15 * @QCOM_SSR_AFTER_SHUTDOWN: Remoteproc is down (unprepare stage)
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-class-remoteproc1 What: /sys/class/remoteproc/.../firmware
10 stopped (using /sys/class/remoteproc/.../state) and write a new filename.
12 What: /sys/class/remoteproc/.../state
46 /sys/class/remoteproc/.../firmware. The remote processor should
52 What: /sys/class/remoteproc/.../name
62 What: /sys/class/remoteproc/.../coredump
86 What: /sys/class/remoteproc/.../recovery
/kernel/linux/linux-4.19/Documentation/
Dremoteproc.txt17 The remoteproc framework allows different platforms/architectures to
22 platform-specific remoteproc drivers only need to provide a few low-level
28 remoteproc will add those devices. This makes it possible to reuse the
83 #include <linux/remoteproc.h>
150 Register @rproc with the remoteproc framework, after it has been
185 Report a crash in a remoteproc
189 non-remoteproc driver. This function can be called from atomic/interrupt
195 These callbacks should be provided by platform-specific remoteproc
210 Every remoteproc implementation should at least provide the ->start and ->stop
216 The boot address, in case needed, can be found in rproc->bootaddr (remoteproc
[all …]
/kernel/linux/linux-5.10/Documentation/staging/
Dremoteproc.rst17 The remoteproc framework allows different platforms/architectures to
22 platform-specific remoteproc drivers only need to provide a few low-level
28 remoteproc will add those devices. This makes it possible to reuse the
83 #include <linux/remoteproc.h>
150 Register @rproc with the remoteproc framework, after it has been
185 Report a crash in a remoteproc
189 non-remoteproc driver. This function can be called from atomic/interrupt
195 These callbacks should be provided by platform-specific remoteproc
210 Every remoteproc implementation should at least provide the ->start and ->stop
216 The boot address, in case needed, can be found in rproc->bootaddr (remoteproc
[all …]
/kernel/linux/linux-4.19/Documentation/ABI/testing/
Dsysfs-class-remoteproc1 What: /sys/class/remoteproc/.../firmware
10 stopped (using /sys/class/remoteproc/.../state) and write a new filename.
12 What: /sys/class/remoteproc/.../state
46 /sys/class/remoteproc/.../firmware. The remote processor should
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/remoteproc/
Dst,stm32-rproc.yaml4 $id: "http://devicetree.org/schemas/remoteproc/st,stm32-rproc.yaml#"
10 This document defines the binding for the remoteproc component that loads and
85 remoteproc device. This is variable and describes the memories shared with
86 the remote processor (e.g. remoteproc firmware and carveouts, rpmsg
102 If defined, when remoteproc is probed, it loads the default firmware and
Dti,omap-remoteproc.yaml4 $id: http://devicetree.org/schemas/remoteproc/ti,omap-remoteproc.yaml#
7 title: OMAP4+ Remoteproc Devices
96 with the remoteproc device. The reserved memory node
103 Address space for any remoteproc memories present on
134 Custom autosuspend delay for the remoteproc in milliseconds.
Dqcom,pil-info.yaml4 $id: http://devicetree.org/schemas/remoteproc/qcom,pil-info.yaml#
14 used for communicating remoteproc relocation information to post mortem
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/
Dqcom,ipa.yaml116 modem-remoteproc:
119 This defines the phandle to the remoteproc node representing
139 - modem-remoteproc
172 modem-remoteproc = <&mss_pil>;
/kernel/linux/linux-5.10/drivers/media/platform/mtk-vcodec/
Dmtk_vcodec_fw.h6 #include <linux/remoteproc.h>
7 #include <linux/remoteproc/mtk_scp.h>

123456