[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YcC2M/QseKewXDGw@kroah.com>
Date: Mon, 20 Dec 2021 17:58:27 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Arnaud Pouliquen <arnaud.pouliquen@...s.st.com>
Cc: Russell King <linux@...linux.org.uk>,
Arnd Bergmann <arnd@...db.de>, Joel Stanley <joel@....id.au>,
Dmitry Osipenko <digetx@...il.com>,
Thierry Reding <treding@...dia.com>,
Manivannan Sadhasivam <mani@...nel.org>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] ARM: multi_v7_defconfig: Enable CONFIG_RPMSG_TTY
On Mon, Dec 20, 2021 at 05:11:55PM +0100, Arnaud Pouliquen wrote:
> The RPMsg TTY implements an inter-processor communication with a standard
> TTY interface on top of the RPMsg framework.
> This driver is a generic RPMsg client that can run on different platforms.
>
> By enabling the RPMSG_TTY driver as module in multi_v7_defconfig, it makes
> possible to automatically probe the rpmsg_tty driver by the RPMsg bus,
> when the support of the RPMsg service is dynamically requested by the
> co-processor firmware.
>
> Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen@...s.st.com>
> ---
> delta vs V1:
> add
> ---
"add"? What does that mean?
Do all v7 chips have this hardware?
thanks,
greg k-h
Powered by blists - more mailing lists