public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kyungmin Park <kyungmin.park@samsung.com>
To: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Cc: soni.trilok@gmail.com
Subject: [PATCH 2/6] Haptic: Documentation for haptic class (v2)
Date: Fri, 09 Oct 2009 18:01:20 +0900	[thread overview]
Message-ID: <20091009090120.GA24935@july> (raw)

Describe the haptic class and how to use

Changelog v1:
	Apply comments and feedbacks

Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
---
 Documentation/haptic-class.txt |   20 ++++++++++++++++++++
 1 files changed, 20 insertions(+), 0 deletions(-)
 create mode 100644 Documentation/haptic-class.txt

diff --git a/Documentation/haptic-class.txt b/Documentation/haptic-class.txt
new file mode 100644
index 0000000..6bee82a
--- /dev/null
+++ b/Documentation/haptic-class.txt
@@ -0,0 +1,20 @@
+
+Haptic handling under Linux
+========================
+
+In its simplest form, the haptic class just allows control of Haptics from
+userspace. Haptic appears in /sys/class/haptic/. The maximum level of the
+haptic is defined in max_level file.
+
+The interface is pretty simple - it provides oneshot mode where user
+can specify duration of the effect (in milliseconds) and desired level
+Of course, you can adjust the level by setting level property
+
+# echo ${millisecond} > /sys/class/haptic/<device>/oneshot
+
+# echo ${level} > /sys/class/haptic/<device>/level
+
+You can also enable or disable haptics devices by manipulating 'enable' attribute:
+
+# echo 1 > /sys/class/haptic/<device>/enable	-> Enable
+# echo 0 > /sys/class/haptic/<device>/enable	-> Disable
-- 
1.5.3.3


             reply	other threads:[~2009-10-09  9:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-09  9:01 Kyungmin Park [this message]
2009-10-09  9:29 ` [PATCH 2/6] Haptic: Documentation for haptic class (v2) Trilok Soni

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=20091009090120.GA24935@july \
    --to=kyungmin.park@samsung.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=soni.trilok@gmail.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