mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Oleksandr Andrushchenko <andr2000@gmail.com>,
	xen-devel@lists.xenproject.org, linux-input@vger.kernel.org,
	linux-kernel@vger.kernel.org, dmitry.torokhov@gmail.com,
	lyan@suse.com, boris.ostrovsky@oracle.com
Cc: konrad.wilk@oracle.com, andrii_chepurnyi@epam.com,
	Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Subject: Re: [PATCH v5 3/3] Input: xen-kbdfront - allow better run-time configuration
Date: Tue, 12 Jun 2018 15:50:08 +0200	[thread overview]
Message-ID: <5fbac8d0-a3cf-af8a-690e-947752a53ab6@suse.com> (raw)
In-Reply-To: <20180612074856.28451-4-andr2000@gmail.com>

On 12/06/18 09:48, Oleksandr Andrushchenko wrote:
> From: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
> 
> It is now only possible to control if multi-touch virtual device
> is created or not (via the corresponding XenStore entries),
> but keyboard and pointer devices are always created.
> In some cases this is not desirable. For example, if virtual
> keyboard device is exposed to Android then the latter won't
> automatically show on-screen keyboard as it expects that a
> physical keyboard device can be used for typing.
> 
> Utilize keyboard and pointer device XenStore feature fields to
> configure which virtual devices are created:
>  - set "feature-disable-keyboard" to 1 if no keyboard device
>    needs to be created
>  - set "feature-disable-pointer" to 1 if no pointer device
>    needs to be created
> Keep old behavior by default.
> 
> Signed-off-by: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
> Suggested-by: Andrii Chepurnyi <andrii_chepurnyi@epam.com>
> Tested-by: Andrii Chepurnyi <andrii_chepurnyi@epam.com>

Reviewed-by: Juergen Gross <jgross@suse.com>


Juergen

  reply	other threads:[~2018-06-12 13:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-12  7:48 [PATCH v5 0/3] " Oleksandr Andrushchenko
2018-06-12  7:48 ` [PATCH v5 1/3] xen: Sync up with the canonical protocol definitions in Xen Oleksandr Andrushchenko
2018-06-12 13:46   ` Juergen Gross
2018-06-12 13:47     ` Oleksandr Andrushchenko
2018-06-12 23:40     ` Dmitry Torokhov
2018-06-13  5:49       ` Oleksandr Andrushchenko
2018-06-13  6:11         ` Dmitry Torokhov
2018-06-13  6:13           ` Oleksandr Andrushchenko
2018-06-13  6:25             ` Dmitry Torokhov
2018-06-13  6:28               ` Oleksandr Andrushchenko
2018-06-13  6:40             ` Juergen Gross
2018-06-13  6:43               ` Oleksandr Andrushchenko
2018-06-12  7:48 ` [PATCH v5 2/3] Input: xen-kbdfront - fix multi-touch XenStore node's locations Oleksandr Andrushchenko
2018-06-12 13:47   ` Juergen Gross
2018-06-12  7:48 ` [PATCH v5 3/3] Input: xen-kbdfront - allow better run-time configuration Oleksandr Andrushchenko
2018-06-12 13:50   ` Juergen Gross [this message]
2018-06-12 22:07   ` Dmitry Torokhov
2018-06-13  5:47     ` Oleksandr Andrushchenko

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=5fbac8d0-a3cf-af8a-690e-947752a53ab6@suse.com \
    --to=jgross@suse.com \
    --cc=andr2000@gmail.com \
    --cc=andrii_chepurnyi@epam.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lyan@suse.com \
    --cc=oleksandr_andrushchenko@epam.com \
    --cc=xen-devel@lists.xenproject.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

all inboxes | Powered by JetHome®