From: Vasyl Vavrychuk <vasyl.vavrychuk@opensynergy.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: <virtualization@lists.linux-foundation.org>,
<linux-kernel@vger.kernel.org>, <linux-input@vger.kernel.org>,
<stable@vger.kernel.org>, Jason Wang <jasowang@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Henrik Rydberg <rydberg@bitmath.org>,
Mathias Crombez <mathias.crombez@faurecia.com>
Subject: Re: [PATCH RESEND v2] virtio-input: add multi-touch support
Date: Sat, 19 Dec 2020 01:25:15 +0200 [thread overview]
Message-ID: <84310558-729b-d6d0-cf1a-e48febc3f001@opensynergy.com> (raw)
In-Reply-To: <20201209030635-mutt-send-email-mst@kernel.org>
On 09.12.20 10:28, Michael S. Tsirkin wrote:
> On Tue, Dec 08, 2020 at 11:01:50PM +0200, Vasyl Vavrychuk wrote:
>> From: Mathias Crombez <mathias.crombez@faurecia.com>
>> Cc: stable@vger.kernel.org
>
> I don't believe this is appropriate for stable, looks like
> a new feature to me.
Agree, removed.
>>
>> +config VIRTIO_INPUT_MULTITOUCH_SLOTS
>> + depends on VIRTIO_INPUT
>> + int "Number of multitouch slots"
>> + range 0 64
>> + default 10
>> + help
>> + Define the number of multitouch slots used. Default to 10.
>> + This parameter is unused if there is no multitouch capability.
>> +
>> + 0 will disable the feature.
>> +
>
> Most people won't be using this config so the defaults matter. So why 10? 10 fingers?
>
> And where does 64 come from?
I have sent v3 version where number of slots it obtained from the host.
>> + if (is_mt)
>> + input_mt_init_slots(vi->idev,
>> + CONFIG_VIRTIO_INPUT_MULTITOUCH_SLOTS,
>> + INPUT_MT_DIRECT);
>
>
> Do we need the number in config space maybe? And maybe with a feature
> bit so host can find out whether guest supports MT?
I think it is not applicable in v3 which I sent, because number of slots
is commit from the host. So, now host controls whether guest support MT.
prev parent reply other threads:[~2020-12-18 23:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 21:01 Vasyl Vavrychuk
2020-12-08 22:05 ` Dmitry Torokhov
2020-12-18 23:20 ` Vasyl Vavrychuk
2020-12-09 7:01 ` Greg KH
2020-12-09 8:28 ` Michael S. Tsirkin
2020-12-18 23:25 ` Vasyl Vavrychuk [this message]
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=84310558-729b-d6d0-cf1a-e48febc3f001@opensynergy.com \
--to=vasyl.vavrychuk@opensynergy.com \
--cc=jasowang@redhat.com \
--cc=kraxel@redhat.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias.crombez@faurecia.com \
--cc=mst@redhat.com \
--cc=rydberg@bitmath.org \
--cc=stable@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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®