From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754923AbeASAuH (ORCPT ); Thu, 18 Jan 2018 19:50:07 -0500 Received: from mail-pf0-f194.google.com ([209.85.192.194]:40475 "EHLO mail-pf0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754793AbeASAt7 (ORCPT ); Thu, 18 Jan 2018 19:49:59 -0500 X-Google-Smtp-Source: ACJfBouyIkRbkDkIxBLV8nlquj5f40dXV2GfKGoi5evz8NgUGvmB6BZdDNvsgjnvUUgb2l/KENEcEg== From: Dmitry Torokhov To: Benjamin Tissoires , Lyude Paul , Damjan Georgievski Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, Andrew Duggan Subject: [PATCH 0/3] RMI4: improve trackpoint detection Date: Thu, 18 Jan 2018 16:49:52 -0800 Message-Id: <20180119004955.247190-1-dmitry.torokhov@gmail.com> X-Mailer: git-send-email 2.16.0.rc1.238.g530d649a79-goog Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, The following patch series is hopefully improves trackpint detection on systems using RMI4 and PS/2 guest modules. The issue was that we were registering port too early, before RMI driver was ready to service interrupts properly, so psmouse would try to get ID from the device and RMI driver would still be initializing other functions and interrupts would still be masked, so GetID would simply time out. Then we may or may not get interrupt from trackpoint and run through the detection again, but probably much later. Please take a look and hpefully give it a try. Damjan, I hope it might fix your issue with trackpoint appearing much much later. Thanks! -- Dmitry