On 2/13/19 7:48 PM, Xiang Xiao wrote:
> From: Guiding Li <liguiding@xxxxxxxxxxxx>
>
> This driver allows the remote processor redirect the output of
processor to redirect
> syslog/printf into the kernel log, which is very useful to see
> what happen in the remote side.
>
> Signed-off-by: Guiding Li <liguiding@xxxxxxxxxxxx>
> ---
> drivers/rpmsg/Kconfig | 12 ++++
> drivers/rpmsg/Makefile | 1 +
> drivers/rpmsg/rpmsg_syslog.c | 163 +++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 176 insertions(+)
> create mode 100644 drivers/rpmsg/rpmsg_syslog.c
>
> diff --git a/drivers/rpmsg/Kconfig b/drivers/rpmsg/Kconfig
> index d0322b4..d701614 100644
> --- a/drivers/rpmsg/Kconfig
> +++ b/drivers/rpmsg/Kconfig
> @@ -15,6 +15,18 @@ config RPMSG_CHAR
> in /dev. They make it possible for user-space programs to send and
> receive rpmsg packets.
>
> +config RPMSG_SYSLOG
> + tristate "RPMSG syslog redirection"
> + depends on RPMSG
> + help
> + Say Y here to redirect the syslog/printf from remote processor into
> + the kernel log which is very useful to see what happen in the remote
see what happens
or see what happened
> + side.
> +
> + If the remote processor hang during bootup or panic at the runtime,
hangs during bootup or panics during runtime,
> + We can even cat /sys/kernel/debug/remoteproc/remoteprocX/trace0 to
we
> + get the last log which doesn't output yet.
get the last log which hasn't been output yet.
> +
> config RPMSG_QCOM_GLINK_NATIVE
> tristate
> select RPMSG
--
~Randy
