Message ID | 20230213165743.1.I6f03f86546e6ce9abb1d24fd9ece663c3a5b950c@changeid |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:adf:eb09:0:0:0:0:0 with SMTP id s9csp2682714wrn; Mon, 13 Feb 2023 17:14:05 -0800 (PST) X-Google-Smtp-Source: AK7set81aSk0M4ogqu0BmJ4WvVwX4NaF56RHH6iYs6nkvTY2OGaBCNLq3gOIqNRegb5Hj3LnxkZu X-Received: by 2002:a17:90b:1c06:b0:232:db7b:5698 with SMTP id oc6-20020a17090b1c0600b00232db7b5698mr567325pjb.15.1676337245582; Mon, 13 Feb 2023 17:14:05 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1676337245; cv=none; d=google.com; s=arc-20160816; b=aFZFm+gPQCFLW+S4TeR+yQ0rWLe9NUl8a91oDNHZryoGGESh/UiOmc96p6VuJKZbUr mBsTfq6ppnCpO9UHMMm3ySr4vJz3X8snqaBaS3J4lmzuTprgq7tYOnucrW6sszixs7zS cDEcRXdZs70hvpebcrOUz86Zd3+vEr4sjik434I3cHeEaqQTdgRUx1MlXC/MlK7U+cUx Xtp5RvC2g/LAEmVJZ2iBzQodJezLHyaJscaHRhOTihY4/J+OZhOblafhHepD7Lu1TBcJ v9pArejHnYz/vKSVL7dWsKT7gqWP32xbd8cVH8tJzcw7OlpQcIK6Lvm11ckIKSooKJri JVDw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=jhxllVnbI2AwFWPN2tKYS/gPDBTeZyTnINmF5vnAF9s=; b=VXetJelda/MaGnFWj7LekTj3AMPuf7ublR9WJExxDXsAWYywKpyI0ZbaVhtubN9Uvv Wt8Blvr8v+Y4Hq89DX3gMrR7zqUXhpl1iwC38m6H+2mtuIv5TiqaereFTDrp23wB+b1w /XXJ8ckURrDZ4TE+IbRIc3ydFssbXmX0wW4n0tptJ3AMlt39hEEFhmGKtBPz7UvP1bTR x5LZI05IR7YH8cD+bzEOC9RWrR2Yu/s/OUtNhNnGAcbvsAjACXxGmH9f9qo0HA2wSrdX vRSCv0WLR3LBj5yUvnZuQM7kJFp1lnMqN0aADKB9uEqviCYubadsckGZvAI++88YxMjk zj4g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=jiksO25M; 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=NONE dis=NONE) header.from=chromium.org Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id i2-20020a636d02000000b004fb878e0fbbsi7142875pgc.639.2023.02.13.17.13.52; Mon, 13 Feb 2023 17:14:05 -0800 (PST) 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=@chromium.org header.s=google header.b=jiksO25M; 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=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230098AbjBNBAf (ORCPT <rfc822;tebrre53rla2o@gmail.com> + 99 others); Mon, 13 Feb 2023 20:00:35 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57948 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229539AbjBNBAd (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Mon, 13 Feb 2023 20:00:33 -0500 Received: from mail-pf1-x430.google.com (mail-pf1-x430.google.com [IPv6:2607:f8b0:4864:20::430]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7E77614226 for <linux-kernel@vger.kernel.org>; Mon, 13 Feb 2023 17:00:32 -0800 (PST) Received: by mail-pf1-x430.google.com with SMTP id n2so9159713pfo.3 for <linux-kernel@vger.kernel.org>; Mon, 13 Feb 2023 17:00:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=jhxllVnbI2AwFWPN2tKYS/gPDBTeZyTnINmF5vnAF9s=; b=jiksO25M1xbJMh+TgDf925qz1OI33yVXPFpT+lYue4N/aK/2EjPChZIbJ4iopZfMH9 qL3CQlp3Q9OGs9elRk+awGd4bmSX4oldimJ+cw6T7pzAirT+A7PkIorWfcbglVMNxmcY x/zEMdVvjkjXDnoH1Sfjv0OboADk5n9MAOyyI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=jhxllVnbI2AwFWPN2tKYS/gPDBTeZyTnINmF5vnAF9s=; b=7P2dlBAXmCkY6zoAHzWcNf/+VSEwOleHab418uxI7nbx2n3hzgBdwHNSLGVgLPzX7U QfOkg11Qmc5hvTYoMvJJNaWCHpe1uq7ft1zf82Q18mK6xDT5CurrOPlTROhsurxXNf6t h7q/rc/ZE4DFY5TI1qlCjG9X6gdPINjYuoTHP68Y/k7pOWP1/0l9dw9X7TC3JBOYWu3N xnVPNJKWIe5xT+/mswlnyNTSEvfLbno+3E0chplSLuNQqO9Yuw/pf5bDSWA3xwMB4Mip nM2G3CPaDtoJq3Y5dwYabEKC3sN6jGq/g3H02q7RDz37Crvei7iMeQ5H+4BCzxwH3YYj S+8g== X-Gm-Message-State: AO0yUKXnvFYkVMppjiX7MzJfn110iyeZsxy7cdE947m96Lqm2fq+d7i5 k4iO7yn4IwL9JA51DnfvMFQUuA== X-Received: by 2002:a62:17d2:0:b0:5a8:49c8:8533 with SMTP id 201-20020a6217d2000000b005a849c88533mr397121pfx.8.1676336432029; Mon, 13 Feb 2023 17:00:32 -0800 (PST) Received: from tictac2.mtv.corp.google.com ([2620:15c:9d:2:af55:a232:a032:95ff]) by smtp.gmail.com with ESMTPSA id e22-20020aa78256000000b00592626fe48csm8482914pfn.122.2023.02.13.17.00.30 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 13 Feb 2023 17:00:31 -0800 (PST) From: Douglas Anderson <dianders@chromium.org> To: Bjorn Andersson <andersson@kernel.org> Cc: amstan@chromium.org, swboyd@chromium.org, mka@chromium.org, Douglas Anderson <dianders@chromium.org>, Andy Gross <agross@kernel.org>, Konrad Dybcio <konrad.dybcio@linaro.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Rob Clark <robdclark@chromium.org>, Rob Herring <robh+dt@kernel.org>, devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH 1/2] arm64: dts: qcom: sc7180: Fix trogdor qspi pull direction Date: Mon, 13 Feb 2023 16:57:51 -0800 Message-Id: <20230213165743.1.I6f03f86546e6ce9abb1d24fd9ece663c3a5b950c@changeid> X-Mailer: git-send-email 2.39.1.581.gbfd45094c4-goog MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS 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: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1757767003241539021?= X-GMAIL-MSGID: =?utf-8?q?1757767003241539021?= |
Series |
[1/2] arm64: dts: qcom: sc7180: Fix trogdor qspi pull direction
|
|
Commit Message
Doug Anderson
Feb. 14, 2023, 12:57 a.m. UTC
Though it shouldn't matter very much, we've decided that it's slightly
better to park the qspi lines for trogdor with an internal pulldown
instead of an internal pullup. There was a footnote that Cr50 (which
connects to these lines too) may have pulldowns configured on one of
the data lines and we don't want to have fighting pulls. This also
means that if the pulls somehow get left powered in S3 (which I'm
uncertain about) that they won't be pulling up lines on an unpowered
SPI part.
Originally the pullup was picked because SPI transfers are active low
and thus the high state is somewhat more "idle", but that really isn't
that important because the chip select won't be asserted when the bus
is idle. The chip select has a nice external pullup on it that's
powered by the same power rail as the SPI flash.
This shouldn't have any functionality impact w/ reading/writing the
SPI since the lines are always push-pull when SPI transfers are
actually taking place.
Fixes: 7ec3e67307f8 ("arm64: dts: qcom: sc7180-trogdor: add initial trogdor and lazor dt")
Signed-off-by: Douglas Anderson <dianders@chromium.org>
---
arch/arm64/boot/dts/qcom/sc7180-trogdor.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Comments
Quoting Douglas Anderson (2023-02-13 16:57:51) > Though it shouldn't matter very much, we've decided that it's slightly > better to park the qspi lines for trogdor with an internal pulldown > instead of an internal pullup. There was a footnote that Cr50 (which > connects to these lines too) may have pulldowns configured on one of > the data lines and we don't want to have fighting pulls. Ok. > This also > means that if the pulls somehow get left powered in S3 (which I'm > uncertain about) that they won't be pulling up lines on an unpowered > SPI part. As far as I know, the pulls are maintained in S3. There's verbage about "keeper" on the pins. The SPI part is powered in S3 though. I believe it only loses power in S5. Can you reword this statement? The fighting pulls should be resolved though. Or maybe it is better to simply not put any pull on the line? Presumably the pull is there to avoid seeing 0->1 transitions on the data lines when inactive, but I'm not really convinced that is going to happen because the SPI chip itself would have to be doing that driving, and the chip select isn't changing. > > Originally the pullup was picked because SPI transfers are active low > and thus the high state is somewhat more "idle", but that really isn't > that important because the chip select won't be asserted when the bus > is idle. The chip select has a nice external pullup on it that's > powered by the same power rail as the SPI flash. > > This shouldn't have any functionality impact w/ reading/writing the > SPI since the lines are always push-pull when SPI transfers are > actually taking place. > Right.
Quoting Stephen Boyd (2023-02-15 21:46:52) > Quoting Douglas Anderson (2023-02-13 16:57:51) > > Though it shouldn't matter very much, we've decided that it's slightly > > better to park the qspi lines for trogdor with an internal pulldown > > instead of an internal pullup. There was a footnote that Cr50 (which > > connects to these lines too) may have pulldowns configured on one of > > the data lines and we don't want to have fighting pulls. > > Ok. > > > This also > > means that if the pulls somehow get left powered in S3 (which I'm > > uncertain about) that they won't be pulling up lines on an unpowered > > SPI part. > > As far as I know, the pulls are maintained in S3. There's verbage about > "keeper" on the pins. > > The SPI part is powered in S3 though. I believe it only loses power in > S5. Can you reword this statement? I see that we list pp1800_l13a in sc7180-trogdor.dtsi but don't mark it always on. I suspect it is turned off at late init, but then wifi turns it on itself because it is the IO voltage for the wcn chip. We're at the mercy of the wifi firmware here? Shouldn't we just mark it always on and boot on? I wonder how this is working.
diff --git a/arch/arm64/boot/dts/qcom/sc7180-trogdor.dtsi b/arch/arm64/boot/dts/qcom/sc7180-trogdor.dtsi index 423630c4d02c..de40abcd18db 100644 --- a/arch/arm64/boot/dts/qcom/sc7180-trogdor.dtsi +++ b/arch/arm64/boot/dts/qcom/sc7180-trogdor.dtsi @@ -1054,7 +1054,7 @@ &qspi_clk { &qspi_data01 { /* High-Z when no transfers; nice to park the lines */ - bias-pull-up; + bias-pull-down; }; &qup_i2c2_default {