Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp2215724imm; Mon, 3 Sep 2018 23:35:35 -0700 (PDT) X-Google-Smtp-Source: ANB0VdabMebMpySyd2wFh5PJC41IARhJoyaEkh8VIBADbDDspFsHEPRMkftynJNcRVTqe6FYGHUh X-Received: by 2002:a63:bc0a:: with SMTP id q10-v6mr14990725pge.60.1536042935671; Mon, 03 Sep 2018 23:35:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1536042935; cv=none; d=google.com; s=arc-20160816; b=SQWclzqEwZjkVUIzNF8WUqdlPKSnEeYvwR9cq/0pCCi2GP0ElsEbLrPKYdFgElezHj HmDjZH1Ru5cjLBmBe4OJihSAUNozKbxYL39z9v5CrYY0VheH6XFg0gqd0K7fU7cTMod4 SXoeMpGqlFRxmt80P5qUFqyCm0T8amreSz3NKeU4CtuvIdsVcXLmUJQqWrF2+c6ocPwA rCKuVoeYyaRpLVhhW1AN28WOov+ii89M0YLSIwu0ZMhf3I5rZw7q3eVrQKmMh8Y86P7D GLFRFTdwuU3poyJh5nL3oQIWtrB2pmBlJpLzoj08xBMSZ+yZOTednWxP3z+MGM8y9OCD BUgg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:dkim-signature :arc-authentication-results; bh=epQwX8VindIobxw6Xv2LIlc2IzE321uDHdIjShC88/s=; b=e6GRRbXxz3JoOllBDRPj56cIiYfwUS6YawRl9pTEohYcIzLyMBUuuvEUvAo8WfQHgM ZAshNg+D0SUYG/A1LXI69zNV4v4WpuFdkfvpfnHpVvh8Kc6ituNlvOR3w96yYr5iNOQc +lpWTYaoiXgCkCBybfaJlolRj5pe3iIrF/teyHDsrS0QAdgf7ah/rF7PK9zJOFTcZ3Sx 6AQ312BXMjxFT6jFX60l8hF1hBSnRaZrKJN5MciiRf2POmj01+V891Mm88YGjW1SQGxx S9CMfIF/HZOR9VAo97gd861OWrRkyPYYXz5rMr9HXQUog8FWhwRPKlB/TxfVNOnEMmMR WQXg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@who-t.net header.s=fm1 header.b=e0qqtDsY; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b="qgbRaSf/"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 7-v6si19491726pgw.207.2018.09.03.23.35.20; Mon, 03 Sep 2018 23:35:35 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@who-t.net header.s=fm1 header.b=e0qqtDsY; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b="qgbRaSf/"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727583AbeIDK5T (ORCPT + 99 others); Tue, 4 Sep 2018 06:57:19 -0400 Received: from wnew1-smtp.messagingengine.com ([64.147.123.26]:60581 "EHLO wnew1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726377AbeIDK5T (ORCPT ); Tue, 4 Sep 2018 06:57:19 -0400 X-Greylist: delayed 307 seconds by postgrey-1.27 at vger.kernel.org; Tue, 04 Sep 2018 06:57:18 EDT Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailnew.west.internal (Postfix) with ESMTP id 8F10B4C1; Tue, 4 Sep 2018 02:28:31 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Tue, 04 Sep 2018 02:28:32 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=who-t.net; h=cc :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=epQwX8VindIobxw6Xv2LIlc2IzE321uDHdIjShC88/s=; b=e0qqtDsY ABsOQDTgfqnjaUsU7RRPPsfdZyDY5ltazJXkvpwNYKV0GFFPrx675OuJ0rTeQjWB AzbsIkqPctxJ72WqgGlUr3XcxH5nVdu5W9pvc87PU278Z712OXa/EvdzRQqkCFfI y+fj96n2wzY4BFyvlNIqQ9Hoe3svBO3bpKf6bvVoT0dRiD30VPNm/2r7o3dk8gw+ KS12wbprYmDLUyGPn8VklMtPWXKETqr4OVEUqLW495VPR/qC1mG1Ip/4EiGVBHRl T+eOSAw3J8n8m88NLNAgpSAYH0/AkKffk4wAtdGQh4KmTIXCCN7Hrf3FBeQ1dWbK uKNwf73iE3EZ4g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=epQwX8VindIobxw6Xv2LIlc2IzE32 1uDHdIjShC88/s=; b=qgbRaSf/xU/wBtze4Vv0D8juIRSm/M6mOiasnBRUNAiTd /V1o7tht7jvIbwWbaE0xLeC5aG5MC2WR1KXbQvWmN4loq0YrwN1lLz/XcpNtMzHf LJUdQAXptK7BR8T/VrywXxfISEDcB84aN21DwA1I69INxLHM5xhvdBKAD6Ll2xlO NNn5C2csBmIbBGasfOLAncwAH8sMRPeu/BYE0a7kxry+wQtk0fduz6Qo79sckA0t lwzMhS9/ehCJ7DxCQhluXeI0ufMntezLFnYRDmegO4Fmfa79RkCxkZml5LcTjhC/ DNBR8bfQGDNOw4T6ql0HN/nKD38XsXp0GRyKm1K8A== X-ME-Proxy: X-ME-Sender: Received: from jelly (167-179-166-29.a7b3a6.bne.nbn.aussiebb.net [167.179.166.29]) by mail.messagingengine.com (Postfix) with ESMTPA id EB48510299; Tue, 4 Sep 2018 02:28:26 -0400 (EDT) Date: Tue, 4 Sep 2018 16:28:24 +1000 From: Peter Hutterer To: Harry Cutts Cc: linux-input , LKML , Jiri Kosina , Dmitry Torokhov , Benjamin Tissoires , linux-doc@vger.kernel.org, Jonathan Corbet Subject: Re: [PATCH v2 1/5] Add the `REL_WHEEL_HI_RES` event code Message-ID: <20180904062824.GB1086@jelly> References: <20180830215622.47550-1-hcutts@chromium.org> <20180830215622.47550-2-hcutts@chromium.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180830215622.47550-2-hcutts@chromium.org> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 30, 2018 at 02:56:18PM -0700, Harry Cutts wrote: > This event code represents scroll reports from high-resolution wheels, > and will be used by future patches in this series. See the linux-input > "Reporting high-resolution scroll events" thread [0] for more details. > > [0]: https://www.spinics.net/lists/linux-input/msg57380.html > > Signed-off-by: Harry Cutts looks good to me, thanks. For the archives, the libinput issue filed for this is here: https://gitlab.freedesktop.org/libinput/libinput/issues/130 Cheers, Peter > --- > > Changes in v2: None > > Documentation/input/event-codes.rst | 11 ++++++++++- > include/uapi/linux/input-event-codes.h | 1 + > 2 files changed, 11 insertions(+), 1 deletion(-) > > diff --git a/Documentation/input/event-codes.rst b/Documentation/input/event-codes.rst > index a8c0873beb95..cef220c176a4 100644 > --- a/Documentation/input/event-codes.rst > +++ b/Documentation/input/event-codes.rst > @@ -190,7 +190,16 @@ A few EV_REL codes have special meanings: > * REL_WHEEL, REL_HWHEEL: > > - These codes are used for vertical and horizontal scroll wheels, > - respectively. > + respectively. The value is the number of "notches" moved on the wheel, the > + physical size of which varies by device. For high-resolution wheels (which > + report multiple events for each notch of movement, or do not have notches) > + this may be an approximation based on the high-resolution scroll events. > + > +* REL_WHEEL_HI_RES: > + > + - If a vertical scroll wheel supports high-resolution scrolling, this code > + will be emitted in addition to REL_WHEEL. The value is the (approximate) > + distance travelled by the user's finger, in microns. > > EV_ABS > ------ > diff --git a/include/uapi/linux/input-event-codes.h b/include/uapi/linux/input-event-codes.h > index 53fbae27b280..dad8d3890a3a 100644 > --- a/include/uapi/linux/input-event-codes.h > +++ b/include/uapi/linux/input-event-codes.h > @@ -708,6 +708,7 @@ > #define REL_DIAL 0x07 > #define REL_WHEEL 0x08 > #define REL_MISC 0x09 > +#define REL_WHEEL_HI_RES 0x0a > #define REL_MAX 0x0f > #define REL_CNT (REL_MAX+1) > > -- > 2.19.0.rc0.228.g281dcd1b4d0-goog >