Home
last modified time | relevance | path

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

1234

/Linux-v5.15/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 "i.MX remoteproc support"
38 tristate "Ingenic JZ47xx VPU remoteproc support"
57 tristate "OMAP remoteproc support"
76 bool "OMAP remoteproc watchdog timer"
88 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 …]
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");
Dqcom_common.c14 #include <linux/remoteproc.h>
15 #include <linux/remoteproc/qcom_rproc.h>
211 * @ssr_name: identifier of the associated remoteproc for ssr notifications
253 * @rproc: remoteproc handle
256 * Register all segments of the ELF in the remoteproc coredump segment list
379 * remoteproc associated with @name. The notifier block's callback
472 * registered listeners for the remoteproc when it's SSR events occur
508 MODULE_DESCRIPTION("Qualcomm Remoteproc helper driver");
Dremoteproc_sysfs.c6 #include <linux/remoteproc.h>
97 * default: When the remoteproc crashes the entire coredump will be
252 .name = "remoteproc",
258 /* create remoteproc device class for sysfs */ in rproc_init_sysfs()
262 pr_err("remoteproc: unable to register class\n"); in rproc_init_sysfs()
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");
Dremoteproc_cdev.c3 * Character device interface driver for Remoteproc framework.
12 #include <linux/remoteproc.h>
134 ret = alloc_chrdev_region(&rproc_major, 0, NUM_RPROC_DEVICES, "remoteproc"); in rproc_init_cdev()
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()
Dpru_rproc.c3 * PRU-ICSS remoteproc driver for various TI SoCs
20 #include <linux/remoteproc.h>
107 * struct pru_rproc - PRU remoteproc structure
111 * @rproc: remoteproc pointer for this PRU core
253 * The entries are created only if the parent remoteproc debugfs directory
254 * exists, and will be cleaned up by the remoteproc core.
323 * for these mappings for a given PRU remoteproc is always its in pru_handle_intrmap()
505 * Provide address translations for only PRU Data RAMs through the remoteproc
641 /* skip the memzero logic performed by remoteproc ELF loader */ in pru_rproc_load_elf_segments()
809 * remoteproc sysfs interface or through the equivalent kernel API. in pru_rproc_probe()
Dremoteproc_core.c33 #include <linux/remoteproc.h>
60 /* Unique indices for remoteproc devices */
165 * rproc_da_to_va() - lookup the kernel virtual address for a remoteproc address
167 * @da: remoteproc device address to translate
184 * translations on the internal remoteproc memory regions through a platform
425 * remoteproc core, otherwise it is NULL. in rproc_free_vring()
1665 * the remoteproc core. That cache table should be used for in rproc_reset_rsc_table_on_stop()
1889 * rproc_trigger_recovery() - recover a remoteproc
1894 * remoteproc functional again.
2103 * remoteproc core
[all …]
Dti_sci_proc.h19 * @proc_id: processor id for the consumer remoteproc device
20 * @host_id: host id to pass the control over for this consumer remoteproc
Dmtk_common.h12 #include <linux/remoteproc.h>
13 #include <linux/remoteproc/mtk_scp.h>
Dingenic_rproc.c3 * Ingenic JZ47xx remoteproc driver
14 #include <linux/remoteproc.h>
53 * struct vpu - Ingenic VPU remoteproc private structure
Dremoteproc_virtio.c15 #include <linux/remoteproc.h>
40 * rproc_vq_interrupt() - tell remoteproc that a virtqueue is interrupted
219 * Packed ring isn't enabled on remoteproc for now, in rproc_transport_features()
220 * because remoteproc uses vring_new_virtqueue() which in rproc_transport_features()
/Linux-v5.15/include/linux/remoteproc/
Dqcom_rproc.h7 * enum qcom_ssr_notify_type - Startup/Shutdown events related to a remoteproc
10 * @QCOM_SSR_BEFORE_POWERUP: Remoteproc about to start (prepare stage)
11 * @QCOM_SSR_AFTER_POWERUP: Remoteproc is running (start stage)
12 * @QCOM_SSR_BEFORE_SHUTDOWN: Remoteproc crashed or shutting down (stop stage)
13 * @QCOM_SSR_AFTER_SHUTDOWN: Remoteproc is down (unprepare stage)
/Linux-v5.15/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
/Linux-v5.15/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 …]
/Linux-v5.15/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
87 remoteproc device. This is variable and describes the memories shared with
88 the remote processor (e.g. remoteproc firmware and carveouts, rpmsg
114 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
99 with the remoteproc device. The reserved memory node
106 Address space for any remoteproc memories present on
136 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
Dwkup_m3_rproc.txt1 TI Wakeup M3 Remoteproc Driver
7 binary to accomplish this. The wkup_m3 remoteproc driver handles the loading of
/Linux-v5.15/drivers/media/platform/mtk-vcodec/
Dmtk_vcodec_fw.h6 #include <linux/remoteproc.h>
7 #include <linux/remoteproc/mtk_scp.h>
/Linux-v5.15/drivers/rpmsg/
Dqcom_glink_ssr.c12 #include <linux/remoteproc/qcom_rproc.h>
62 * qcom_glink_ssr_notify() - notify GLINK SSR about stopped remoteproc
63 * @ssr_name: name of the remoteproc that has been stopped
/Linux-v5.15/include/linux/
Dremoteproc.h59 * of specific remoteproc configuration. Other entries require the host to
205 * want remoteproc implementations to provide us ranges of physical addresses
286 * By providing this resource entry, the firmware essentially asks remoteproc
292 * the Linux side which is running remoteproc to control the remote
500 * @dev: virtual device for refcounting and common remoteproc behavior
531 * @cdev_put_on_release: flag to indicate if remoteproc should be shutdown on @char_dev release
574 * struct rproc_subdev - subdevice tied to a remoteproc
596 * struct rproc_vring - remoteproc vring state
616 * struct rproc_vdev - remoteproc state for a supported virtio device

1234