linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Bastien Nocera <hadess@hadess.net>
Cc: Alberto Mardegan <mardy@users.sourceforge.net>,
	linux-kernel@vger.kernel.org,
	"Javier S. Pedro" <maemo@javispedro.com>,
	linux-input@vger.kernel.org
Subject: Re: Reporting screen/laptop orientation data to userspace
Date: Mon, 6 Jun 2011 19:41:22 +0100	[thread overview]
Message-ID: <20110606194122.0fb8d46c@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <1307382639.2669.147.camel@novo.hadess.net>

> When an "change" event is received on an accelerometer,
> open its device node, and from the value, as well as the previous
> value of the property, calculate the device's new orientation,
> and export it as ID_INPUT_ACCELEROMETER_ORIENTATION.
>     
> Possible values are:
> * undefined
> * normal
> * bottom-up
> * left-up
> * right-up

For quite a few of the discrete accelerometers not being used in
'joystick' mode this would make quite a sensible input interface,
at least for those that generate inputs for their transitions.

You need a couple more values though because some devices care if they
are held up/down/left/right or if they are lying flat on their front or
on their back.

Phones for example sometimes go to speakerphone if laid flat on their
back, and go into silent mode if turned over.

Alan

  reply	other threads:[~2011-06-06 18:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-29  7:49 Reporting screen/laptop orientation data to userspace Alberto Mardegan
2011-06-02 22:19 ` Pavel Machek
2011-06-03 15:55 ` Bastien Nocera
2011-06-04 17:13   ` Mohamed Ikbel Boulabiar
2011-06-06 17:53     ` Bastien Nocera
2011-06-06  6:53   ` Alberto Mardegan
2011-06-06  8:42     ` Jonathan Cameron
2011-06-06 17:50     ` Bastien Nocera
2011-06-06 18:41       ` Alan Cox [this message]
2011-06-20 14:53         ` Bastien Nocera

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=20110606194122.0fb8d46c@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=hadess@hadess.net \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maemo@javispedro.com \
    --cc=mardy@users.sourceforge.net \
    /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).