From: Rishi Gupta <gupt21@gmail.com>
To: gregkh@linuxfoundation.org, robh+dt@kernel.org
Cc: jslaby@suse.com, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org, Rishi Gupta <gupt21@gmail.com>
Subject: [PATCH v2 3/4] tty: documentation: abi: add ttyvs null modem driver sysfs nodes
Date: Sat, 15 Feb 2020 23:21:08 +0530 [thread overview]
Message-ID: <1581789069-5232-3-git-send-email-gupt21@gmail.com> (raw)
In-Reply-To: <1581789069-5232-1-git-send-email-gupt21@gmail.com>
The ttyvs driver exposes sysfs file called event to emulate
various serial port events. This commit document this file.
User space application writes various codes to this file.
Signed-off-by: Rishi Gupta <gupt21@gmail.com>
---
Changes in v2:
- Updated path to /sys/class/tty/ttyvsN/event
- Used Documentation/ABI/testing/sysfs-tty, previously new file was created
Documentation/ABI/testing/sysfs-tty | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-tty b/Documentation/ABI/testing/sysfs-tty
index 9eb3c2b..c6002c5 100644
--- a/Documentation/ABI/testing/sysfs-tty
+++ b/Documentation/ABI/testing/sysfs-tty
@@ -154,3 +154,18 @@ Description:
device specification. For example, when user sets 7bytes on
16550A, which has 1/4/8/14 bytes trigger, the RX trigger is
automatically changed to 4 bytes.
+
+What: /sys/class/tty/ttyvsN/event
+Date: February 2020
+Contact: Rishi Gupta <gupt21@gmail.com>
+Description:
+ The ttyvs driver will emulate serial port event; parity error,
+ framing error, overrun error, asserting/de-asserting break
+ condition and ring indication when user space application
+ writes an event code on this sysfs file.
+
+ Write 1 to emulate framing error, write 2 for parity error,
+ write 3 for overrun error, write 4 to set ring indication,
+ write 5 to clear ring indication, write 6 to emulate a break
+ condition detected, write 7 to emulate a faulty cable and
+ write 8 to remove faulty cable condition.
--
2.7.4
next prev parent reply other threads:[~2020-02-15 17:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-15 17:51 [PATCH v2 1/4] dt-bindings: ttyvs: document serial null modem driver bindings Rishi Gupta
2020-02-15 17:51 ` [PATCH v2 2/4] tty/serial: ttvys: add null modem driver for emulation Rishi Gupta
2020-04-08 16:16 ` rishi gupta
2020-04-13 9:23 ` Andy Shevchenko
2020-02-15 17:51 ` Rishi Gupta [this message]
2020-02-15 17:51 ` [PATCH v2 4/4] tty: documentation: document how to use ttyvs driver Rishi Gupta
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=1581789069-5232-3-git-send-email-gupt21@gmail.com \
--to=gupt21@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=robh+dt@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).