From: Anssi Hannula <anssi.hannula@iki.fi>
To: "Michal Malý" <madcatxster@prifuk.cz>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
dmitry.torokhov@gmail.com, elias.vds@gmail.com, jkosina@suse.cz,
simon@mungewell.org
Subject: Re: [PATCH v2 1/4] Add ff-memless-next driver
Date: Mon, 24 Feb 2014 04:11:04 +0200 [thread overview]
Message-ID: <530AAA38.3090700@iki.fi> (raw)
In-Reply-To: <1651798.4YaLXnucpJ@geidi-prime>
24.02.2014 03:54, Michal Malý kirjoitti:
> I forgot to comment on this:
>> Stopped effects should still be able to be updated.
> Fair enough. I could not find a definitive answer to what is expected behavior
> in this case. As far as I can tell, there are following cases:
> - Effects with no duration and delay: they shall be updated right away.
> - Effects with delay: updated parameters shall be sent to the device at the
> correct time.
> - "Expired" effects with finite duration - ??? I assumed that effects with
> finite duration that have already finished playing cannot be updated because
> it does not seem to make much sense to do so.
"Expired" effects can always be played back again later - if that
happens, the updated parameters will be in effect.
> Shall such an effect be
> restarted when it is updated?
No.
> Is there any guideline I should stick to I am
> not aware of?
Only "3.7 Dynamic update of an effect" of input/ff.txt.
--
Anssi Hannula
--
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
WARNING: multiple messages have this Message-ID (diff)
From: Anssi Hannula <anssi.hannula@iki.fi>
To: "Michal Malý" <madcatxster@prifuk.cz>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
dmitry.torokhov@gmail.com, elias.vds@gmail.com, jkosina@suse.cz,
simon@mungewell.org
Subject: Re: [PATCH v2 1/4] Add ff-memless-next driver
Date: Mon, 24 Feb 2014 04:11:04 +0200 [thread overview]
Message-ID: <530AAA38.3090700@iki.fi> (raw)
In-Reply-To: <1651798.4YaLXnucpJ@geidi-prime>
24.02.2014 03:54, Michal Malý kirjoitti:
> I forgot to comment on this:
>> Stopped effects should still be able to be updated.
> Fair enough. I could not find a definitive answer to what is expected behavior
> in this case. As far as I can tell, there are following cases:
> - Effects with no duration and delay: they shall be updated right away.
> - Effects with delay: updated parameters shall be sent to the device at the
> correct time.
> - "Expired" effects with finite duration - ??? I assumed that effects with
> finite duration that have already finished playing cannot be updated because
> it does not seem to make much sense to do so.
"Expired" effects can always be played back again later - if that
happens, the updated parameters will be in effect.
> Shall such an effect be
> restarted when it is updated?
No.
> Is there any guideline I should stick to I am
> not aware of?
Only "3.7 Dynamic update of an effect" of input/ff.txt.
--
Anssi Hannula
next prev parent reply other threads:[~2014-02-24 2:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-23 23:24 [PATCH v2 0/4] Add ff-memless-next and make hid-lg4ff use it Michal Malý
2014-02-23 23:24 ` Michal Malý
2014-02-23 23:29 ` [PATCH v2 1/4] Add ff-memless-next driver Michal Malý
2014-02-23 23:29 ` Michal Malý
2014-02-24 0:32 ` Anssi Hannula
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 [this message]
2014-02-24 2:11 ` Anssi Hannula
2014-02-24 2:45 ` Michal Malý
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:32 ` Michal Malý
2014-02-23 23:34 ` [PATCH v2 3/4] hid-lg4ff: Add support for periodic effects Michal Malý
2014-02-23 23:34 ` Michal Malý
2014-02-23 23:36 ` [PATCH v2 4/4] hid-lg4ff: Add support for ramp effect Michal Malý
2014-02-23 23:36 ` 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:32 ` Anssi Hannula
2014-02-24 0:58 ` Michal Malý
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ý
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=530AAA38.3090700@iki.fi \
--to=anssi.hannula@iki.fi \
--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=madcatxster@prifuk.cz \
--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.