From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.5 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id DD120C12002 for ; Wed, 21 Jul 2021 13:40:48 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id CA32061279 for ; Wed, 21 Jul 2021 13:40:46 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238520AbhGUNAG (ORCPT ); Wed, 21 Jul 2021 09:00:06 -0400 Received: from mail.kernel.org ([198.145.29.99]:46450 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238513AbhGUM7z (ORCPT ); Wed, 21 Jul 2021 08:59:55 -0400 Received: by mail.kernel.org (Postfix) with ESMTPS id E1D1160FF4 for ; Wed, 21 Jul 2021 13:40:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1626874829; bh=LLwutF+9OZ49pKtYJ29kQi1FEI3iyzStZxwJm0GkNQ8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=M4ApOyQ6ENY8nuuoqFMP4WEWt+wngPowDNhdCxIOSMWoeZGPEfCE/l4GqdgBZzCEk NQFmHd9QAYad/ljIQbXRTQNlFrQRRR4r2OEsbTk3N66QkX9s6F6BaIUQ0Zsz1GkClx IX4AZD4o3VM7aVXeC5rXwvm/TEi7qPVxgubttW2dDQOgQTj8hIUjDFD+wrlNLxdhK4 3xKIyL8umZpIxx+LwiF84/4gkc7OoMD2Z90A/W5t4m+JmGN8F/8xGwv8z56828KfMY f5E++XqObmn79ME1Ui40YzqcKjYqTMF3SmmIkNVMekagN4dT0S4XA5z0vUT83Gibeh mBQAIEulGXeDA== From: bugzilla-daemon@bugzilla.kernel.org To: platform-driver-x86@vger.kernel.org Subject: [Bug 213579] Clevo NH55HJ (intel tigerlake) touchpad support (GPIO can't be used as IRQ) Date: Wed, 21 Jul 2021 13:40:29 +0000 X-Bugzilla-Reason: None X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: AssignedTo drivers_platform_x86@kernel-bugs.osdl.org X-Bugzilla-Product: Drivers X-Bugzilla-Component: Platform_x86 X-Bugzilla-Version: 2.5 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: patacca@autistici.org X-Bugzilla-Status: NEEDINFO X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: drivers_platform_x86@kernel-bugs.osdl.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugzilla.kernel.org/ Auto-Submitted: auto-generated MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: platform-driver-x86@vger.kernel.org https://bugzilla.kernel.org/show_bug.cgi?id=3D213579 --- Comment #20 from Riccardo Mori (patacca@autistici.org) --- (In reply to Andy Shevchenko from comment #19) > What I'm wondering is if the pin list is broken and actual pin 57 is > something else (+- few pins according to the current driver). May be some= one > can install libgpiod tools (such as `gpiomon`) and run with pins that are > already in GPIO mode without [ACPI] bit set. Something like `gpiomon > gpiochip0 43` (for pin #56) and `gpiomon gpiochip0 47` (for pin #60). Then > if touchpad (when being touched I presume) generates the interrupts this > will show them. But it's unlikely as=20 > per success story described in the bug #211957 where pin under question h= as > much higher number and any pin list disturbance will be noticed immediate= ly. Thank you for helping us Andy. I tried `gpiomon gpiochip0 $PIN` with the non-ACPI pins numbered from 15 up= to 100 but unfortunately I didn't get any output. --=20 You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.=