Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp7529649rwd; Tue, 6 Jun 2023 12:05:58 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ6nDlJuvh0e3Cbb+nVJV2a192J7QhJ02NqbTea9UhzhpjTcoRO7ZB3DNxJnblGtrZcEGvEn X-Received: by 2002:a05:620a:8f02:b0:75b:23a1:407 with SMTP id rh2-20020a05620a8f0200b0075b23a10407mr622985qkn.29.1686078356701; Tue, 06 Jun 2023 12:05:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1686078356; cv=none; d=google.com; s=arc-20160816; b=lq8u88qz9EMw5XMYXeN8T8KyV0tqhkgE+H+R7TbE6/d01/QrhKhHR+Jcq4d4beS5yL OXKKs6sDgglk11yXFLW+6k+8/Q1TeX/2vpU0lgvtglTceiGx8NW0EQ7NAjQCfJ4OtpCE W23gQ8t+rvQr9L+UL6UZ+VhWYZIpXVIq7D58cQjCksSOs3ml1l/SlsTP85aKgqqbP0f3 aejqUTQ2ZghhMd+myYiXX+A3PW4+IiGBOpdMoyQUVHBS/Z8G+N54ci2SLQpVMjmxDFBF HjcO9uDb1Q33C/k4BtFLl38df7zeK2bffxTodBvpAZGRdTOr7TNgqyKCnDb0bbcyZvxR +Kuw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=FnxSGX9RGEOsuf5fjVZlUilqBnK9L4Q5QcWfPvvT188=; b=VWVgAubsoY9F37eoeHga0oAX3KjAjkwa7bH8zMCyEGD+4LHT0JdWcg+Tco8LhcK2iM qSDFfEjVDqd9WaDa6C8Wjxhj5TH+dy+8feY8RiXN1KhygroyxQmbOelc7maXnjW7882I g2zPVO0yA1n7vSmquawLHuk3qFShqJVmKDn+fU7IlzY9nrOm8B+NcXntbv24Z97crjVj NDOh/oTsprsvoIymGGpWbNWQiMav2pgxz4SuQd9ZlDoAgho4mdX3OuElHx94/aSLTGHz dF4Kx7hLl6mmHLUTfZkdwhwfkYrJgA/id9H4N12xlqR4/JI63LanMRWzoqoiDNEhhs85 DGHA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20221208 header.b=Hv2MAbOs; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id x4-20020a05620a12a400b0075ca303a9c4si6535200qki.651.2023.06.06.12.05.41; Tue, 06 Jun 2023 12:05:56 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20221208 header.b=Hv2MAbOs; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239062AbjFFSo5 (ORCPT + 99 others); Tue, 6 Jun 2023 14:44:57 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54754 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239067AbjFFSou (ORCPT ); Tue, 6 Jun 2023 14:44:50 -0400 Received: from mail-pf1-x42c.google.com (mail-pf1-x42c.google.com [IPv6:2607:f8b0:4864:20::42c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 90B7310F2; Tue, 6 Jun 2023 11:44:49 -0700 (PDT) Received: by mail-pf1-x42c.google.com with SMTP id d2e1a72fcca58-654f8b56807so3832863b3a.1; Tue, 06 Jun 2023 11:44:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1686077089; x=1688669089; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=FnxSGX9RGEOsuf5fjVZlUilqBnK9L4Q5QcWfPvvT188=; b=Hv2MAbOsi/py9dCB1OT98jVelXiGsC0q4zvrD9Qpel0UuNQ9B90H/Zllw9TUP0Kg5A liJANCu79rkr4JjLRDujReUbR5PbF1v6dxqR0TV47gRMkpTeQ12IxC0AQsXL9PXNsjFD qYJHl4SAY2crpAcWmA+tqIKgYdnX5c/okpK6JjOGGewfIsDr32My/5Bk+rHrTz/8vBy9 vKKyNq8i/Ojm7LRsaN82KAplE8LIm4cjL8debuesp/e36zupmmbWo8H8DkELbsKq/8uH M9gsF6jmya5hL5X/1wursH8O08HqOgpT3/ygARu8OlyfBJF67jllwRmWtPFj0lvoYrYo Ug7g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686077089; x=1688669089; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=FnxSGX9RGEOsuf5fjVZlUilqBnK9L4Q5QcWfPvvT188=; b=Jsb+50e3xpKOpBzqfvtrIXlSSI4aNLqJ09pyPu6apukjUoiddHl63jeehh6iAYp+5R XiU5epeEOmkqgk9lqoCj6uaireHUh31jrWJyT+TsJCbzmmHZ4UPU3PUpIqiQg/z/Aewn 38eH8ldLyxijdOdZc/1kAtt10G9+sAwZgpgFpJImsMKB7v03ehiLLgQPefpRgzac6ZiS xIld9Yd/pckvtkQq44zUyRUR/dyje5sz+m0EzppzaBRvB1kjGxqDqV5f8ljP1v2zqA1E 5e1nEdyAvbRYDYEcb+es2jcnhp3Bkxi7VLalWlMpEfNCJKPpDhjsR/a79fHZnwgQNjLD SlmA== X-Gm-Message-State: AC+VfDxlGT9/RwvYBaenqE5k8Z6OODRuwBrf4PzuG0QXyIwu9fRC421M bqCa/yPQxaNNk8IofLQ27lf7H6Qa1jM= X-Received: by 2002:a05:6a00:c8c:b0:64f:52c9:ddd5 with SMTP id a12-20020a056a000c8c00b0064f52c9ddd5mr3888893pfv.34.1686077088947; Tue, 06 Jun 2023 11:44:48 -0700 (PDT) Received: from google.com ([2620:15c:9d:2:f59e:5ad5:28cc:2003]) by smtp.gmail.com with ESMTPSA id j17-20020aa79291000000b006410f4f3ecdsm7118044pfa.83.2023.06.06.11.44.47 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 06 Jun 2023 11:44:48 -0700 (PDT) Date: Tue, 6 Jun 2023 11:44:45 -0700 From: Dmitry Torokhov To: Neil Armstrong Cc: Hans de Goede , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Bastien Nocera , Henrik Rydberg , linux-input@vger.kernel.org, linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH RFC 0/4] input: touchscreen: add initial support for Goodix Berlin touchscreen IC Message-ID: References: <20230606-topic-goodix-berlin-upstream-initial-v1-0-4a0741b8aefd@linaro.org> <2677ae8c-59d3-b658-dc3f-918838ac0fb6@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2677ae8c-59d3-b658-dc3f-918838ac0fb6@linaro.org> X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,FSL_HELO_FAKE, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 06, 2023 at 08:12:04PM +0200, Neil Armstrong wrote: > Hi, > > On 06/06/2023 17:31, Hans de Goede wrote: > > Hi Neil, > > > > On 6/6/23 16:31, Neil Armstrong wrote: > > > These touchscreen ICs support SPI, I2C and I3C interface, up to > > > 10 finger touch, stylus and gestures events. > > > > > > This initial driver is derived from the Goodix goodix_ts_berlin > > > available at [1] and [2] and only supports the GT9916 IC > > > present on the Qualcomm SM8550 MTP & QRD touch panel. > > > > > > The current implementation only supports BerlinD, aka GT9916. > > > > > > Support for advanced features like: > > > - Firmware & config update > > > - Stylus events > > > - Gestures events > > > - Previous revisions support (BerlinA or BerlinB) > > > is not included in current version. > > > > > > The current support will work with currently flashed firmware > > > and config, and bail out if firmware or config aren't flashed yet. > > > > What I'm missing here / in the commit msg of > > "input: touchscreen: add core support for Goodix Berlin Touchscreen IC" > > > > is an explanation why this is a new driver instead of adding > > support to the existing goodix.c code. > > > > I assume you have good reasons for this, but it would be good > > if you can write the reasons for this down. > > Sure, should I write it down here and/or update the commit message in a new revision ? > > Anyway, here's the reasons: > - globally the event handling "looks like" the current goodix.c, but again the offsets > are again different and none of the register address are the same, and unlike the current > support all registers are provided by the "ic_info" structure > - while with the current code it *could* be possible to merge it, with a lot of changes, > the firmware management looks really different, and it would be really hard to merge. > > But I may be wrong, and may be misleaded by the goodix driver structure (even if it > went through a really heavy cleaning process). > > Globally it seems they tried to match the "event handling" process of the previous > generations, but the firmware interface is completely different. It is not unprecedented for drivers to share event processing and implement several ways/generations of firmware update mechanisms. Thanks. -- Dmitry