From: pavan_savoy@ti.com
To: gregkh@suse.de, alan@lxorguk.ukuu.org.uk
Cc: pavan_savoy@ti.com, linux-kernel@vger.kernel.org,
pavan_savoy@yahoo.co.in
Subject: [PATCH 7/7] Documentation/ABI: for N_TI_SHARED ldisc
Date: Tue, 23 Mar 2010 15:41:15 -0500 [thread overview]
Message-ID: <1269376875-25940-8-git-send-email-pavan_savoy@ti.com> (raw)
In-Reply-To: <1269376875-25940-7-git-send-email-pavan_savoy@ti.com>
From: Pavan Savoy <pavan_savoy@ti.com>
N_TI_SHARED creates a sysfs entry to communicate
with the application/daemon which would want to install/
un-install the line discipline, it's documentation
now exists in testing/ subdirectory.
Signed-off-by: Pavan Savoy <pavan_savoy@ti.com>
---
Documentation/ABI/testing/sysfs-uim | 24 ++++++++++++++++++++++++
1 files changed, 24 insertions(+), 0 deletions(-)
create mode 100644 Documentation/ABI/testing/sysfs-uim
diff --git a/Documentation/ABI/testing/sysfs-uim b/Documentation/ABI/testing/sysfs-uim
new file mode 100644
index 0000000..899aa4d
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-uim
@@ -0,0 +1,24 @@
+What: /sys/uim
+Date: March 22
+Contact: Pavan Savoy <pavan_savoy@ti.com>
+Description:
+ Create a new kobject to pass information about the
+ N_TI_SHARED line discipline created to application/daemon
+ which would install/un-install line discipline.
+
+What: /sys/uim/pid
+Date: March 22
+Contact: Pavan Savoy <pavan_savoy@ti.com>
+Description:
+ The daemon/application wanting to use the line discipline
+ N_TI_SHARED will write in it's process Id, for the LDISC
+ driver to send SIGUSR2 signal to the process whenever a
+ upper layer protocol driver wants to make use of the LDISC
+ driver.
+
+What: /sys/uim/protocols
+Date: March 22
+Contact: Pavan Savoy <pavan_savoy@ti.com>
+Description:
+ List the protocols currently making use of the LDISC to ensure
+ LDISC is not un-installed when BT/FM or GPS is making use of it.
--
1.5.4.3
next prev parent reply other threads:[~2010-03-23 20:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 20:41 [v3] New ldisc for WiLink7.0 pavan_savoy
2010-03-23 20:41 ` [PATCH 1/7] serial: TTY: new ldisc for TI BT/FM/GPS chips pavan_savoy
2010-03-23 20:41 ` [PATCH 2/7] drivers:staging: Kconfig, Makefile for TI's ST ldisc pavan_savoy
2010-03-23 20:41 ` [PATCH 3/7] drivers:staging: sources for ST core pavan_savoy
2010-03-23 20:41 ` [PATCH 4/7] drivers:staging: sources for Init manager module pavan_savoy
2010-03-23 20:41 ` [PATCH 5/7] drivers:staging: sources for HCI LL PM protocol pavan_savoy
2010-03-23 20:41 ` [PATCH 6/7] drivers:staging: sources for ST header file pavan_savoy
2010-03-23 20:41 ` pavan_savoy [this message]
2010-03-24 2:29 ` [PATCH 7/7] Documentation/ABI: for N_TI_SHARED ldisc Greg KH
2010-03-24 2:28 ` [PATCH 2/7] drivers:staging: Kconfig, Makefile for TI's ST ldisc Greg KH
2010-03-24 2:30 ` Greg KH
2010-03-24 2:24 ` [PATCH 1/7] serial: TTY: new ldisc for TI BT/FM/GPS chips Marcel Holtmann
2010-03-24 2:48 ` Greg KH
2010-03-24 2:28 ` Greg KH
2010-03-24 8:43 ` Alan Cox
2010-03-24 15:49 ` Greg KH
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=1269376875-25940-8-git-send-email-pavan_savoy@ti.com \
--to=pavan_savoy@ti.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavan_savoy@yahoo.co.in \
/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
all inboxes | Powered by JetHome®