From: "Michal Malý" <madcatxster@prifuk.cz>
To: dmitry.torokhov@gmail.com, jkosina@suse.cz, elias.vds@gmail.com,
simon@mungewell.org, linux-input@vger.kernel.org
Subject: [PATCH 0/5] Add ff-memless-next and make hid-lg4ff use it
Date: Tue, 04 Feb 2014 23:06:53 +0100 [thread overview]
Message-ID: <1602354.DiHhm9tiaI@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 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.
Michal M.
Michal Malý (5):
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
INPUT: Remove the note that no driver currently uses ff-memless-next from KConfig
Documentation/input/ff-memless-next.txt | 149 ++++++
drivers/hid/Kconfig | 2 +-
drivers/hid/hid-lg4ff.c | 93 ++--
drivers/input/Kconfig | 11 +
drivers/input/Makefile | 2 +
drivers/input/ff-memless-next.c | 793 ++++++++++++++++++++++++++++++++
include/linux/input/ff-memless-next.h | 31 ++
7 files changed, 1045 insertions(+), 36 deletions(-)
--
1.8.5.3
--
--
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-04 22:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 22:06 Michal Malý [this message]
2014-02-04 22:10 ` [PATCH 1/5] Add ff-memless-next Michal Malý
2014-02-04 22:11 ` [PATCH 2/5] Port hid-lg4ff to ff-memless-next Michal Malý
2014-02-04 22:12 ` [PATCH 3/5] Add support for periodic effects in hid-lg4ff Michal Malý
2014-02-04 22:13 ` [PATCH 4/5] Add support for ramp effect " Michal Malý
2014-02-04 22:14 ` [PATCH 5/5] Remove the note that no driver currently uses ff-memless-next Michal Malý
[not found] ` <CADbOyBS8C+OR5D6EhNCY4O-nMsb5XXdHmkN+8wzj=vT7kXy4pw@mail.gmail.com>
2014-02-04 23:54 ` [PATCH 2/5] Port hid-lg4ff to ff-memless-next Michal Malý
2014-02-05 0:03 ` Michal Malý
2014-02-05 0:08 ` simon
[not found] ` <CADbOyBSXKvRpTB-3NezDhFwggrD7i7qS9e6Aa4JWUe_BynVH3g@mail.gmail.com>
2014-02-05 9:35 ` Michal Malý
2014-02-20 15:16 ` Jiri Kosina
2014-02-20 15:32 ` 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=1602354.DiHhm9tiaI@geidi-prime \
--to=madcatxster@prifuk.cz \
--cc=dmitry.torokhov@gmail.com \
--cc=elias.vds@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.