linux-kernel - Re: [PATCH 1/6] Haptic: add haptic class

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <359ed6810910130335m45919d6ala921d4cbfa5a341a@mail.gmail.com>
Date:	Tue, 13 Oct 2009 13:35:47 +0300
From:	Jani Nikula <ext-jani.1.nikula@...ia.com>
To:	Kyungmin Park <kyungmin.park@...sung.com>
Cc:	linux-kernel@...r.kernel.org, linux-input@...r.kernel.org,
	soni.trilok@...il.com
Subject: Re: [PATCH 1/6] Haptic: add haptic class

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?

BR,
Jani.
--
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/