mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trilok Soni <soni.trilok@gmail.com>
To: Kyungmin Park <kmpark@infradead.org>
Cc: Jiri Slaby <jirislaby@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:21:18 +0530	[thread overview]
Message-ID: <5d5443650908230051wa8fa77cu280707281fe450ff@mail.gmail.com> (raw)
In-Reply-To: <9c9fda240908222145j1938baa3v3ecf8c5899ce3850@mail.gmail.com>

Hi Kyungmin,

On Sun, Aug 23, 2009 at 10:15 AM, Kyungmin Park<kmpark@infradead.org> wrote:
> 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.

I am looking at 3rd type, and evaulating that for embedded systems
devices having haptics chips can be programmed under drivers/input or
not. It is kind of early discussion and gathering inputs on what could
be lacking part in input subsystem for support such category of
devices.

Is it possible for you to submit your version of code and drivers? It
will be good starting point for discussion.


-- 
---Trilok Soni
http://triloksoni.wordpress.com
http://www.linkedin.com/in/triloksoni

  reply	other threads:[~2009-08-23  7:51 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
2009-08-23  7:51     ` Trilok Soni [this message]
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=5d5443650908230051wa8fa77cu280707281fe450ff@mail.gmail.com \
    --to=soni.trilok@gmail.com \
    --cc=jirislaby@gmail.com \
    --cc=kmpark@infradead.org \
    --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®