public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>
Cc: Russell King <linux@armlinux.org.uk>,
	Arnd Bergmann <arnd@arndb.de>, Joel Stanley <joel@jms.id.au>,
	Dmitry Osipenko <digetx@gmail.com>,
	Thierry Reding <treding@nvidia.com>,
	Manivannan Sadhasivam <mani@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ARM: multi_v7_defconfig: Enable CONFIG_RPMSG_TTY
Date: Mon, 20 Dec 2021 17:58:27 +0100	[thread overview]
Message-ID: <YcC2M/QseKewXDGw@kroah.com> (raw)
In-Reply-To: <20211220161155.32564-1-arnaud.pouliquen@foss.st.com>

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@foss.st.com>
> ---
> delta vs V1:
> add
> ---

"add"?  What does that mean?

Do all v7 chips have this hardware?

thanks,

greg k-h

  reply	other threads:[~2021-12-20 16:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-20 16:11 [PATCH v2] ARM: multi_v7_defconfig: Enable CONFIG_RPMSG_TTY Arnaud Pouliquen
2021-12-20 16:58 ` Greg Kroah-Hartman [this message]
2021-12-21  9:05   ` Arnaud POULIQUEN

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YcC2M/QseKewXDGw@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arnaud.pouliquen@foss.st.com \
    --cc=arnd@arndb.de \
    --cc=digetx@gmail.com \
    --cc=joel@jms.id.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mani@kernel.org \
    --cc=treding@nvidia.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox