Searched full:remoteproc (Results 1 – 25 of 58) sorted by relevance
123
| /Documentation/ABI/testing/ |
| D | sysfs-class-remoteproc | 1 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
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | renesas,rcar-rproc.yaml | 4 $id: http://devicetree.org/schemas/remoteproc/renesas,rcar-rproc.yaml#
13 This document defines the bindings for the remoteproc component that loads and
31 remoteproc device. This is variable and describes the memories shared with
32 the remote processor (e.g. remoteproc firmware and carveouts, rpmsg
|
| D | qcom,pas-common.yaml | 4 $id: http://devicetree.org/schemas/remoteproc/qcom,pas-common.yaml#
67 $ref: /schemas/remoteproc/qcom,smd-edge.yaml#
74 $ref: /schemas/remoteproc/qcom,glink-edge.yaml#
|
| D | qcom,qcs404-pas.yaml | 4 $id: http://devicetree.org/schemas/remoteproc/qcom,qcs404-pas.yaml#
58 - $ref: /schemas/remoteproc/qcom,pas-common.yaml#
67 remoteproc@c700000 {
|
| D | qcom,pil-info.yaml | 4 $id: http://devicetree.org/schemas/remoteproc/qcom,pil-info.yaml#
14 used for communicating remoteproc relocation information to post mortem
|
| D | qcom,sdx55-pas.yaml | 4 $id: http://devicetree.org/schemas/remoteproc/qcom,sdx55-pas.yaml#
68 - $ref: /schemas/remoteproc/qcom,pas-common.yaml#
78 remoteproc@4080000 {
|
| D | xlnx,zynqmp-r5fss.yaml | 4 $id: http://devicetree.org/schemas/remoteproc/xlnx,zynqmp-r5fss.yaml#
90 remoteproc device. This is variable and describes the memories shared with
91 the remote processor (e.g. remoteproc firmware and carveouts, rpmsg
115 remoteproc {
|
| D | st,stm32-rproc.yaml | 4 $id: http://devicetree.org/schemas/remoteproc/st,stm32-rproc.yaml#
10 This document defines the binding for the remoteproc component that loads and
100 remoteproc device. This is variable and describes the memories shared with
101 the remote processor (e.g. remoteproc firmware and carveouts, rpmsg
139 If defined, when remoteproc is probed, it loads the default firmware and
|
| D | qcom,sc8280xp-pas.yaml | 4 $id: http://devicetree.org/schemas/remoteproc/qcom,sc8280xp-pas.yaml#
54 - $ref: /schemas/remoteproc/qcom,pas-common.yaml#
108 remoteproc@3000000 {
|
| D | qcom,sm6115-pas.yaml | 4 $id: http://devicetree.org/schemas/remoteproc/qcom,sm6115-pas.yaml#
59 - $ref: /schemas/remoteproc/qcom,pas-common.yaml#
122 remoteproc@ab00000 {
|
| D | qcom,sc7180-pas.yaml | 4 $id: http://devicetree.org/schemas/remoteproc/qcom,sc7180-pas.yaml#
73 - $ref: /schemas/remoteproc/qcom,pas-common.yaml#
101 remoteproc@4080000 {
|
| D | qcom,sm6350-pas.yaml | 4 $id: http://devicetree.org/schemas/remoteproc/qcom,sm6350-pas.yaml#
54 - $ref: /schemas/remoteproc/qcom,pas-common.yaml#
131 remoteproc@3000000 {
|
| D | qcom,glink-edge.yaml | 4 $id: http://devicetree.org/schemas/remoteproc/qcom,glink-edge.yaml#
83 remoteproc@8a00000 {
|
| D | qcom,sc8180x-pas.yaml | 4 $id: http://devicetree.org/schemas/remoteproc/qcom,sc8180x-pas.yaml#
54 - $ref: /schemas/remoteproc/qcom,pas-common.yaml#
|
| D | qcom,sm8150-pas.yaml | 4 $id: http://devicetree.org/schemas/remoteproc/qcom,sm8150-pas.yaml#
58 - $ref: /schemas/remoteproc/qcom,pas-common.yaml#
141 remoteproc@17300000 {
|
| D | qcom,sm8550-pas.yaml | 4 $id: http://devicetree.org/schemas/remoteproc/qcom,sm8550-pas.yaml#
59 - $ref: /schemas/remoteproc/qcom,pas-common.yaml#
140 remoteproc@30000000 {
|
| D | ti,omap-remoteproc.yaml | 4 $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
137 Custom autosuspend delay for the remoteproc in milliseconds.
|
| D | wkup_m3_rproc.txt | 1 TI Wakeup M3 Remoteproc Driver
7 binary to accomplish this. The wkup_m3 remoteproc driver handles the loading of
|
| D | ti,pru-consumer.yaml | 4 $id: http://devicetree.org/schemas/remoteproc/ti,pru-consumer.yaml#
17 properties are a list of common properties supported by the PRU remoteproc
|
| D | qcom,sm8350-pas.yaml | 4 $id: http://devicetree.org/schemas/remoteproc/qcom,sm8350-pas.yaml#
59 - $ref: /schemas/remoteproc/qcom,pas-common.yaml#
145 remoteproc@30000000 {
|
| D | amlogic,meson-mx-ao-arc.yaml | 4 $id: http://devicetree.org/schemas/remoteproc/amlogic,meson-mx-ao-arc.yaml#
77 remoteproc@1c {
|
| D | qcom,rpm-proc.yaml | 4 $id: http://devicetree.org/schemas/remoteproc/qcom,rpm-proc.yaml#
96 $ref: /schemas/remoteproc/qcom,smd-edge.yaml#
102 $ref: /schemas/remoteproc/qcom,glink-rpm-edge.yaml#
136 remoteproc {
156 remoteproc {
|
| /Documentation/staging/ |
| D | remoteproc.rst | 17 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
84 #include <linux/remoteproc.h>
151 Register @rproc with the remoteproc framework, after it has been
186 Report a crash in a remoteproc
190 non-remoteproc driver. This function can be called from atomic/interrupt
196 These callbacks should be provided by platform-specific remoteproc
211 Every remoteproc implementation should at least provide the ->start and ->stop
217 The boot address, in case needed, can be found in rproc->bootaddr (remoteproc
[all …]
|
| D | index.rst | 11 remoteproc
|
| /Documentation/translations/zh_CN/staging/ |
| D | index.rst | 22 * remoteproc
|
123