From: Benjamin Tissoires <benjamin.tissoires@redhat.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: Dmitry Torokhov <dtor@chromium.org>,
Henrik Rydberg <rydberg@bitmath.org>,
Wei-Ning Huang <wnhuang@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux Input <linux-input@vger.kernel.org>,
Peter Hutterer <peter.hutterer@who-t.net>
Subject: Re: [PATCH v4] HID: hid-multitouch: support fine-grain orientation reporting
Date: Wed, 11 Oct 2017 15:53:24 +0200 [thread overview]
Message-ID: <20171011135324.GI865@mail.corp.redhat.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.1710111529360.14384@jbgna.fhfr.qr>
On Oct 11 2017 or thereabouts, Jiri Kosina wrote:
> On Wed, 11 Oct 2017, Benjamin Tissoires wrote:
>
> > I am not sure if libinput even uses ABS_MT_ORIENTATION
>
> I don't think it does, so that should be okay. However ...
I had a meeting this Peter at noon today. The summary is that libinput
doesn't uses ABS_MT_ORIENTATION, and that the documentation requires
actually 3 things:
- 0 is Y-aligned, up ("north")
- maximum should be aligned with X, pointing toward the right ("east")
- negative and out of range values are allowed
>From this, we can conclude that the minimum doesn't matter, as long as
it is 0 or -max, it is the same from the user space point of view.
One thing that the documentation suggests is that if we report [0, max],
this would indicate that out of ranges values won't be triggered, and
[-max, max] would seem to indicate that the data might be negative and
so out of range values would be acceptable.
Anyway, no changes in any cases from userspace.
>
> > , but I'd go for fixing the documentation. And re-reading it, it's not
> > clear that the doc tells us to have [0,90]. It mentions negative values
> > and out of ranges too, so we might just as well simply clarify that we
> > rather have [-90,90], with 0 being "north".
>
> ... I'd like the documentation fix to go in together in one go with this
> patch if possible.
>
Sounds like a plan.
Cheers,
Benjamin
> Thanks,
>
> --
> Jiri Kosina
> SUSE Labs
>
next prev parent reply other threads:[~2017-10-11 13:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 4:16 Wei-Ning Huang
2017-10-10 6:57 ` Henrik Rydberg
2017-10-10 16:25 ` Dmitry Torokhov
2017-10-11 8:54 ` Benjamin Tissoires
2017-10-11 13:30 ` Jiri Kosina
2017-10-11 13:53 ` Benjamin Tissoires [this message]
2017-10-11 20:43 ` Henrik Rydberg
2017-10-11 22:24 ` Peter Hutterer
2017-10-10 7:40 ` 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=20171011135324.GI865@mail.corp.redhat.com \
--to=benjamin.tissoires@redhat.com \
--cc=dtor@chromium.org \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.hutterer@who-t.net \
--cc=rydberg@bitmath.org \
--cc=wnhuang@chromium.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
Powered by JetHome