Received: by 2002:a05:6a10:6744:0:0:0:0 with SMTP id w4csp423374pxu; Wed, 14 Oct 2020 05:02:47 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwGqxivKBmRENWoRvxmgW4OaZbLmPGgCJJk8auiQtwjz/Vw+q5BXXF/BUKyPrgtIUiMD64J X-Received: by 2002:a17:906:3e4b:: with SMTP id t11mr4758759eji.420.1602676966771; Wed, 14 Oct 2020 05:02:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1602676966; cv=none; d=google.com; s=arc-20160816; b=fIA0dF/NIpowcWpGu8p3/oiFXfFC50RDoEBLE25hiK04lsYaVxzwpD7InaGFV794P9 W/EYl/IU5KaT+xoJR+e2axClgORT2ool2vU30m6Ez0xTE+Z1J8DPFUoimsDFBeNqsNfl wlcy1u/bWZ/Pb8wkWPJOUymCnuGWkzzxye8I96+UDMY5XtyhYe2/slCCVAUxJ4MeFiay BI3DEJJvMdgaZLI3y/IEBmqveZU8YeyxQ2NQ/DZ1BseiJdrOHbBQNT3Yy3mCCuj0bYIe lBMcO7e6yxSndIklt5aK0cHF4NDqcf6iZG2ZDKMfcus57o3M8v0H+4gnaPpAH1zXmJCh m2Wg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:dkim-signature:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=MpUvsa/wMAY7BzkAhwbdXgZgbZYHy0ZGBz0aDP8EC30=; b=GKHuUIA41KTncnRZBke3o2HV4uKHsDH810nYAljSnX1+sqZCFdaIM6yb0dlA4Qw+Ca 6sQvoSJk+/o0aRl3Wx+jNAzESrgFrE7a4pzmViST5Ed3YnIAyZJS2FEBRXdgUe5F0tvc 5+4PFtEhC4+vbnXnqtjf2pR76ZPu6WxitDx35VTmu3yuUE1IHDIlDxTZ5xKQtYKuyhzV fkOX/DV2TBn3EFrjzZDPmtMPwVvZbd6oyP+KEyzMcy/HhgxSpqLJAOrNXLCsDN1mG65S uuejUgex7ibhttAYnZdyLzWTGNeQNsCEcYbeO4/8TsY8weQmy2QxunuxCMvZaa094kW5 m10A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=NbYay9iI; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id n13si1954221edy.429.2020.10.14.05.02.09; Wed, 14 Oct 2020 05:02:46 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=NbYay9iI; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729599AbgJNDVO (ORCPT + 99 others); Tue, 13 Oct 2020 23:21:14 -0400 Received: from hqnvemgate24.nvidia.com ([216.228.121.143]:10838 "EHLO hqnvemgate24.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726049AbgJNDVN (ORCPT ); Tue, 13 Oct 2020 23:21:13 -0400 Received: from hqmail.nvidia.com (Not Verified[216.228.121.13]) by hqnvemgate24.nvidia.com (using TLS: TLSv1.2, AES256-SHA) id ; Tue, 13 Oct 2020 20:19:44 -0700 Received: from [10.19.100.177] (10.124.1.5) by HQMAIL107.nvidia.com (172.20.187.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 14 Oct 2020 03:21:07 +0000 Subject: Re: [PATCH v3 04/15] phy: tegra: xusb: tegra210: Do not reset UPHY PLL To: Thierry Reding CC: , , , , , , , , References: <20200909081041.3190157-1-jckuo@nvidia.com> <20200909081041.3190157-5-jckuo@nvidia.com> <20200928130618.GE3065790@ulmo> X-Nvconfidentiality: public From: JC Kuo Message-ID: <0ec9045c-8722-d7cd-20f0-2c163be75619@nvidia.com> Date: Wed, 14 Oct 2020 11:21:06 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <20200928130618.GE3065790@ulmo> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.124.1.5] X-ClientProxiedBy: HQMAIL111.nvidia.com (172.20.187.18) To HQMAIL107.nvidia.com (172.20.187.13) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1602645584; bh=MpUvsa/wMAY7BzkAhwbdXgZgbZYHy0ZGBz0aDP8EC30=; h=Subject:To:CC:References:X-Nvconfidentiality:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Language: Content-Transfer-Encoding:X-Originating-IP:X-ClientProxiedBy; b=NbYay9iIS0u9b13wMqVg/7m1S5/uQvHx3hDHKgGcf/5ALGojoN25hgrvBf5wfO7Tm UP71jMjVDMeE+zWpx5YyjWdxHaEX8H2re8CDEEWVQeTqNCIIikzOYnO4UVnZTNex2v 1J6Izi/vusu2n1rzG1eiLDeLn4nxLakh72KqFnuOJNq0pXaduNDJAV+P3geg73VtOk QxoiCAIrGre9Wcqgo3WR+HvDlG0Qsr1Cu1YBLXV/P/6JFsbBHJvADGHGzgeBTgAHpZ 6EWk1/jrgDJyGCxyxyX1LwTXU7F/Td7ZuEjqP8WGw8gDDpC8q0CAbiPwJwQn87Wl6c ncdUMJmQJor/Q== Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Asserting reset to a PLL when it's managed by hardware power sequencer would break sequencer's state machine. Putting PLL in reset doesn't save some extra power. Thanks for review. JC On 9/28/20 9:06 PM, Thierry Reding wrote: > On Wed, Sep 09, 2020 at 04:10:30PM +0800, JC Kuo wrote: >> Once UPHY PLL hardware power sequencer is enabled, do not assert >> reset to PEX/SATA PLLs, otherwise UPHY PLL operation will be broken. >> This commit removes reset_control_assert(pcie->rst) and >> reset_control_assert(sata->rst) from PEX/SATA UPHY disable procedure. >> >> Signed-off-by: JC Kuo >> --- >> v3: >> new, was a part of "phy: tegra: xusb: Rearrange UPHY init on Tegra210" >> >> drivers/phy/tegra/xusb-tegra210.c | 2 -- >> 1 file changed, 2 deletions(-) >> >> diff --git a/drivers/phy/tegra/xusb-tegra210.c b/drivers/phy/tegra/xusb-tegra210.c >> index f06e7bc7a51b..ef4bbcbed60b 100644 >> --- a/drivers/phy/tegra/xusb-tegra210.c >> +++ b/drivers/phy/tegra/xusb-tegra210.c >> @@ -504,7 +504,6 @@ static void tegra210_pex_uphy_disable(struct tegra_xusb_padctl *padctl) >> if (--pcie->enable > 0) >> goto unlock; >> >> - reset_control_assert(pcie->rst); >> clk_disable_unprepare(pcie->pll); >> >> unlock: >> @@ -746,7 +745,6 @@ static void tegra210_sata_uphy_disable(struct tegra_xusb_padctl *padctl) >> if (--sata->enable > 0) >> goto unlock; >> >> - reset_control_assert(sata->rst); >> clk_disable_unprepare(sata->pll); >> >> unlock: > > Does this mean that we can no longer reset these PLLs anymore? Is that > safe? Would we ever need to reset them for recovery or similar? For > power saving, is disabling the clock enough, or could we save some extra > power by putting the PLLs into reset? > > Thierry >