From: Kyungmin Park <kmpark@infradead.org>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Trilok Soni <soni.trilok@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-input@vger.kernel.org
Subject: Re: haptics devices linux driver support
Date: Sun, 23 Aug 2009 13:45:40 +0900 [thread overview]
Message-ID: <9c9fda240908222145j1938baa3v3ecf8c5899ce3850@mail.gmail.com> (raw)
In-Reply-To: <4A902904.2090008@gmail.com>
Hi,
There's three types as I know,
1) just GPIO enable motor
2) GPIO & PWM motor.
3) I2C based GPIO & PWM motor.
Frankly we made a motor framework at kernel. but I 'm not sure motor
is right naming or not.
I think we need new framework. since it's not input device.
Thank you,
Kyungmin Park
On Sun, Aug 23, 2009 at 2:21 AM, Jiri Slaby<jirislaby@gmail.com> wrote:
> On 08/22/2009 07:04 PM, Trilok Soni wrote:
>> Does anyone know example Linux drivers for haptics devices?
>
> Yup, drivers/misc/phantom.c for Sensable Phantom (the old one over PCI).
> The rest needed (esp. floating point computation) is done in userspace.
>
> Then, all force-feedack drivers under drivers/input and drivers/hid.
>
> What exactly do you want to know?
> --
> To unsubscribe from this list: send the line "unsubscribe linux-input" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2009-08-23 4:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-22 17:04 Trilok Soni
2009-08-22 17:21 ` Jiri Slaby
2009-08-23 4:45 ` Kyungmin Park [this message]
2009-08-23 7:51 ` Trilok Soni
2009-08-24 16:36 ` Mohamed Ikbel Boulabiar
2009-09-07 11:29 ` Trilok Soni
2009-09-07 11:44 ` Joonyoung Shim
2009-09-07 12:26 ` Trilok Soni
2009-09-07 13:06 ` Kyungmin Park
2009-09-11 18:52 ` Pavel Machek
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=9c9fda240908222145j1938baa3v3ecf8c5899ce3850@mail.gmail.com \
--to=kmpark@infradead.org \
--cc=jirislaby@gmail.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
all inboxes | Powered by JetHome®