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.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS autolearn=ham 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 8750ACA9EB5 for ; Mon, 4 Nov 2019 14:19:41 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 4C9F021655 for ; Mon, 4 Nov 2019 14:19:41 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="tp4VYwNT" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728097AbfKDOTk (ORCPT ); Mon, 4 Nov 2019 09:19:40 -0500 Received: from mail-il1-f196.google.com ([209.85.166.196]:35241 "EHLO mail-il1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727861AbfKDOTk (ORCPT ); Mon, 4 Nov 2019 09:19:40 -0500 Received: by mail-il1-f196.google.com with SMTP id z12so2959363ilp.2; Mon, 04 Nov 2019 06:19:40 -0800 (PST) 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=lF1WE1isaBjDr+TMSOi18bgjGXsXpz2MAkSlnPFM5BM=; b=tp4VYwNTyrIbMsMDKBZMr0U1v1tpkzNfA6hg8iB3X4E+qmlzTt7ygvAGhuuifV84lr nfMseSsvQQAnAr5vgX6pUnRZz0PBQEoNcNZfYZlQDdznGJKUwoBlmcDNev/OzWnjfgoe Fm/zQ7VEucGrqD0wO//NWdSc+Zg6Ff+J6XfLqXnEmQD0NcJAw2rqhJ+RCNtWniSIXdhV OI8iJcY2x3UFci7Lgd+zT3TBTZS6OaGlaDQgAR1g7CznZksADbGM+OdrbpOsjiDZaJGd tXNzxQn+qVLxDQQA5k47VOji8Ih8fkPKg07AdHNITnrvjhrjJYUqgrR+sv3HLRJVX6NR zXEw== 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=lF1WE1isaBjDr+TMSOi18bgjGXsXpz2MAkSlnPFM5BM=; b=JJ1PnlkacMFV5dtv6MrKxRNDEcggpQWc6obg0OtZCL/cZkpof78wlAwGyKOQuY69ZN z85LdcHIC+rmYJpoi0wN7BVxU/fIQdtVHtr2acWcPaM8s5ISz7i8f6Cqn1fxXgenWyWi q26jFqz0tz+rbGtG7NPcsC1JS64tGqHKTNkbdoLYPOmoMYnz0Chn30vHlnpnP3vl3PpL /iUYvWqcg/zx3MdJ4/KQAH066M6ZZQ7QOQ5SGbQPPrl6lBHhtPqzgu/a7FCPZhVUDDVc U9J7vxHDzOfwhnV2r/EQbAWWrH8D7TphEN5wPGXmXCQdhK2tSgnaGcNde76kPYeV+z6a EOSA== X-Gm-Message-State: APjAAAUSrDmJ/VhKhwjhlkSEyL8u4Z/cHjxpJXKhO2okN+QKYmhylvWP DoT56FXXMnT8ZHTNaKtnaVw4oImmNE2ZQqgvEVU= X-Google-Smtp-Source: APXvYqyrBchjwhSoha+V5PjVcj9qJMDkIexcW0zjXh+uZ5qirAamQ4EPo2ARC6NJ77ISTRwnIbbz398vQcaAwYQMY/s= X-Received: by 2002:a05:6e02:c2c:: with SMTP id q12mr29091298ilg.205.1572877179288; Mon, 04 Nov 2019 06:19:39 -0800 (PST) MIME-Version: 1.0 References: <20190302141704.32547-1-marex@denx.de> <20191101204801.16328-1-TheSven73@gmail.com> <20191104070116.GM57214@dtor-ws> In-Reply-To: From: Adam Ford Date: Mon, 4 Nov 2019 08:19:28 -0600 Message-ID: Subject: Re: [PATCH 2/2] Input: ili210x - add ILI2117 support To: Sven Van Asbroeck Cc: Dmitry Torokhov , Marek Vasut , linux-input@vger.kernel.org, Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Sender: linux-input-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-input@vger.kernel.org On Mon, Nov 4, 2019 at 7:49 AM Sven Van Asbroeck wrote: > > On Mon, Nov 4, 2019 at 2:01 AM Dmitry Torokhov > wrote: > > > > Can you please tell me what device you have? Do the patches work for > > you? > > I have an ILI2117A/ILI2118A. > > I'll try out the patches today. I'm stuck with a 4.1 vendor kernel, so > I'll need to backport the (patched) mainline driver to 4.1 before > I'm able to test. > > I wil try Marek's patch, and Dmitry's rebased patch from > https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git/log/?h=ili2xxx-touchscreen > and let you know the results. For what it's worth, I tried the 3-patch series from that branch on 5.4-RC5, but the ts_calibrate and ts_test_mt do not appear to receive touch info. They execute when I 'export TSLIB_TSDEVICE=/dev/input/event0' but I don't get touch data. If I do a hex-dump of /dev/event0 and it dumps data if and only if I hold my finger on the touch screen for a while. I'll try just doing the 1st patch to see if it it's any better. adam > > If the problem with Dmitry's patch is located in ili251x_read_touch_data, > then using a ILI2117A should work fine.