Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 090B0C636CC for ; Tue, 7 Feb 2023 18:19:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232147AbjBGSTi (ORCPT ); Tue, 7 Feb 2023 13:19:38 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41088 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232251AbjBGSTR (ORCPT ); Tue, 7 Feb 2023 13:19:17 -0500 Received: from mail-il1-x136.google.com (mail-il1-x136.google.com [IPv6:2607:f8b0:4864:20::136]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8C75B40BFB for ; Tue, 7 Feb 2023 10:18:13 -0800 (PST) Received: by mail-il1-x136.google.com with SMTP id l7so6401702ilf.0 for ; Tue, 07 Feb 2023 10:18:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; 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=fQMCLtY/o/lcP2wVxbKEZHVTujPOs6CF4TCboKmWfnM=; b=DYiZQ/QlyBeTa/mCDWni3T7T/0TILBtLstqv2EawL1Ewt5HTPQKQIbVG8t0RJoY5sZ 7CWDsy4IjKqxxiPS4ke4s9Tgez07u870yZBp4cCdYjwhvqUr6HrM7ZYCgQqyGa1ZFnVF xsUWTLvKoPpTXYX29+5exDtYHvXgWQzD2Dw9E= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=fQMCLtY/o/lcP2wVxbKEZHVTujPOs6CF4TCboKmWfnM=; b=Jzj/12d6auyCN2fck66dXMc6Ly3W/iHAPHnMQVugWOHzPMaO+MTRF6wxEC3Z71e2HR RYrdxVv0H6T4NffK7aXCAK1ESkx/g3zOffREQct8EKAMDyTsbygfBT6xUukghtwSuw0f 6ZaH8JVsHTm5R5j4x10kU1utI8aXpQegLMFMdxMIPPIgxk7WVUpuOyJNt/5mhYrW3E7D ztmucBBdWBwWa8BoblJ8A2pzpH1vhP1JJHkCuF7MZQffzKbt4sugwQgE7NwmuaaH4kk1 0K0P6xR/BA4uJUyQqLOUyd9z4DUZRyHuavyhhq/QelHwgu7JhXXY2of395POqH1BQSr2 GGVQ== X-Gm-Message-State: AO0yUKWcQ/Xd37odxr0H6reXLifQn2jZw04iE91kIIL+YgqLZil9O/CQ tFBJkRijc8ybCZaBBvwkIyBPsg== X-Google-Smtp-Source: AK7set987uZbgR5yZkVJT+jrgFpaiDdCBjJhqCqZZGfbB4Gk0XbPD2P05L05pZgj2GUSaLAHeDcYig== X-Received: by 2002:a05:6e02:178b:b0:310:a06a:d0b0 with SMTP id y11-20020a056e02178b00b00310a06ad0b0mr5382939ilu.10.1675793889892; Tue, 07 Feb 2023 10:18:09 -0800 (PST) Received: from localhost (30.23.70.34.bc.googleusercontent.com. [34.70.23.30]) by smtp.gmail.com with UTF8SMTPSA id e1-20020a056e020b2100b0030c27c9eea4sm4352263ilu.33.2023.02.07.10.18.09 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 07 Feb 2023 10:18:09 -0800 (PST) Date: Tue, 7 Feb 2023 18:18:08 +0000 From: Matthias Kaehlcke To: Douglas Anderson Cc: Bjorn Andersson , Rob Herring , Krzysztof Kozlowski , Jiri Kosina , Benjamin Tissoires , linux-input@vger.kernel.org, linux-arm-msm@vger.kernel.org, Dmitry Torokhov , devicetree@vger.kernel.org, Stephen Kitt , Konrad Dybcio , Andy Gross , linux-kernel@vger.kernel.org Subject: Re: [PATCH 3/7] arm64: dts: qcom: sc7280: Hook up the touchscreen IO rail on villager Message-ID: References: <20230207024816.525938-1-dianders@chromium.org> <20230206184744.3.I740d409bc5bb69bf4a7b3c4568ea6e7a92f16ccd@changeid> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20230206184744.3.I740d409bc5bb69bf4a7b3c4568ea6e7a92f16ccd@changeid> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 06, 2023 at 06:48:12PM -0800, Douglas Anderson wrote: > On never revs of sc7280-herobrine-villager (rev2+) the L3C rail is nit: s/never/newer/ no need to re-spin just for this. > provided to the touchscreen as the IO voltage rail. Let's add it in > the device tree. > > NOTE: Even though this is only really needed on rev2+ villagers (-rev0 > had non-functioning touchscreen and -rev1 had some hacky hardware > magic), it doesn't actually hurt to do this for old villager revs. As > talked about in the patch ("arm64: dts: qcom: sc7280: On QCard, > regulator L3C should be 1.8V") the L3C regulator didn't go anywhere at > all on older revs. That means that turning it on for older revs > doesn't hurt other than drawing a tiny bit of extra power. Since -rev0 > and -rev1 villagers will never make it to real customers and it's nice > not to have too many old device trees, the better tradeoff seems to be > to enable it everywhere. > > Signed-off-by: Douglas Anderson Reviewed-by: Matthias Kaehlcke