From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jari Vanhala <ext-jari.vanhala@nokia.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: [PATCH] HID: TWL4030: add HID Force Feedback vibra
Date: Sat, 20 Feb 2010 00:52:27 -0800 [thread overview]
Message-ID: <20100220085226.GA30739@core.coreip.homeip.net> (raw)
In-Reply-To: <1266497417.4787.2923.camel@tema>
On Thu, Feb 18, 2010 at 02:50:16PM +0200, Jari Vanhala wrote:
> On Wed, 2010-02-17 at 13:41 +0100, ext Jiri Kosina wrote:
> > On Wed, 17 Feb 2010, Jari Vanhala wrote:
> > As the device doesn't seem to be registering itself on the HID bus at all,
> > I am not sure we want to put it together with all the HID drivers. Maybe
> > drivers/input/misc would be more appropriate?
>
> I felt like I forgot something.. Well, moving it to input/misc is easy
> (commit attached), but I (still) wanted to try getting it to use
> hid-functions. Results weren't that nice. Looking hid-core just shows,
> it's thought to connect (hotplug) usb or bt devices and i2c doesn't fit
> nicely to that. Making it to use hid_allocate_device(), hid_connect()
> etc takes actually more code..
>
> Leaving it as-is in hid would look little odd, so probably moving it to
> drivers/input/misc is best thing. What you think? Dmitry?
>
I can take it into misc. Still need to review it though.
--
Dmitry
next prev parent reply other threads:[~2010-02-20 8:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 12:22 [PATCH] HID: TWL4030: add HID Force Feedback vibra Jari Vanhala
2010-02-17 12:41 ` Jiri Kosina
2010-02-18 12:50 ` Jari Vanhala
2010-02-18 12:52 ` Jiri Kosina
2010-02-20 8:52 ` Dmitry Torokhov [this message]
2010-02-22 6:40 ` Dmitry Torokhov
2010-02-22 13:19 ` Jari Vanhala
2010-02-22 18:38 ` Dmitry Torokhov
2010-02-23 8:40 ` Jari Vanhala
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=20100220085226.GA30739@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=ext-jari.vanhala@nokia.com \
--cc=jkosina@suse.cz \
--cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).