From: Trilok Soni <soni.trilok@gmail.com>
To: Jani Nikula <ext-jani.1.nikula@nokia.com>
Cc: Kyungmin Park <kyungmin.park@samsung.com>,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: [PATCH 1/6] Haptic: add haptic class
Date: Tue, 13 Oct 2009 16:43:43 +0530 [thread overview]
Message-ID: <5d5443650910130413t6ecd3d54p214d8f80972ed128@mail.gmail.com> (raw)
In-Reply-To: <359ed6810910130335m45919d6ala921d4cbfa5a341a@mail.gmail.com>
Hi Kyungmin, Dmitry,
On Tue, Oct 13, 2009 at 4:05 PM, Jani Nikula
<ext-jani.1.nikula@nokia.com> wrote:
> On Wed, Oct 7, 2009 at 09:17, Kyungmin Park <kyungmin.park@samsung.com> wrote:
>> New haptic class support.
>> This class handles the haptic devices.
>
> I'm wondering why a haptic class is needed when there is force
> feedback support. Admittedly, I don't know the force feedback
> implementation too well, but could someone please enlighten me on
> this? Am I missing something here?
>
> I see haptics as simple force feedback, just with (usually) small
> force and short duration. There are devices out there doing haptics
> using vibra motors, which I think would be limited if implemented
> using this haptics class driver. Would it be somehow problematic
> interfacing with the simple haptic hardware using the force feedback
> API?
Please share your inputs on ff_device usage instead of haptics class.
I think Dmitry could add some points here as I don't see much users of
ff_device and I don't see any embedded device (like mobile) using it.
--
---Trilok Soni
http://triloksoni.wordpress.com
http://www.linkedin.com/in/triloksoni
next prev parent reply other threads:[~2009-10-13 11:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 6:17 Kyungmin Park
2009-10-07 7:09 ` Trilok Soni
2009-10-13 10:35 ` Jani Nikula
2009-10-13 11:13 ` Trilok Soni [this message]
2009-10-14 7:59 ` Dmitry Torokhov
2009-10-14 10:38 ` 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=5d5443650910130413t6ecd3d54p214d8f80972ed128@mail.gmail.com \
--to=soni.trilok@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=ext-jani.1.nikula@nokia.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®