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=-8.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_PASS,T_DKIMWL_WL_HIGH,URIBL_BLOCKED,USER_AGENT_GIT autolearn=unavailable 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 1D138C004C9 for ; Tue, 7 May 2019 23:50:53 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id E1FBD205ED for ; Tue, 7 May 2019 23:50:52 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="NaFA+Ahy"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="cOk+SU1i" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org E1FBD205ED Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=chromium.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:Message-Id:Date:Subject:To :From:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References: List-Owner; bh=BmuHCjeFhpzgsh+y5OvYRZO1zAAAAadcEPHEjOZJ/kM=; b=NaFA+AhyEd8qeE f8bdCyOeKqQSDPNm2JOZj69IxwLsacZxmC7GNbBWPsPzltxNWSfZVyxj6SftyId//n3NAw18zRiMD wCPto59cocAPf9z/8ckMqdAeLFsv+BMfEk20R6UD0rO6q+sQiqk92+BeX14G2GtoQl+jjvg1TmSH+ 5f6e6tfAYWfD29YMBO+qsyHqG9yGHLIZKwG3RaYlZjHV0G0lhFC7WPAYNPvbFmJFIlWnANUiCuAhm zELcsKCqYVAqjNRDS5yIa0z8sJ0/zw3Fj0TMZtNaKJkJOhiVU8vX6a7nVckH/ZbQW4iQyCyj7THA6 3q5wyfZsBd4wThkRmzPw==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1hO9rE-0002nS-Ih; Tue, 07 May 2019 23:50:48 +0000 Received: from mail-pg1-x541.google.com ([2607:f8b0:4864:20::541]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1hO9rB-0002mo-2T for linux-arm-kernel@lists.infradead.org; Tue, 07 May 2019 23:50:46 +0000 Received: by mail-pg1-x541.google.com with SMTP id h1so9110188pgs.2 for ; Tue, 07 May 2019 16:50:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=C2o4ETy+vWyO645V7kF5tMNDqsri4a3cWb41vpQuvow=; b=cOk+SU1iuvIll4eRwwIrl5D3fmLsvWuhtE1OcoCzB240FCv3dCCE2VDX8UL/cD5vIS x1XUhb0ErANI7cOso8PoCamjW1SavXsouvxL+B20d1sExG7iHT8GufU1y+biN/X1HoEg becIXZZzA9wVvAnEdU6TZhncZ3bW0qSkIbDs0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=C2o4ETy+vWyO645V7kF5tMNDqsri4a3cWb41vpQuvow=; b=cGYRh0vtypzMUt2JwmW2yduf/DR+u20a6klZ8g2V5tiZy7kCYkRAH4z88P0tbLQMRE h1ALm0rjm7K4vge/fjtStr71kLAQFa6s/COgupw1j9/sgXjA1BTHNe1OPqtljpeVNr3T GiU1FhelVJEOOndbu/p9GQeYJzZOKmMH6wzbxubEI72AwEMRQ6BtbE0D2x/xqgA+poK9 yh7JK4OcIw9gCV1clkIjPxWIwgflEBTpWwEqr/lbu0HK6syIG15Pt7MH5qrRVPpEAoTD GyvnaJK5cg3c7AwApKPEmTvHRSWy3UrS+uIpvRyrDq2jkZepyrm5T+BV+DSf3chx0dBS b/Xg== X-Gm-Message-State: APjAAAWoUmjBKW3aFF2zfhe+Ct1KZkvh1sSMZTsEN9PDr1p5xwEpnLt8 85jVtxldxmQunWjzYdfjwvOERw== X-Google-Smtp-Source: APXvYqyPRHj71I0RtZt1k/NbQYF+jTnztfdDZMDt/S2D2rOv+RAfu+tJI8s6apjo+dh+q0OSW58e1A== X-Received: by 2002:a63:6b49:: with SMTP id g70mr43558513pgc.340.1557273044079; Tue, 07 May 2019 16:50:44 -0700 (PDT) Received: from tictac2.mtv.corp.google.com ([2620:15c:202:1:24fa:e766:52c9:e3b2]) by smtp.gmail.com with ESMTPSA id n18sm30268927pfi.48.2019.05.07.16.50.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 May 2019 16:50:43 -0700 (PDT) From: Douglas Anderson To: Kishon Vijay Abraham I , Heiko Stuebner Subject: [PATCH] phy: rockchip-dp: Avoid power leak by leaving the PHY power on Date: Tue, 7 May 2019 16:48:56 -0700 Message-Id: <20190507234857.81414-1-dianders@chromium.org> X-Mailer: git-send-email 2.21.0.1020.gf2820cf01a-goog MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190507_165045_141779_4CA193A6 X-CRM114-Status: GOOD ( 18.11 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Elaine Zhang , hl@rock-chips.com, dbasehore@chromium.org, Douglas Anderson , linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org, mka@chromium.org, ryandcase@chromium.org, groeck@chromium.org, linux-arm-kernel@lists.infradead.org, wxt@rock-chips.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org While testing a newer kernel on rk3288-based Chromebooks I found that the power draw in suspend was higher on newer kernels compared to the downstream Chrome OS 3.14 kernel. Specifically the power of an rk3288-veyron-jerry board that I tested (as measured by the smart battery) was ~16 mA on Chrome OS 3.14 and ~21 mA on a newer kernel. I tracked the regression down to the fact that the "DP PHY" driver didn't exist in our downstream 3.14. We relied on the eDP driver to turn on the clock and relied on the fact that the power for the PHY was default turned on. Specifically the thing that caused the power regression was turning the eDP PHY _off_. Presumably there is some sort of power leak in the system and when we turn the PHY off something is leaching power from something else and causing excessive power draw. Doing a search through device trees shows that this PHY is only ever used on rk3288. Presumably this power leak is present on all rk3288-SoCs running upstream Linux so let's just whack the driver to make sure we never turn off power. We'll still leave the parts that turn _on_ the power and grab the clock, though. NOTES: A) If someone can identify what this power leak is and fix it in some other way we can revert this patch. B) If someone can show that their particular board doesn't have this power leak (maybe they have rails hooked up differently?) we can perhaps add a device tree property indicating that for some boards it's OK to turn this rail off. I don't want to add this property until I know of a board that needs it. Fixes: fd968973de95 ("phy: Add driver for rockchip Display Port PHY") Signed-off-by: Douglas Anderson --- As far as I know Yakir (the original author) is no longer at Rockchip. I've added a few other Rockchip people and hopefully one of them can help direct even if they're not directly responsible. drivers/phy/rockchip/phy-rockchip-dp.c | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/drivers/phy/rockchip/phy-rockchip-dp.c b/drivers/phy/rockchip/phy-rockchip-dp.c index 8b267a746576..10bbcd69d6f5 100644 --- a/drivers/phy/rockchip/phy-rockchip-dp.c +++ b/drivers/phy/rockchip/phy-rockchip-dp.c @@ -35,7 +35,7 @@ struct rockchip_dp_phy { static int rockchip_set_phy_state(struct phy *phy, bool enable) { struct rockchip_dp_phy *dp = phy_get_drvdata(phy); - int ret; + int ret = 0; if (enable) { ret = regmap_write(dp->grf, GRF_SOC_CON12, @@ -50,9 +50,12 @@ static int rockchip_set_phy_state(struct phy *phy, bool enable) } else { clk_disable_unprepare(dp->phy_24m); - ret = regmap_write(dp->grf, GRF_SOC_CON12, - GRF_EDP_PHY_SIDDQ_HIWORD_MASK | - GRF_EDP_PHY_SIDDQ_OFF); + /* + * Intentionally don't turn SIDDQ off when disabling + * the PHY. There is a power leak on rk3288 and + * suspend power _increases_ by 5 mA if you turn this + * off. + */ } return ret; -- 2.21.0.1020.gf2820cf01a-goog _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel