Home
last modified time | relevance | path

Searched +full:rpmsg +full:- +full:name (Results 1 – 25 of 79) sorted by relevance

1234

/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-bus-rpmsg1 What: /sys/bus/rpmsg/devices/.../name
4 Contact: Ohad Ben-Cohen <ohad@wizery.com>
6 Every rpmsg device is a communication channel with a remote
7 processor. Channels are identified with a (textual) name,
9 rpmsg.h).
11 This sysfs entry contains the name of this channel.
13 What: /sys/bus/rpmsg/devices/.../src
16 Contact: Ohad Ben-Cohen <ohad@wizery.com>
18 Every rpmsg device is a communication channel with a remote
19 processor. Channels have a local ("source") rpmsg address,
[all …]
/kernel/linux/linux-4.19/Documentation/ABI/testing/
Dsysfs-bus-rpmsg1 What: /sys/bus/rpmsg/devices/.../name
4 Contact: Ohad Ben-Cohen <ohad@wizery.com>
6 Every rpmsg device is a communication channel with a remote
7 processor. Channels are identified with a (textual) name,
9 rpmsg.h).
11 This sysfs entry contains the name of this channel.
13 What: /sys/bus/rpmsg/devices/.../src
16 Contact: Ohad Ben-Cohen <ohad@wizery.com>
18 Every rpmsg device is a communication channel with a remote
19 processor. Channels have a local ("source") rpmsg address,
[all …]
/kernel/linux/linux-5.10/Documentation/staging/
Drpmsg.rst2 Remote Processor Messaging (rpmsg) Framework
7 This document describes the rpmsg bus and how to write rpmsg drivers.
8 To learn how to add rpmsg support for new platforms, check out remoteproc.txt
17 flavor of real-time OS.
19 OMAP4, for example, has dual Cortex-A9, dual Cortex-M3 and a C64x+ DSP.
20 Typically, the dual cortex-A9 is running Linux in a SMP configuration,
25 hardware accelerators, and therefore are often used to offload CPU-intensive
28 These remote processors could also be used to control latency-sensitive
34 hardware accessible only by the remote processor, reserving kernel-controlled
37 Rpmsg is a virtio-based messaging bus that allows kernel drivers to communicate
[all …]
Dremoteproc.rst10 of operating system, whether it's Linux or any other flavor of real-time OS.
12 OMAP4, for example, has dual Cortex-A9, dual Cortex-M3 and a C64x+ DSP.
13 In a typical configuration, the dual cortex-A9 is running Linux in a SMP
20 duplicated. In addition, this framework also adds rpmsg virtio devices
22 platform-specific remoteproc drivers only need to provide a few low-level
23 handlers, and then all rpmsg drivers will then just work
24 (for more information about the virtio-based rpmsg bus and its drivers,
25 please read Documentation/staging/rpmsg.rst).
111 struct rproc *rproc_alloc(struct device *dev, const char *name,
117 name of this remote processor, platform-specific ops handlers,
[all …]
/kernel/linux/linux-4.19/Documentation/
Drpmsg.txt2 Remote Processor Messaging (rpmsg) Framework
7 This document describes the rpmsg bus and how to write rpmsg drivers.
8 To learn how to add rpmsg support for new platforms, check out remoteproc.txt
17 flavor of real-time OS.
19 OMAP4, for example, has dual Cortex-A9, dual Cortex-M3 and a C64x+ DSP.
20 Typically, the dual cortex-A9 is running Linux in a SMP configuration,
25 hardware accelerators, and therefore are often used to offload CPU-intensive
28 These remote processors could also be used to control latency-sensitive
34 hardware accessible only by the remote processor, reserving kernel-controlled
37 Rpmsg is a virtio-based messaging bus that allows kernel drivers to communicate
[all …]
Dremoteproc.txt10 of operating system, whether it's Linux or any other flavor of real-time OS.
12 OMAP4, for example, has dual Cortex-A9, dual Cortex-M3 and a C64x+ DSP.
13 In a typical configuration, the dual cortex-A9 is running Linux in a SMP
20 duplicated. In addition, this framework also adds rpmsg virtio devices
22 platform-specific remoteproc drivers only need to provide a few low-level
23 handlers, and then all rpmsg drivers will then just work
24 (for more information about the virtio-based rpmsg bus and its drivers,
25 please read Documentation/rpmsg.txt).
111 struct rproc *rproc_alloc(struct device *dev, const char *name,
117 name of this remote processor, platform-specific ops handlers,
[all …]
/kernel/linux/linux-5.10/drivers/rpmsg/
Drpmsg_core.c1 // SPDX-License-Identifier: GPL-2.0
8 * Ohad Ben-Cohen <ohad@wizery.com>
16 #include <linux/rpmsg.h>
24 * rpmsg_create_ept() - create a new rpmsg_endpoint
25 * @rpdev: rpmsg channel device
28 * @chinfo: channel_info with the local rpmsg address to bind with @cb
30 * Every rpmsg address in the system is bound to an rx callback (so when
31 * inbound messages arrive, they are dispatched by the rpmsg bus using the
35 * bind a callback, and possibly some private data too, to an rpmsg address
39 * Simple rpmsg drivers need not call rpmsg_create_ept, because an endpoint
[all …]
Dmtk_rpmsg.c1 // SPDX-License-Identifier: GPL-2.0
10 #include <linux/rpmsg/mtk_rpmsg.h>
36 * struct rpmsg_ns_msg - dynamic name service announcement message
37 * @name: name of remote service that is published
41 * messages, an appropriate rpmsg channel (i.e device) is created. In turn, the
42 * ->probe() handler of the appropriate rpmsg driver will be invoked
43 * (if/as-soon-as one is registered).
46 char name[RPMSG_NAME_SIZE]; member
75 struct rpmsg_endpoint *ept = &mept->ept; in mtk_rpmsg_ipi_handler()
78 ret = (*ept->cb)(ept->rpdev, data, len, ept->priv, ept->addr); in mtk_rpmsg_ipi_handler()
[all …]
Drpmsg_char.c1 // SPDX-License-Identifier: GPL-2.0
9 * Based on rpmsg performance statistics driver by Michal Simek, which in turn
10 * was based on TI & Google OMX rpmsg driver.
19 #include <linux/rpmsg.h>
23 #include <uapi/linux/rpmsg.h>
43 * struct rpmsg_ctrldev - control device for instantiating endpoint devices
44 * @rpdev: underlaying rpmsg device
55 * struct rpmsg_eptdev - endpoint device context
58 * @rpdev: underlaying rpmsg device
61 * @ept: rpmsg endpoint reference, when open
[all …]
Dvirtio_rpmsg_bus.c1 // SPDX-License-Identifier: GPL-2.0
3 * Virtio-based remote processor messaging bus
8 * Ohad Ben-Cohen <ohad@wizery.com>
14 #include <linux/dma-mapping.h>
21 #include <linux/rpmsg.h>
34 * struct virtproc_info - virtual remote processor state
51 * @ns_ept: the bus's name service endpoint
53 * This structure stores the rpmsg state of a given virtio remote processor
73 /* The feature bitmap for virtio rpmsg */
74 #define VIRTIO_RPMSG_F_NS 0 /* RP supports name service notifications */
[all …]
Drpmsg_internal.h1 /* SPDX-License-Identifier: GPL-2.0 */
8 * Ohad Ben-Cohen <ohad@wizery.com>
15 #include <linux/rpmsg.h>
22 * struct rpmsg_device_ops - indirection table for the rpmsg_device operations
23 * @create_ept: create backend-specific endpoint, required
27 * Indirection table for the operations that a rpmsg backend should implement.
41 * struct rpmsg_endpoint_ops - indirection table for rpmsg_endpoint operations
51 * Indirection table for the operations that a rpmsg backend should implement.
53 * @trysend, while the variants sending data off-channel are optional.
79 * rpmsg_chrdev_register_device() - register chrdev device based on rpdev
[all …]
/kernel/linux/linux-4.19/drivers/rpmsg/
Drpmsg_core.c1 // SPDX-License-Identifier: GPL-2.0
8 * Ohad Ben-Cohen <ohad@wizery.com>
16 #include <linux/rpmsg.h>
24 * rpmsg_create_ept() - create a new rpmsg_endpoint
25 * @rpdev: rpmsg channel device
28 * @chinfo: channel_info with the local rpmsg address to bind with @cb
30 * Every rpmsg address in the system is bound to an rx callback (so when
31 * inbound messages arrive, they are dispatched by the rpmsg bus using the
35 * bind a callback, and possibly some private data too, to an rpmsg address
39 * Simple rpmsg drivers need not call rpmsg_create_ept, because an endpoint
[all …]
Drpmsg_char.c1 // SPDX-License-Identifier: GPL-2.0
9 * Based on rpmsg performance statistics driver by Michal Simek, which in turn
10 * was based on TI & Google OMX rpmsg driver.
19 #include <linux/rpmsg.h>
23 #include <uapi/linux/rpmsg.h>
43 * struct rpmsg_ctrldev - control device for instantiating endpoint devices
44 * @rpdev: underlaying rpmsg device
55 * struct rpmsg_eptdev - endpoint device context
58 * @rpdev: underlaying rpmsg device
61 * @ept: rpmsg endpoint reference, when open
[all …]
Dvirtio_rpmsg_bus.c1 // SPDX-License-Identifier: GPL-2.0
3 * Virtio-based remote processor messaging bus
8 * Ohad Ben-Cohen <ohad@wizery.com>
20 #include <linux/dma-mapping.h>
26 #include <linux/rpmsg.h>
33 * struct virtproc_info - virtual remote processor state
50 * @ns_ept: the bus's name service endpoint
52 * This structure stores the rpmsg state of a given virtio remote processor
72 /* The feature bitmap for virtio rpmsg */
73 #define VIRTIO_RPMSG_F_NS 0 /* RP supports name service notifications */
[all …]
Drpmsg_internal.h1 /* SPDX-License-Identifier: GPL-2.0 */
8 * Ohad Ben-Cohen <ohad@wizery.com>
15 #include <linux/rpmsg.h>
22 * struct rpmsg_device_ops - indirection table for the rpmsg_device operations
23 * @create_ept: create backend-specific endpoint, requried
27 * Indirection table for the operations that a rpmsg backend should implement.
41 * struct rpmsg_endpoint_ops - indirection table for rpmsg_endpoint operations
50 * Indirection table for the operations that a rpmsg backend should implement.
52 * @trysend, while the variants sending data off-channel are optional.
78 * rpmsg_chrdev_register_device() - register chrdev device based on rpdev
[all …]
/kernel/linux/linux-5.10/include/linux/
Drpmsg.h1 /* SPDX-License-Identifier: BSD-3-Clause */
29 * struct rpmsg_channel_info - channel info representation
30 * @name: name of service
35 char name[RPMSG_NAME_SIZE]; member
41 * rpmsg_device - device that belong to the rpmsg bus
43 * @id: device id (used to match between rpmsg drivers and devices)
44 * @driver_override: driver name to force a match
47 * @ept: the rpmsg endpoint of this channel
48 * @announce: if set, rpmsg will announce the creation/removal of this channel
65 * struct rpmsg_endpoint - binds a local rpmsg address to its user
[all …]
/kernel/linux/linux-4.19/include/linux/
Drpmsg.h1 /* SPDX-License-Identifier: BSD-3-Clause */
29 * struct rpmsg_channel_info - channel info representation
30 * @name: name of service
35 char name[RPMSG_NAME_SIZE]; member
41 * rpmsg_device - device that belong to the rpmsg bus
43 * @id: device id (used to match between rpmsg drivers and devices)
44 * @driver_override: driver name to force a match
47 * @ept: the rpmsg endpoint of this channel
48 * @announce: if set, rpmsg will announce the creation/removal of this channel
65 * struct rpmsg_endpoint - binds a local rpmsg address to its user
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/remoteproc/
Dmtk,scp.txt2 ----------------------------------------
4 This binding provides support for ARM Cortex M4 Co-processor found on some
8 - compatible Should be "mediatek,mt8183-scp"
9 - reg Should contain the address ranges for the two memory
11 - reg-names Contains the corresponding names for the two memory
13 - clocks Clock for co-processor (See: ../clock/clock-bindings.txt)
14 - clock-names Contains the corresponding name for the clock. This
18 --------
20 Subnodes of the SCP represent rpmsg devices. The names of the devices are not
22 for the rpmsg devices - but must contain the following property:
[all …]
/kernel/linux/linux-5.10/drivers/platform/chrome/
Dcros_ec_rpmsg.c1 // SPDX-License-Identifier: GPL-2.0
13 #include <linux/rpmsg.h>
23 * struct cros_ec_rpmsg_response - rpmsg message format from from EC.
36 * struct cros_ec_rpmsg - information about a EC over rpmsg.
38 * @rpdev: rpmsg device we are connected to
41 * @ept: The rpmsg endpoint of this channel.
55 * cros_ec_cmd_xfer_rpmsg - Transfer a message over rpmsg and receive the reply
63 * Return: -EINVAL
68 return -EINVAL; in cros_ec_cmd_xfer_rpmsg()
72 * cros_ec_pkt_xfer_rpmsg - Transfer a packet over rpmsg and receive the reply
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/
Dgoogle,cros-ec.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mfd/google,cros-ec.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Benson Leung <bleung@chromium.org>
11 - Enric Balletbo i Serra <enric.balletbo@collabora.com>
12 - Guenter Roeck <groeck@chromium.org>
23 - description:
25 const: google,cros-ec-i2c
26 - description:
[all …]
/kernel/linux/linux-5.10/samples/rpmsg/
Drpmsg_client_sample.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * Remote processor messaging - sample client driver
8 * Ohad Ben-Cohen <ohad@wizery.com>
14 #include <linux/rpmsg.h>
29 struct instance_data *idata = dev_get_drvdata(&rpdev->dev); in rpmsg_sample_cb()
31 dev_info(&rpdev->dev, "incoming msg %d (src: 0x%x)\n", in rpmsg_sample_cb()
32 ++idata->rx_count, src); in rpmsg_sample_cb()
38 if (idata->rx_count >= count) { in rpmsg_sample_cb()
39 dev_info(&rpdev->dev, "goodbye!\n"); in rpmsg_sample_cb()
44 ret = rpmsg_send(rpdev->ept, MSG, strlen(MSG)); in rpmsg_sample_cb()
[all …]
/kernel/linux/linux-4.19/samples/rpmsg/
Drpmsg_client_sample.c2 * Remote processor messaging - sample client driver
7 * Ohad Ben-Cohen <ohad@wizery.com>
22 #include <linux/rpmsg.h>
35 struct instance_data *idata = dev_get_drvdata(&rpdev->dev); in rpmsg_sample_cb()
37 dev_info(&rpdev->dev, "incoming msg %d (src: 0x%x)\n", in rpmsg_sample_cb()
38 ++idata->rx_count, src); in rpmsg_sample_cb()
44 if (idata->rx_count >= MSG_LIMIT) { in rpmsg_sample_cb()
45 dev_info(&rpdev->dev, "goodbye!\n"); in rpmsg_sample_cb()
50 ret = rpmsg_send(rpdev->ept, MSG, strlen(MSG)); in rpmsg_sample_cb()
52 dev_err(&rpdev->dev, "rpmsg_send failed: %d\n", ret); in rpmsg_sample_cb()
[all …]
/kernel/linux/linux-4.19/drivers/media/platform/sti/delta/
Ddelta-ipc.c1 // SPDX-License-Identifier: GPL-2.0
7 #include <linux/rpmsg.h>
10 #include "delta-ipc.h"
11 #include "delta-mem.h"
38 #define msg_to_ctx(msg) ((struct delta_ipc_ctx *)(msg)->header.host_hdl)
39 #define msg_to_copro_hdl(msg) ((msg)->header.copro_hdl)
43 return (ctx->ipc_buf->paddr + (vaddr - ctx->ipc_buf->vaddr)); in to_paddr()
49 return ((data >= ctx->ipc_buf->vaddr) && in is_valid_data()
50 ((data + size) <= (ctx->ipc_buf->vaddr + ctx->ipc_buf->size))); in is_valid_data()
58 * this IPC shared memory, avoiding de-facto recopies inside delta-ipc.
[all …]
/kernel/linux/linux-5.10/drivers/media/platform/sti/delta/
Ddelta-ipc.c1 // SPDX-License-Identifier: GPL-2.0
7 #include <linux/rpmsg.h>
10 #include "delta-ipc.h"
11 #include "delta-mem.h"
38 #define msg_to_ctx(msg) ((struct delta_ipc_ctx *)(msg)->header.host_hdl)
39 #define msg_to_copro_hdl(msg) ((msg)->header.copro_hdl)
43 return (ctx->ipc_buf->paddr + (vaddr - ctx->ipc_buf->vaddr)); in to_paddr()
49 return ((data >= ctx->ipc_buf->vaddr) && in is_valid_data()
50 ((data + size) <= (ctx->ipc_buf->vaddr + ctx->ipc_buf->size))); in is_valid_data()
58 * this IPC shared memory, avoiding de-facto recopies inside delta-ipc.
[all …]
/kernel/linux/linux-4.19/drivers/remoteproc/
Dqcom_sysmon.c1 // SPDX-License-Identifier: GPL-2.0
14 #include <linux/rpmsg.h>
26 const char *name; member
49 * sysmon_send_event() - send notification of other remote's SSR event
51 * @name: other remote's name
53 static void sysmon_send_event(struct qcom_sysmon *sysmon, const char *name) in sysmon_send_event() argument
59 len = snprintf(req, sizeof(req), "ssr:%s:before_shutdown", name); in sysmon_send_event()
63 mutex_lock(&sysmon->lock); in sysmon_send_event()
64 reinit_completion(&sysmon->comp); in sysmon_send_event()
65 sysmon->ssr_ack = false; in sysmon_send_event()
[all …]

1234