linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Daniel Drake <dsd@laptop.org>
Cc: linux-input@vger.kernel.org, linux-hotplug@vger.kernel.org,
	hadess@hadess.net, Carlos Garnacho <carlosg@gnome.org>
Subject: Re: Communicating tablet mode status to userspace
Date: Tue, 02 Oct 2012 22:39:56 +0000	[thread overview]
Message-ID: <20121002233956.71b805e4@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <CAMLZHHS80_zdmgVtJ87w+fuQGC05yj+EoJt3C_zBC7hkyhnaoQ@mail.gmail.com>

> The change event would (presumably) trigger libudev's udev_monitor,
> which would be used by the on-screen keyboard software (maliit) to
> change its behaviour according to the property value.
> 
> Does this sound like a sensible plan, would these udev and kernel
> changes be acceptable? Or is there a better option that I'm missing?

Seems reasonable to me - but remember that a device can be in both tablet
and non tablet modes at once to different users once you have a wireless
display.

ie it's really not "tablet mode" it's "does this particular interface
have a keyboard"




  reply	other threads:[~2012-10-02 22:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-02 22:27 Communicating tablet mode status to userspace Daniel Drake
2012-10-02 22:39 ` Alan Cox [this message]
2012-10-02 23:36 ` Dmitry Torokhov
2012-10-03  2:58   ` Greg KH
2012-10-03 14:52   ` Daniel Drake
2012-10-03 15:05     ` Greg KH
2012-10-03 15:23       ` Kay Sievers
2012-10-03 16:04         ` Daniel Drake
2012-10-05 15:50           ` Bastien Nocera
2012-10-05 16:11             ` Daniel Drake
2012-10-05 16:40               ` Bastien Nocera
2012-10-04 13:35     ` Mark Brown

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=20121002233956.71b805e4@pyramind.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=carlosg@gnome.org \
    --cc=dsd@laptop.org \
    --cc=hadess@hadess.net \
    --cc=linux-hotplug@vger.kernel.org \
    --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).