I am sending this patch as RFC I am am aware that this is
not ready for inclusion. I am however want to get some
feedback on this choosen approach. In the end I want to be
able to get log messages from the remote firmware into syslog.
Christian Gmeiner (1):
rpmsg: add syslog driver
drivers/rpmsg/Kconfig | 8 ++++++++
drivers/rpmsg/Makefile | 1 +
2 files changed, 9 insertions(+)
--
2.33.1
Allows the remote firmware to log into syslog.
Signed-off-by: Christian Gmeiner <[email protected]>
---
drivers/rpmsg/Kconfig | 8 ++++++++
drivers/rpmsg/Makefile | 1 +
2 files changed, 9 insertions(+)
diff --git a/drivers/rpmsg/Kconfig b/drivers/rpmsg/Kconfig
index 0b4407abdf13..801f9956ec21 100644
--- a/drivers/rpmsg/Kconfig
+++ b/drivers/rpmsg/Kconfig
@@ -73,4 +73,12 @@ config RPMSG_VIRTIO
select RPMSG_NS
select VIRTIO
+config RPMSG_SYSLOG
+ tristate "SYSLOG device interface"
+ depends on RPMSG
+ 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.
+
endmenu
diff --git a/drivers/rpmsg/Makefile b/drivers/rpmsg/Makefile
index 8d452656f0ee..75b2ec7133a5 100644
--- a/drivers/rpmsg/Makefile
+++ b/drivers/rpmsg/Makefile
@@ -9,3 +9,4 @@ obj-$(CONFIG_RPMSG_QCOM_GLINK_RPM) += qcom_glink_rpm.o
obj-$(CONFIG_RPMSG_QCOM_GLINK_SMEM) += qcom_glink_smem.o
obj-$(CONFIG_RPMSG_QCOM_SMD) += qcom_smd.o
obj-$(CONFIG_RPMSG_VIRTIO) += virtio_rpmsg_bus.o
+obj-$(CONFIG_RPMSG_SYSLOG) += rpmsg_syslog.o
--
2.33.1