From: simon@mungewell.org
To: "Dan Murphy" <dmurphy@ti.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org,
"\"Michal Malý\"" <madcatxster@devoid-pointer.net>,
"Elias Vanderstuyft" <elias.vds@gmail.com>
Subject: Re: [v2] input: drv260x: Add TI drv260x haptics driver
Date: Mon, 28 Jul 2014 13:59:34 -0400 [thread overview]
Message-ID: <5adf0339146a7b655a77053195aa892c.squirrel@mungewell.org> (raw)
In-Reply-To: <20140728174334.GD8982@core.coreip.homeip.net>
>> The initial driver supports the devices
>> real time playback mode. But the device
>> has additional wave patterns in ROM.
>
> As it presented the device appears to be a memoryless device, however
> you present it to the rest of the system as if it can support playback
> of multiple effects simultaneously, which is incorrect.
>
> My guess that you need to engage the memoryless input library to schedule
> handling multiple effects for your device, including ramping up, ramping
> down, stopping playback when effects runs out, etc.
Hi Dan,
Elias and Michal (cc'ed) are working on a kernel/userland library to
handle sending multiple force feedback signals to 'simple' devices,
perhaps you should engage with them.
Simon
next prev parent reply other threads:[~2014-07-28 18:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 16:53 Dan Murphy
2014-07-28 17:43 ` Dmitry Torokhov
2014-07-28 17:59 ` simon [this message]
2014-07-28 21:21 ` Murphy, Dan
2014-07-29 12:08 ` Michal Malý
2014-07-29 13:41 ` Murphy, Dan
2014-07-28 18:02 ` Murphy, Dan
2014-07-29 9:37 ` Mark Rutland
2014-07-29 13:50 ` Murphy, Dan
2014-07-29 14:39 ` Mark Rutland
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=5adf0339146a7b655a77053195aa892c.squirrel@mungewell.org \
--to=simon@mungewell.org \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=elias.vds@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madcatxster@devoid-pointer.net \
/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®