From: Rob Herring <robh+dt@kernel.org>
To: Rishi Gupta <gupt21@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>, Jonathan Corbet <corbet@lwn.net>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
devicetree@vger.kernel.org,
"open list:SERIAL DRIVERS" <linux-serial@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>
Subject: Re: [PATCH v3 1/4] dt-bindings: ttyvs: document serial null modem driver bindings
Date: Thu, 16 Apr 2020 15:38:07 -0500 [thread overview]
Message-ID: <CAL_JsqLWMTpHG=bOmWgy1kg6d7vxRGbCda+febq=FnqbuRbPyQ@mail.gmail.com> (raw)
In-Reply-To: <1587012974-21219-1-git-send-email-gupt21@gmail.com>
On Wed, Apr 15, 2020 at 11:56 PM Rishi Gupta <gupt21@gmail.com> wrote:
>
> The ttyvs driver creates virtual tty devices. These devices can
> also be created through device tree. This commit document this.
Device tree is for real h/w devices. You have a configfs interface to
set these up. I don't think we need both.
Rob
next prev parent reply other threads:[~2020-04-16 20:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 4:56 [PATCH v3 1/4] dt-bindings: ttyvs: document serial null modem driver bindings Rishi Gupta
2020-04-16 4:56 ` [PATCH v3 2/4] tty/serial: ttvys: add null modem driver for emulation Rishi Gupta
2020-04-20 11:32 ` Andy Shevchenko
2020-04-16 4:56 ` [PATCH v3 3/4] tty: documentation: abi: add ttyvs null modem driver sysfs nodes Rishi Gupta
2020-04-16 4:56 ` [PATCH v3 4/4] tty: documentation: document how to use ttyvs driver Rishi Gupta
2020-04-16 5:58 ` Randy Dunlap
2020-04-16 7:24 ` Mauro Carvalho Chehab
2020-04-17 5:16 ` rishi gupta
2020-04-17 12:53 ` Andy Shevchenko
2020-04-16 20:38 ` Rob Herring [this message]
2020-04-17 5:14 ` [PATCH v3 1/4] dt-bindings: ttyvs: document serial null modem driver bindings rishi gupta
2020-04-17 13:22 ` Rob Herring
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='CAL_JsqLWMTpHG=bOmWgy1kg6d7vxRGbCda+febq=FnqbuRbPyQ@mail.gmail.com' \
--to=robh+dt@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=gupt21@gmail.com \
--cc=jslaby@suse.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).