From: Randy Dunlap <rdunlap@infradead.org>
To: "Michal Malý" <madcatxster@prifuk.cz>, linux-input@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, elias.vds@gmail.com, joe@perches.com
Subject: Re: [RFC v3] Add ff-memless-next
Date: Tue, 24 Dec 2013 11:38:03 -0800 [thread overview]
Message-ID: <52B9E29B.1040005@infradead.org> (raw)
In-Reply-To: <1494187.y8mYFDm1lA@geidi-prime>
On 12/23/13 14:46, Michal Malý wrote:
> ---
> Documentation/input/ff-memless-next.txt | 145 ++++++
> drivers/input/Kconfig | 12 +
> drivers/input/Makefile | 2 +
> drivers/input/ff-memless-next.c | 786 ++++++++++++++++++++++++++++++++
> include/linux/input/ff-memless-next.h | 31 ++
> 5 files changed, 976 insertions(+)
> create mode 100644 Documentation/input/ff-memless-next.txt
> create mode 100644 drivers/input/ff-memless-next.c
> create mode 100644 include/linux/input/ff-memless-next.h
>
> diff --git a/Documentation/input/ff-memless-next.txt b/Documentation/input/ff-memless-next.txt
> new file mode 100644
> index 0000000..00f893d
> --- /dev/null
> +++ b/Documentation/input/ff-memless-next.txt
> @@ -0,0 +1,145 @@
> +"ff-memless-next" force feedback module for memoryless devices.
> +By Michal Malý <madcatxster@prifuk.cz> on 2013/12/21
> +----------------------------------------------------------------------------
> +
> +1. Introduction
> +~~~~~~~~~~~~~~~
> +This document describes basic working principles of the "ff-memless-next"
driver
(or module)
> +and its purpose. This document also contains summary of "ff-memless-next" API
a summary of the
> +and brief instructions on how to use it to write a hardware-specific backend
> +with "ff-memless-next". Some specifics of ff-memless-next that might be of
> +interest for userspace developers are also discussed.
> diff --git a/drivers/input/Kconfig b/drivers/input/Kconfig
> index a11ff74..893ab00 100644
> --- a/drivers/input/Kconfig
> +++ b/drivers/input/Kconfig
> @@ -77,6 +77,18 @@ config INPUT_MATRIXKMAP
> To compile this driver as a module, choose M here: the
> module will be called matrix-keymap.
>
> +config INPUT_FF_MEMLESS_NEXT
> + tristate "New version of support for memoryless force feedback devices"
> + help
> + Say Y here if you want to enable support for various memoryless
> + force feedback devices (as of now there is no hardware-specific
> + driver that supports this)
this).
> +
> + If unsure, say N.
> +
> + To compile this driver as a module, choose M here: the
> + module will be called ff-memless-next.
> +
> comment "Userland interfaces"
>
> config INPUT_MOUSEDEV
--
~Randy
--
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
prev parent reply other threads:[~2013-12-24 19:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 22:46 [RFC v3] Add ff-memless-next Michal Malý
2013-12-24 0:21 ` Joe Perches
2013-12-24 2:11 ` Michal Malý
2013-12-24 19:38 ` Randy Dunlap [this message]
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=52B9E29B.1040005@infradead.org \
--to=rdunlap@infradead.org \
--cc=elias.vds@gmail.com \
--cc=joe@perches.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madcatxster@prifuk.cz \
/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).