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=-0.8 required=3.0 tests=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 0348FCA9ED3 for ; Tue, 5 Nov 2019 02:04:26 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id BE7B8214E0 for ; Tue, 5 Nov 2019 02:04:25 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="lh+taqpr" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729796AbfKECEZ (ORCPT ); Mon, 4 Nov 2019 21:04:25 -0500 Received: from mail-oi1-f170.google.com ([209.85.167.170]:44238 "EHLO mail-oi1-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729597AbfKECEZ (ORCPT ); Mon, 4 Nov 2019 21:04:25 -0500 Received: by mail-oi1-f170.google.com with SMTP id s71so16078113oih.11; Mon, 04 Nov 2019 18:04:24 -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=ADhHQyzzzWn62AhgjPBGjZ8RKk/lIEHw/9dcMO6+pCk=; b=lh+taqpro3T1ItQODcyPB3kJNsKkTG9wg7JPqeRouX9H+IDJbvGh3xl/krrLLUGcKD g6tjmweAkkVbxMWeRF6OKnvvhZ3Mps5JQcs4uGMCOgBcQbtSuLWHClnbJLki94kkiPfF sBrJQdETsXyOwtXkffzRQf1bqoUfcfS604LCBI/V6rr/OK9qWj93jeks784jnZmVkFBt 9L51/MVqilrrvg3qaZLJG9MD67gv4CQfEgSqAW2w4Hj5b4zLwEyT7MYyJVTdH4fY35hO 54yklCViHM4UeTEotJ/E/RQFJ91RU+ROAFc40K5D0xtLlxj5MHeOEsSGbLnPoba4S/gW nkCg== 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=ADhHQyzzzWn62AhgjPBGjZ8RKk/lIEHw/9dcMO6+pCk=; b=rCeLLLz/ehkhzirqkiyoPfIxN1ohZg8Vzjdy+VuTDdwPfsU2C3HHQZi8+xA5XTHu81 UoFkyDFqlhW1Eo7+p2N+fNA4jzjd0uzT/VqRayu7MatCmyuyxNlp2LJ9SHKHa/zB9lhP tnHZiBiRxbOQsC+C98nZhpNYu9nyNsRSlDLSUMpNezbgsUe+dXqNdBExC3ZqEC74CTZf MsAB3MU2um/jUVFKc6PYEvdzWL1IpZPEfUes8lUR/i4o7nH2RFUwxs7y9eHHKw29aH2a rhVNE3z6gslzk7zy2uCFUtwGDavu0oqZGPjwxKewfoTkv3oxjSA8xXL5Wh5Qj+QW2x2h DJQA== X-Gm-Message-State: APjAAAU2B5//5DKfqWhbCRb9Xb5hiphVb9T0Sme5EsbhajTTGseI/zHf icIjBSfOWqsKnuYuMGhJ0kEew9N1DI6TSKNkUq3ajA== X-Google-Smtp-Source: APXvYqzQGIxisFpxPq6yZRZ1LuLxkXbVelLMLIpWXHzlIySh5ijOD0lSqbLfxkb7ZpV3CqbjgwCHs7NOUJQ48sEM7hw= X-Received: by 2002:a05:6808:7d0:: with SMTP id f16mr1769719oij.86.1572919463689; Mon, 04 Nov 2019 18:04:23 -0800 (PST) MIME-Version: 1.0 References: <20191104070116.GM57214@dtor-ws> <20191104183702.8894-1-TheSven73@gmail.com> <20191104233621.GP57214@dtor-ws> In-Reply-To: From: Sven Van Asbroeck Date: Mon, 4 Nov 2019 21:04:11 -0500 Message-ID: Subject: Re: [PATCH 2/2] Input: ili210x - add ILI2117 support To: Adam Ford 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 6:40 PM Adam Ford wrote: > > I will test it tomorrow on a 2117a and reply with results. I am very > excited to see this integrated. > I will do the same. That should give us confidence that 211x works ok. Dmitry, should someone retest 251x and 210x after such a significant change? Unfortunately I don't have access to these chips.