From: "Michal Malý" <madcatxster@prifuk.cz>
To: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: dmitry.torokhov@gmail.com, anssi.hannula@gmail.com,
elias.vds@gmail.com, jkosina@suse.cz, simon@mungewell.org
Subject: [PATCH v2 0/4] Add ff-memless-next and make hid-lg4ff use it
Date: Mon, 24 Feb 2014 00:24:02 +0100 [thread overview]
Message-ID: <1516865.M993BQAYe4@geidi-prime> (raw)
Hi everybody,
this patch series is a result of my work to improve FFB support for memoryless
devices. ff-memless-next is an improvement over the currently available
ff-memless which is well suited for joypads but cannot handle more advanced
devices such as racing wheels properly. As I have explained in one of RFCs
regarding ff-memless-next, the extent of the changes makes implementing
ff-memless-next as a patch to ff-memless unfeasible. As of now there is a total
of 27 drivers using ff-memless (including lg4ff) - a lot of them joypads.
I do not have access to any FFB joypad at the moment so I cannot
implement the functionality required to handle joypads properly - namely FF_RUMBLE
and emulation of FF_PERIODIC through FF_RUMBLE.
The plan is to implement the missing functionality and replace ff-memless completely
in the future.
Second part of this series ports lg4ff driver over to ff-memless-next.
The immediate benefit of this is support of all periodic effects and ramp effect.
v2 addresses a few issues that have not been noticed at the time v1 was
submitted. Specific fixes are mentioned in the respective patches.
Michal M.
Michal Malý (4):
INPUT: Add ff-memless-next module
HID: Port hid-lg4ff to ff-memless-next
HID: Add support for periodic effects in hid-lg4ff
HID: Add support for ramp effect in hid-lg4ff
Documentation/input/ff-memless-next.txt | 141 ++++++
drivers/hid/Kconfig | 2 +-
drivers/hid/hid-lg4ff.c | 93 ++--
drivers/input/Kconfig | 11 +
drivers/input/Makefile | 1 +
drivers/input/ff-memless-next.c | 789 ++++++++++++++++++++++++++++++++
include/linux/input/ff-memless-next.h | 32 ++
7 files changed, 1033 insertions(+), 36 deletions(-)
--
1.9.0
--
--
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 reply other threads:[~2014-02-23 23:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-23 23:24 Michal Malý [this message]
2014-02-23 23:29 ` [PATCH v2 1/4] Add ff-memless-next driver Michal Malý
2014-02-24 0:32 ` Anssi Hannula
2014-02-24 1:18 ` Michal Malý
2014-02-24 1:54 ` Michal Malý
2014-02-24 2:11 ` Anssi Hannula
2014-02-24 2:45 ` Michal Malý
2014-02-23 23:32 ` [PATCH v2 2/4] Port hid-lg4ff to ff-memless-next Michal Malý
2014-02-23 23:34 ` [PATCH v2 3/4] hid-lg4ff: Add support for periodic effects Michal Malý
2014-02-23 23:36 ` [PATCH v2 4/4] hid-lg4ff: Add support for ramp effect Michal Malý
2014-02-24 0:32 ` [PATCH v2 0/4] Add ff-memless-next and make hid-lg4ff use it Anssi Hannula
2014-02-24 0:58 ` Michal Malý
2014-02-24 21:17 ` Elias Vanderstuyft
2014-02-24 21:48 ` Dmitry Torokhov
2014-02-24 22:11 ` Michal Malý
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=1516865.M993BQAYe4@geidi-prime \
--to=madcatxster@prifuk.cz \
--cc=anssi.hannula@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=elias.vds@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=simon@mungewell.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).