public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: linux-input@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Vojtech Pavlik <vojtech@suse.cz>
Subject: [PATCH 6/8] Input: docs - note that MT-A protocol is obsolete
Date: Sat, 15 Apr 2017 22:11:43 -0700	[thread overview]
Message-ID: <20170416051145.13618-6-dmitry.torokhov@gmail.com> (raw)
In-Reply-To: <20170416051145.13618-1-dmitry.torokhov@gmail.com>

Everyone should be using multitouch protocol B (slotted) now.

Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
---
 Documentation/input/multi-touch-protocol.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/input/multi-touch-protocol.rst b/Documentation/input/multi-touch-protocol.rst
index 81775d7c1997..8035868c56bc 100644
--- a/Documentation/input/multi-touch-protocol.rst
+++ b/Documentation/input/multi-touch-protocol.rst
@@ -22,6 +22,9 @@ describes how to send the raw data for all contacts to the receiver. For
 devices capable of tracking identifiable contacts (type B), the protocol
 describes how to send updates for individual contacts via event slots.
 
+.. note::
+   MT potocol type A is obsolete, all kernel drivers have been
+   converted to use type B.
 
 Protocol Usage
 --------------
@@ -400,9 +403,6 @@ in a finger packet must not be recognized as single-touch events.
 For type A devices, all finger data bypasses input filtering, since
 subsequent events of the same type refer to different fingers.
 
-For example usage of the type A protocol, see the bcm5974 driver. For
-example usage of the type B protocol, see the hid-egalax driver.
-
 .. [#f1] Also, the difference (TOOL_X - POSITION_X) can be used to model tilt.
 .. [#f2] The list can of course be extended.
 .. [#f3] The mtdev project: http://bitmath.org/code/mtdev/.
-- 
2.12.2.762.g0e3151a226-goog

  parent reply	other threads:[~2017-04-16  5:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-16  5:11 [PATCH 1/8] Input: move documentation for Amiga CD32 Dmitry Torokhov
2017-04-16  5:11 ` [PATCH 2/8] Input: rotary-encoder - remove references to platform data from docs Dmitry Torokhov
2017-04-16  5:11 ` [PATCH 3/8] Input: fix "Game console" heading level in joystick documentation Dmitry Torokhov
2017-04-16  5:11 ` [PATCH 4/8] Input: docs - remove disclaimer/GPL notice Dmitry Torokhov
2017-04-16  5:11 ` [PATCH 5/8] Input: docs - update joystick documentation a bit Dmitry Torokhov
2017-04-16  5:11 ` Dmitry Torokhov [this message]
2017-04-16  5:11 ` [PATCH 7/8] Input: docs - split input docs into kernel- and user-facing Dmitry Torokhov
2017-04-16 14:08   ` Mauro Carvalho Chehab
2017-04-16 14:50     ` Mauro Carvalho Chehab
2017-04-16  5:11 ` [PATCH 8/8] Input: docs - freshen up introduction Dmitry Torokhov

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=20170416051145.13618-6-dmitry.torokhov@gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=vojtech@suse.cz \
    /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