[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140514181402.GF30089@core.coreip.homeip.net>
Date: Wed, 14 May 2014 11:14:02 -0700
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Michal Malý <madcatxster@...oid-pointer.net>
Cc: linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
jkosina@...e.cz, elias.vds@...il.com, anssi.hannula@....fi,
simon@...gewell.org
Subject: Re: [PATCH v4 01/24] input: Add ff-memless-next module
On Sat, Apr 26, 2014 at 05:02:00PM +0200, Michal Malý wrote:
> +
> +/** input_ff_create_mlnx() - Register a device within ff-memless-next and
> + * the kernel force feedback system
> + * @dev: Pointer to the struct input_dev associated with the device.
> + * @data: Any device-specific data that shall be passed to the callback.
> + * function called by ff-memless-next when a force feedback action
> + * shall be performed.
> + * @control_effect: Pointer to the callback function.
> + * @update_date: Delay in milliseconds between two recalculations of periodic
> + * effects, ramp effects and envelopes. Note that this value will
> + * never be lower than (CONFIG_HZ / 1000) + 1 regardless of the
> + * value specified here. This is not a "hard" rate limiter.
> + * Userspace still can submit effects at a rate faster than
> + * this value.
The update rate change seems useful whether we use new ff implementation
or enhance the old one but I would prefer having a separate call to
control it.
Thanks.
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists