linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Orivej Desh <orivej@gmx.fr>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH] HID: gembird: add new driver to fix Gembird JPD-DualForce 2
Date: Wed, 12 Aug 2015 16:51:05 +0000	[thread overview]
Message-ID: <20150812165105.3bfd4516@orivej.orivej.org> (raw)
In-Reply-To: <20150812144028.GA31257@mail.corp.redhat.com>

-linux-kernel@vger.kernel.org
-jkosina@suse.com

* Benjamin Tissoires
> Hmm... This was actually my first shot, and I noticed that the
> flickering original Z axis was now taking over the correct X axis. So
> that's why I added some complexity to ignore at the HID level this axis.
> I just forgot to update the comment :)

How did you notice that?  Is there a tool in hid-replay?  I did not test
my edition of the patch extensively because I did not expect such a
subtle difference.  Yet I did not observe flickering when joypad was
idle.

I assumed that the commit that hid Rx axis in 3.18 by calling
"map_abs_clear(usage->hid & 0xf);" effectively removed any influence of
repeated axes in report description, but now it seems I am wrong.  Would
you explain what it really did?

> If you think this patch is good enough (you will get flickering X), we
> can carry on this one, but I think the one I submitted (with the comment
> edited) would provide a better experience.

In this case I certainly prefer your original patch.

  reply	other threads:[~2015-08-12 16:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-11 15:35 [PATCH] HID: gembird: add new driver to fix Gembird JPD-DualForce 2 Benjamin Tissoires
2015-08-12  1:32 ` Orivej Desh
2015-08-12 14:40   ` Benjamin Tissoires
2015-08-12 16:51     ` Orivej Desh [this message]
2015-08-12 17:34       ` Benjamin Tissoires

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=20150812165105.3bfd4516@orivej.orivej.org \
    --to=orivej@gmx.fr \
    --cc=benjamin.tissoires@redhat.com \
    --cc=linux-input@vger.kernel.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).