linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michal Malý" <madcatxster@prifuk.cz>
To: Anssi Hannula <anssi.hannula@iki.fi>
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 03:45:01 +0100	[thread overview]
Message-ID: <2308366.HeZmROk36g@geidi-prime> (raw)
In-Reply-To: <530AAA38.3090700@iki.fi>

On Monday 24 of February 2014 04:11:04 Anssi Hannula wrote:
> 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.
Okay, let me make this clear. When an effect "expires", update of its 
parameters shall not trigger a restart, therefore it will not play. However, 
when its parameters are updated and the effect is started again at some point, 
the updated parameters shall be used. I will double-check this just to be on 
the safe side, but MLNX always stores the updated parameters no matter what 
the status of the effect is, so it should behave exactly as you suggest. 
Perhaps it was just me misinterpreting the semantics of "update"?

To bring this to a conclusion:
- Do you think that this work is worth mainlining?
- If it is, what do you suggest I change?

Thanks a lot for your input.

Michal M.
--
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

  reply	other threads:[~2014-02-24  2:45 UTC|newest]

Thread overview: 15+ 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:29 ` [PATCH v2 1/4] Add ff-memless-next driver Michal Malý
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
2014-02-24  2:45         ` Michal Malý [this message]
2014-02-23 23:32 ` [PATCH v2 2/4] Port hid-lg4ff to ff-memless-next Michal Malý
2014-02-23 23:34 ` [PATCH v2 3/4] hid-lg4ff: Add support for periodic effects Michal Malý
2014-02-23 23:36 ` [PATCH v2 4/4] hid-lg4ff: Add support for ramp effect 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:58   ` Michal Malý
2014-02-24 21:17     ` Elias Vanderstuyft
2014-02-24 21:48       ` Dmitry Torokhov
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=2308366.HeZmROk36g@geidi-prime \
    --to=madcatxster@prifuk.cz \
    --cc=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=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 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).