Re: [PATCH v4 01/24] input: Add ff-memless-next module

From: Elias Vanderstuyft <elias.vds@gmail.com>
To: Roland Bosa <rbosa@logitech.com>
Cc: "Michal Malý" <madcatxster@devoid-pointer.net>,
	"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
	"open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Jiri Kosina" <jkosina@suse.cz>,
	"Anssi Hannula" <anssi.hannula@iki.fi>,
	"Simon Wood" <simon@mungewell.org>
Subject: Re: [PATCH v4 01/24] input: Add ff-memless-next module
Date: Wed, 21 May 2014 16:53:34 +0200	[thread overview]
Message-ID: <CADbOyBQxC+Epv1kz8jsBKNgYGFO0R-UPBXvn_qV8Sqb6rNw+Og@mail.gmail.com> (raw)
In-Reply-To: <537BCB63.1020200@logitech.com>

On Tue, May 20, 2014 at 11:38 PM, Roland Bosa <rbosa@logitech.com> wrote:
> On 05/20/2014 12:00 PM, Michal Malı wrote:
> There's a healthy amount of
> code in the Windows driver that you would call 'quirks' which deals with
> deciding how to allocate multiple springs and dampers to a single slot.

But 2 Spring effects with different offsets and non-zero effective
force can't be combined into a single slot (without streaming them
with Constant force), right?

> Sometimes, even the springs and dampers are being streamed in via the
> constants force, but that requires (as you pointed out earlier) a fast
> update rate and some "smartness"

OK, is this method used when all force-slots are already full?
Or is it only used for some specific (restricted) devices, such as
devices with only 2 force slots?

And in this case, is the position of the device monitored at a speed
higher than 8ms, in order to keep the feedback-loop stable?

Thanks,
Elias