From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hui Wang Subject: =?UTF-8?B?UmU6IOetlOWkjTog562U5aSNOiDnrZTlpI06IFtQQVRDSF0gaW5wdXQ6?= =?UTF-8?Q?_alps-fix_the_issue_the_special_alps_trackpoint_do_not_work=2e?= Date: Fri, 24 May 2019 15:37:57 +0800 Message-ID: References: <345b62e1-407e-7a03-9b03-486bbf5a0a8e@canonical.com> <20190521094622.syeub6tcqhbyc7sg@pali> <20190522063546.kb74mxeprkauicul@pali> <20190522074030.64sy7xt3wnomtxjb@pali> <20190523060154.GA10526@jelly> <38ec4a40-d51a-aeb1-a5e8-dbaed1142298@canonical.com> <20190524053648.GA16379@jelly> <20190524072648.6zqgz7rpwpcv22pb@pali> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: <20190524072648.6zqgz7rpwpcv22pb@pali> Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org To: =?UTF-8?Q?Pali_Roh=c3=a1r?= Cc: Peter Hutterer , Xiaoxiao Liu , dmitry.torokhov@gmail.com, XiaoXiao Liu , "linux-input@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Xiaojian Cao , "zhangfp1@lenovo.com" List-Id: linux-input@vger.kernel.org On 2019/5/24 下午3:26, Pali Rohár wrote: > On Friday 24 May 2019 13:50:53 Hui Wang wrote: >> On 2019/5/24 下午1:36, Peter Hutterer wrote: >>> On Fri, May 24, 2019 at 01:25:52PM +0800, Hui Wang wrote: >>>> On 2019/5/23 下午2:01, Peter Hutterer wrote: >>>>> On Wed, May 22, 2019 at 09:40:30AM +0200, Pali Rohár wrote: >>>>>> On Wednesday 22 May 2019 07:30:43 Xiaoxiao Liu wrote: >>>>>>> Hi Pali, >>>>>>> >>>>>>> Ok, and cannot you set ALPS_DUALPOINT flag based on that >>>>>>> alps_check_is_trackpoint() result and then update >>>>>>> alps_process_packet_ss4_v3() code to supports also >>>>>>> V8 trackpoint packets? >>>>>>> --> Yes, we can do like so, when we use the v8 method to process the trackpoint , the mouse speed is not ideal. >>>>>>> Then we choose the standard mouse driver. >>>>>> Mouse speed is something which is configurable. Have you configured it >>>>>> somehow? Also there is libinput project should handle these settings >>>>>> more properly. >>>>>> >>>>>> Adding Peter Hutterer, maintainer of libinput to loop. I think he could >>>>>> help with this problem. >>>>> libinput has a quirk for a magic multiplier on trackpoints. it was the only >>>>> solution I found that came close to "working" given that every device seems >>>>> to provide some other random magic data. Doc for it is here: >>>>> https://wayland.freedesktop.org/libinput/doc/latest/trackpoint-configuration.html >>>> Hello Peter Hutterer, >>>> >>>> To adjust the trackpoint speed from userspace: >>>> >>>> If the libinput version is lower than 1.9.0, we could set >>>> POINTINGSTICK_CONST_ACCEL=0.25 >>>> >>>> If the libinput version is higher than 1.12.0, we could set >>>> AttrTrackpointMultiplier=0.25 >>>> >>>> But if we use libinput-1.10.0,  how could we adjust the speed? >>> The LIBINPUT_ATTR_TRACKPOINT_RANGE property, which didn't end up working >>> well (hence why it got replaced again). See the docs here though: >>> https://wayland.freedesktop.org/libinput/doc/1.10.0/trackpoints.html >>> >>> Cheers, >>> Peter >> OK, got it, Thanks. > Is not here some database where for input device name / id is specified > that property? So users do not have to invent what is correct value for > their hardware? Since the libinput version in the ubuntu 18.04 is 1.10,  I tried to set LIBINPUT_ATTR_TRACKPOINT_RANGE with different values (from 25, 20, 10, 5) in the udev hwdb database, I checked it with "udevadm info /dev/input/eventX" to confirm the value is set to LIBINPUT_ATTR_TRACKPOINT_RANGE successfully, but looks like the cursor speed doesn't change at all. So for ubuntu 18.04,  looks like we have to adjust the speed in the kernel driver. Thanks, Hui.