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=-2.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,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 8552DC636C9 for ; Wed, 21 Jul 2021 17:48:57 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 5FE466100C for ; Wed, 21 Jul 2021 17:48:57 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237668AbhGURIR (ORCPT ); Wed, 21 Jul 2021 13:08:17 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46032 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237542AbhGURIO (ORCPT ); Wed, 21 Jul 2021 13:08:14 -0400 Received: from mail-vk1-xa31.google.com (mail-vk1-xa31.google.com [IPv6:2607:f8b0:4864:20::a31]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 84620C061575 for ; Wed, 21 Jul 2021 10:48:50 -0700 (PDT) Received: by mail-vk1-xa31.google.com with SMTP id bc26so689515vkb.13 for ; Wed, 21 Jul 2021 10:48:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=8ETYWsBqUp3S3auaGLRtgQ7yu3TO0BudUXwxuYoMHvU=; b=pbEg9CR3HkC6HU1nQfVIfxIQ/fpsVbZ8/mkCuoBF78SMjYClGKt0UrECoXjdjjXUrp fyRunqy1WIh2bMAluG2N9LCAweqOFlvFXCIbCQY1b8hL3+mHLj6a6ozk/0YcHdiH5OpD XfcjwlX+MOowWhJtWFIcs2YD/oH3Waf1T2J3MHpq07IDsUFV03DojeBtjJxbM0QrN7no uM+KorMbv2EBb074NkuaVMYUHUyw//wXICEU7tLzpIpp75mUdb0vO8xxrgeoMmtRT2mo Gkp4HGN08PoHIH9eNvxTJzij5+K+yUSkyds6nv92w5gFDtAl0OXe77WulUymzsYy1buu 8TNQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=8ETYWsBqUp3S3auaGLRtgQ7yu3TO0BudUXwxuYoMHvU=; b=KNhm4xs/7pFhdUSKNAxgmy9yesocK8f6fUvKPV7yth6E9bUPks/IZZph0Pokyc9AIX euoAFoza/bjiISwz+AaAsiDzy+ayaRkYUjHltC/40CoQF+5tbD99t3xlVzlywyF+13dp z5bsPrRWKUYBMMlZ4H78YG6L0OXuAMr2tY1wCnvLvZ5pqE9/28IYIuNNN50q4fXvSeyN rD+lUVYmbYHNjaak2Pnm4Kvg9OZ3Lst8oXEp/6wntB0mnXP/bcOM00VqrvacJsl5BO3g vcVM4JaKaIdik7JleOqSkW8lq5ASHKar6VE/c8G8NTKS6EZbDroKQAZv6LCq1ZwYF+SI UElQ== X-Gm-Message-State: AOAM530cBeMr5tTuR3jpdaybyaBEVF2c5kv1ADOPtTcr6rDXI2VwgjD2 VjGN4DAZy20FhcRo2AnwumuQpA4Kn+V+gGp4iFI= X-Google-Smtp-Source: ABdhPJzI+l51DqKPXYY585S/r0UhMioC3D4ybCu+9GiOd4dVaNb1bHoOkWVuPa3ZJJFbOjbEl3aic07UKGrqk+rO7jI= X-Received: by 2002:a1f:3a4a:: with SMTP id h71mr32709178vka.20.1626889729627; Wed, 21 Jul 2021 10:48:49 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Dmitry Torokhov Date: Wed, 21 Jul 2021 10:48:37 -0700 Message-ID: Subject: Re: Elantech touchpad not working on mainline kernels To: Hans Schultz Cc: "linux-input@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-input@vger.kernel.org Hi Hans, On Sun, May 30, 2021 at 2:12 AM Hans Schultz wrote: > > Hello, > I have a problem getting my Elantech touchpad to work with the mainline > kernels, and I need some assistance with the code to resolve the > problem. > The kernels that have tried are 5.9.11 and 5.11.11. > > With boot parameters i8042.notimeout i8042.nomux, the touchpad is > detected but does not work. There is absolutely no response from it > with any hid modules loaded. > > It is reported and seen working on a Lubuntu distro (bionic kernel) > when inserting the i2c_hid module. The insertion of the i2c_hid module > pulls in the hid_multitouch module when it works, no boot parameters > necessary. > In the case where it does not work, insering the i2c_hid module does > not pull in the hid_multitouch module. > > I have the bionic kernel code, but I have not as of yet been able to > detect what makes it work in contrast to the kernel.org kernels. > > This I think should lead to a kernel patch. There is not much to go on with. What is the hardware, your kernel .config, dmesg from unsuccessful boot? If you have logs from the working kernel that would help too. Thanks. -- Dmitry