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=-10.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,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 93064C2D0C1 for ; Thu, 19 Dec 2019 15:05:01 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 5D16821655 for ; Thu, 19 Dec 2019 15:05:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1576767901; bh=nGIBL8aVxoKmkDIwSClLd5dlI6t4JIUetskk9vvcXmE=; h=From:To:Cc:Subject:Date:In-Reply-To:References:List-ID:From; b=GXzvNvZYQBIaObwhsIJWe9LzOLK+pDzz6ZqOCA23KrO7EB87mpH3tWFHFfha9Cvxa Dt/+0HrolRbxK8xAdvTvSE+QP9rK0PGQoA6SOJFl6Yp+bCb48/BAXQe8Ecr7dd5fWz R4w/J6rTwKVaC70ilY+RFMs6xX9zCjnA1FhqTJzk= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726895AbfLSPFA (ORCPT ); Thu, 19 Dec 2019 10:05:00 -0500 Received: from mail.kernel.org ([198.145.29.99]:34160 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726817AbfLSPE7 (ORCPT ); Thu, 19 Dec 2019 10:04:59 -0500 Received: from localhost.localdomain (unknown [122.178.234.230]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 1970724672; Thu, 19 Dec 2019 15:04:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1576767898; bh=nGIBL8aVxoKmkDIwSClLd5dlI6t4JIUetskk9vvcXmE=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=wEoffsMqqtDei+TxWhS4ErXebPe5/QAcEeRDjnuJ9hWoJuDCFZWni5wTkSw5v+0Q+ CzGqS0kYdZAd0Y9O503gtkAOKiGeCgwUjyD0KNFf3/GMMxtdcqF28IFUfVQ0PY2zeQ JOG8wfnizA3Yp3TbCOaBK+2Teopb8kCOPg/J93GI= From: Vinod Koul To: Kishon Vijay Abraham I Cc: linux-arm-msm@vger.kernel.org, Bjorn Andersson , Vinod Koul , Andy Gross , Can Guo , Jeffrey Hugo , linux-kernel@vger.kernel.org Subject: [PATCH 1/4] phy: qcom-qmp: Increase the phy init timeout Date: Thu, 19 Dec 2019 20:34:30 +0530 Message-Id: <20191219150433.2785427-2-vkoul@kernel.org> X-Mailer: git-send-email 2.23.0 In-Reply-To: <20191219150433.2785427-1-vkoul@kernel.org> References: <20191219150433.2785427-1-vkoul@kernel.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org If we do full reset of the phy, it seems to take a couple of ms to come up on my system so increase the timeout to 10ms. This was found by full reset addition by commit 870b1279c7a0 ("scsi: ufs-qcom: Add reset control support for host controller") and fixes the regression to platforms by this commit. Suggested-by: Can Guo Signed-off-by: Vinod Koul --- drivers/phy/qualcomm/phy-qcom-qmp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/phy/qualcomm/phy-qcom-qmp.c b/drivers/phy/qualcomm/phy-qcom-qmp.c index 091e20303a14..c2e800a3825a 100644 --- a/drivers/phy/qualcomm/phy-qcom-qmp.c +++ b/drivers/phy/qualcomm/phy-qcom-qmp.c @@ -66,7 +66,7 @@ /* QPHY_V3_PCS_MISC_CLAMP_ENABLE register bits */ #define CLAMP_EN BIT(0) /* enables i/o clamp_n */ -#define PHY_INIT_COMPLETE_TIMEOUT 1000 +#define PHY_INIT_COMPLETE_TIMEOUT 100000 #define POWER_DOWN_DELAY_US_MIN 10 #define POWER_DOWN_DELAY_US_MAX 11 -- 2.23.0