[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5d5443650910130413t6ecd3d54p214d8f80972ed128@mail.gmail.com>
Date: Tue, 13 Oct 2009 16:43:43 +0530
From: Trilok Soni <soni.trilok@...il.com>
To: Jani Nikula <ext-jani.1.nikula@...ia.com>
Cc: Kyungmin Park <kyungmin.park@...sung.com>,
linux-kernel@...r.kernel.org, linux-input@...r.kernel.org,
Dmitry Torokhov <dmitry.torokhov@...il.com>
Subject: Re: [PATCH 1/6] Haptic: add haptic class
Hi Kyungmin, Dmitry,
On Tue, Oct 13, 2009 at 4:05 PM, Jani Nikula
<ext-jani.1.nikula@...ia.com> wrote:
> On Wed, Oct 7, 2009 at 09:17, Kyungmin Park <kyungmin.park@...sung.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists