|
|
|
|
menu "Rpmsg drivers"
|
|
|
|
|
|
|
|
|
|
# RPMSG always gets selected by whoever wants it
|
|
|
|
|
config RPMSG
|
|
|
|
|
tristate
|
|
|
|
|
|
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
8 years ago
|
|
|
config RPMSG_CHAR
|
|
|
|
|
tristate "RPMSG device interface"
|
|
|
|
|
depends on RPMSG
|
|
|
|
|
depends on NET
|
rpmsg: Driver for user space endpoint interface
This driver allows rpmsg instances to expose access to rpmsg endpoints
to user space processes. It provides a control interface, allowing
userspace to export endpoints and an endpoint interface for each exposed
endpoint.
The implementation is based on prior art by Texas Instrument, Google,
PetaLogix and was derived from a FreeRTOS performance statistics driver
written by Michal Simek.
The control interface provides a "create endpoint" ioctl, which is fed a
name, source and destination address. The three values are used to
create the endpoint, in a backend-specific way, and a rpmsg endpoint
device is created - with the three parameters are available in sysfs for
udev usage.
E.g. to create an endpoint device for one of the Qualcomm SMD channel
related to DIAG one would issue:
struct rpmsg_endpoint_info info = { "DIAG_CNTL", 0, 0 };
int fd = open("/dev/rpmsg_ctrl0", O_RDWR);
ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info);
Each created endpoint device shows up as an individual character device
in /dev, allowing permission to be controlled on a per-endpoint basis.
The rpmsg endpoint will be created and destroyed following the opening
and closing of the endpoint device, allowing rpmsg backends to open and
close the physical channel, if supported by the wire protocol.
Cc: Marek Novak <marek.novak@nxp.com>
Cc: Matteo Sartori <matteo.sartori@t3lab.it>
Cc: Michal Simek <monstr@monstr.eu>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
8 years ago
|
|
|
help
|
|
|
|
|
Say Y here to export rpmsg endpoints as device files, usually found
|
|
|
|
|
in /dev. They make it possible for user-space programs to send and
|
|
|
|
|
receive rpmsg packets.
|
|
|
|
|
|
|
|
|
|
config RPMSG_QCOM_GLINK_NATIVE
|
|
|
|
|
tristate
|
|
|
|
|
select RPMSG
|
|
|
|
|
|
|
|
|
|
config RPMSG_QCOM_GLINK_RPM
|
|
|
|
|
tristate "Qualcomm RPM Glink driver"
|
|
|
|
|
select RPMSG_QCOM_GLINK_NATIVE
|
|
|
|
|
depends on HAS_IOMEM
|
|
|
|
|
depends on MAILBOX
|
|
|
|
|
help
|
|
|
|
|
Say y here to enable support for the GLINK RPM communication driver,
|
|
|
|
|
which serves as a channel for communication with the RPM in GLINK
|
|
|
|
|
enabled systems.
|
|
|
|
|
|
|
|
|
|
config RPMSG_QCOM_GLINK_SMEM
|
|
|
|
|
tristate "Qualcomm SMEM Glink driver"
|
|
|
|
|
select RPMSG_QCOM_GLINK_NATIVE
|
|
|
|
|
depends on MAILBOX
|
|
|
|
|
depends on QCOM_SMEM
|
|
|
|
|
help
|
|
|
|
|
Say y here to enable support for the GLINK SMEM communication driver,
|
|
|
|
|
which provides support for using the GLINK communication protocol
|
|
|
|
|
over SMEM.
|
|
|
|
|
|
|
|
|
|
config RPMSG_QCOM_GLINK_SPSS
|
|
|
|
|
tristate "Qualcomm SPSS Glink driver"
|
|
|
|
|
select RPMSG_QCOM_GLINK_NATIVE
|
|
|
|
|
depends on MAILBOX
|
|
|
|
|
depends on QCOM_SMEM
|
|
|
|
|
select QSEE_IPC_IRQ
|
|
|
|
|
help
|
|
|
|
|
Say y here to enable support for the GLINK SPSS communication driver,
|
|
|
|
|
which provides support for using the GLINK communication protocol
|
|
|
|
|
over SMEM. This protocol maps the smem and then shares the mapped
|
|
|
|
|
region with the remote proc by writing the smem descriptor location
|
|
|
|
|
and size into shared registers.
|
|
|
|
|
|
|
|
|
|
config RPMSG_QCOM_GLINK_SPI
|
|
|
|
|
tristate "Qualcomm SPI Glink driver"
|
|
|
|
|
help
|
|
|
|
|
Say y here to enable support for the GLINK SPI communication driver,
|
|
|
|
|
which provides support for using the GLINK communication protocol
|
|
|
|
|
over SPI. This transport performs marshaling of GLINK commands and
|
|
|
|
|
data to the appropriate SPI bus wire format and allows for GLINK
|
|
|
|
|
communication with remote subsystems that are external to the SoC.
|
|
|
|
|
|
|
|
|
|
config RPMSG_QCOM_GLINK_BGCOM
|
|
|
|
|
tristate "Qualcomm Technologies, Inc. BGCOM Glink driver"
|
|
|
|
|
help
|
|
|
|
|
Say y here to enable support for the GLINK BGCOM driver,
|
|
|
|
|
which provides support for using the GLINK communication protocol
|
|
|
|
|
over BGCOM. This transport performs marshaling of GLINK commands and
|
|
|
|
|
data to the appropriate BGCOM format and allows for GLINK
|
|
|
|
|
communication with remote subsystems that are external to the SoC.
|
|
|
|
|
|
|
|
|
|
config RPMSG_QCOM_SMD
|
|
|
|
|
tristate "Qualcomm Shared Memory Driver (SMD)"
|
|
|
|
|
depends on QCOM_SMEM
|
|
|
|
|
select RPMSG
|
|
|
|
|
help
|
|
|
|
|
Say y here to enable support for the Qualcomm Shared Memory Driver
|
|
|
|
|
providing communication channels to remote processors in Qualcomm
|
|
|
|
|
platforms.
|
|
|
|
|
|
|
|
|
|
config RPMSG_VIRTIO
|
|
|
|
|
tristate "Virtio RPMSG bus driver"
|
|
|
|
|
depends on HAS_DMA
|
|
|
|
|
select RPMSG
|
|
|
|
|
select VIRTIO
|
|
|
|
|
|
|
|
|
|
config MSM_RPM_SMD
|
|
|
|
|
bool "RPM driver using SMD protocol"
|
|
|
|
|
help
|
|
|
|
|
RPM is the dedicated hardware engine for managing shared SoC
|
|
|
|
|
resources. This config adds driver support for using SMD as a
|
|
|
|
|
transport layer communication with RPM hardware. It also selects
|
|
|
|
|
the MSM_MPM config that programs the MPM module to monitor interrupts
|
|
|
|
|
during sleep modes.
|
|
|
|
|
|
|
|
|
|
endmenu
|
