X-Git-Url: http://git.efficios.com/?a=blobdiff_plain;f=Documentation%2Finput%2Fmulti-touch-protocol.txt;fp=Documentation%2Finput%2Fmulti-touch-protocol.txt;h=b85d000faeb4067c9ab1ed06690105d459a40a4e;hb=a736775db683174269c65c7c5cc8e5ee534e7681;hp=7b4f59c09ee2301d077446f5f9ce9c2b96aa2551;hpb=09d042a2eb90ee2c86d80c48ad096ae3f5776cef;p=deliverable%2Flinux.git

diff --git a/Documentation/input/multi-touch-protocol.txt b/Documentation/input/multi-touch-protocol.txt
index 7b4f59c09ee2..b85d000faeb4 100644
--- a/Documentation/input/multi-touch-protocol.txt
+++ b/Documentation/input/multi-touch-protocol.txt
@@ -312,9 +312,12 @@ ABS_MT_TOOL_TYPE
 
 The type of approaching tool. A lot of kernel drivers cannot distinguish
 between different tool types, such as a finger or a pen. In such cases, the
-event should be omitted. The protocol currently supports MT_TOOL_FINGER and
-MT_TOOL_PEN [2]. For type B devices, this event is handled by input core;
-drivers should instead use input_mt_report_slot_state().
+event should be omitted. The protocol currently supports MT_TOOL_FINGER,
+MT_TOOL_PEN, and MT_TOOL_PALM [2]. For type B devices, this event is handled
+by input core; drivers should instead use input_mt_report_slot_state().
+A contact's ABS_MT_TOOL_TYPE may change over time while still touching the
+device, because the firmware may not be able to determine which tool is being
+used when it first appears.
 
 ABS_MT_BLOB_ID