Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp578246pxf; Wed, 31 Mar 2021 10:28:14 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxsCBsIBD2xAE4u/+UvvmZ9hWXRJZUvpEehAYp7p0s1bgIzgyOWHSO2P2tg9lIxK86EDyba X-Received: by 2002:a17:906:1494:: with SMTP id x20mr4706788ejc.101.1617211694251; Wed, 31 Mar 2021 10:28:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617211694; cv=none; d=google.com; s=arc-20160816; b=U/QQ04ANhNwYY12G1SJ6cgGDtQ3cFC43MdJh9Bg3PGqVQwQK/iXxjqY+98wWqdifzz PSluPABF9dMxto/f3oo5l6bQlXTp2M6Uq+0/3sF8rJmBVXA7UXz5RCS/kHRISJS6jQUm TkpnmaZMvQtgitwKaJf4vag7JFC9S5WEm8/eDcTsKTrOfAT1Y7yIyb0YkXnWXWBQSkH4 qUOroxBeduWIVxTcSTd/W0iXlmc1Nxll0j5iDwHFdOUptctFDXjbaJCAlgz0fPt9NIAh cVVh/w5PZp250SExYV9lYSUmy3sLajDCeme4KsoDtaHyplD2ex72YESXEfAvfIsd4Jrr 7m7w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:message-id:references:in-reply-to :mail-reply-to:reply-to:organization:subject:cc:to:from:date :content-transfer-encoding:mime-version:sender:dkim-signature; bh=5zPrWlxFJHLDtc9SoIBmfqJpJkOSn1LpHhAgsB/5vG0=; b=dlXpBDzuByYJW5SWYDpvIQViw/t4HVlW61s6hx2lOq2YVmF4faoy3G6PiKtJutHwuv xBd5SC7T7W2WoGuQqEXM4+oHJARhehukjyaurju3t3EYb1iuuW+oW56MApgu7mG22cwK 2Iy2YVX0FKExNhzEvpPZCIZdy/8B2mcCVI0FfmbJH0Nkj7MSgXbuE9M/zZ2cwtLgreQq vsFDMMIw3shSAa4OgTC7Hr93HzGaPsVYpgR1aQvv087bGhzMcwqg5SAUnOfmFmi9X2br dj9jSq2u5hWxRFe1P4F1W6hnUxtyAJrj597a87YWyyiUhlTRy8EbR4TvjFq+DSHgoNi9 wZtA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@mg.codeaurora.org header.s=smtp header.b=v4AFphOR; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id rl3si2113464ejb.86.2021.03.31.10.27.50; Wed, 31 Mar 2021 10:28:14 -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=@mg.codeaurora.org header.s=smtp header.b=v4AFphOR; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234047AbhCaRYA (ORCPT + 99 others); Wed, 31 Mar 2021 13:24:00 -0400 Received: from so254-9.mailgun.net ([198.61.254.9]:24885 "EHLO so254-9.mailgun.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234386AbhCaRX0 (ORCPT ); Wed, 31 Mar 2021 13:23:26 -0400 DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=mg.codeaurora.org; q=dns/txt; s=smtp; t=1617211406; h=Message-ID: References: In-Reply-To: Reply-To: Subject: Cc: To: From: Date: Content-Transfer-Encoding: Content-Type: MIME-Version: Sender; bh=5zPrWlxFJHLDtc9SoIBmfqJpJkOSn1LpHhAgsB/5vG0=; b=v4AFphORCKIDwRGXNTLhuZRO+VfzHq1UfK4VJwujJSIE8eu+gCFblrZ8avQD6TlOzZCqr6IU jO4PzPXr/QyGp5IFdbDMzj5aKtFwpfbT/7tghPQlx4EcAYUAfgSwD/5sRYzIxGPEIdRcq/br ycGK0eOdOIDEPM+OVOM8mXw49zk= X-Mailgun-Sending-Ip: 198.61.254.9 X-Mailgun-Sid: WyI0MWYwYSIsICJsaW51eC1rZXJuZWxAdmdlci5rZXJuZWwub3JnIiwgImJlOWU0YSJd Received: from smtp.codeaurora.org (ec2-35-166-182-171.us-west-2.compute.amazonaws.com [35.166.182.171]) by smtp-out-n03.prod.us-east-1.postgun.com with SMTP id 6064affa03cfff345268c71a (version=TLS1.2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256); Wed, 31 Mar 2021 17:23:06 GMT Sender: bbhatt=codeaurora.org@mg.codeaurora.org Received: by smtp.codeaurora.org (Postfix, from userid 1001) id F2690C43463; Wed, 31 Mar 2021 17:23:05 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-caf-mail-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.9 required=2.0 tests=ALL_TRUSTED,BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.codeaurora.org (localhost.localdomain [127.0.0.1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: bbhatt) by smtp.codeaurora.org (Postfix) with ESMTPSA id EA0B9C433C6; Wed, 31 Mar 2021 17:23:04 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Wed, 31 Mar 2021 10:23:04 -0700 From: Bhaumik Bhatt To: Manivannan Sadhasivam Cc: linux-arm-msm@vger.kernel.org, hemantk@codeaurora.org, jhugo@codeaurora.org, linux-kernel@vger.kernel.org, carl.yin@quectel.com, naveen.kumar@quectel.com, loic.poulain@linaro.org Subject: Re: [PATCH v5 2/2] bus: mhi: core: Move to polling method to wait for MHI ready Organization: Qualcomm Innovation Center, Inc. Reply-To: bbhatt@codeaurora.org Mail-Reply-To: bbhatt@codeaurora.org In-Reply-To: <20210331130451.GJ15610@work> References: <1617047583-12104-1-git-send-email-bbhatt@codeaurora.org> <1617047583-12104-3-git-send-email-bbhatt@codeaurora.org> <20210331130451.GJ15610@work> Message-ID: <0ae6fde544fe67ea9b0a849026a344e2@codeaurora.org> X-Sender: bbhatt@codeaurora.org User-Agent: Roundcube Webmail/1.3.9 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2021-03-31 06:04 AM, Manivannan Sadhasivam wrote: > On Mon, Mar 29, 2021 at 12:53:03PM -0700, Bhaumik Bhatt wrote: >> In certain devices, it is likely that there is no incoming MHI >> interrupt for a transition to MHI READY state. One such example >> is the move from Pass Through to an SBL or AMSS execution >> environment. In order to facilitate faster bootup times as there >> is no need to wait until timeout_ms completes, MHI host can poll >> every 25 milliseconds to check if device has entered MHI READY >> until a maximum timeout of twice the timeout_ms is reached. >> >> Signed-off-by: Bhaumik Bhatt >> --- >> drivers/bus/mhi/core/pm.c | 32 +++++++++++++++----------------- >> 1 file changed, 15 insertions(+), 17 deletions(-) >> >> diff --git a/drivers/bus/mhi/core/pm.c b/drivers/bus/mhi/core/pm.c >> index 681960c..dcc7fe0 100644 >> --- a/drivers/bus/mhi/core/pm.c >> +++ b/drivers/bus/mhi/core/pm.c >> @@ -153,34 +153,32 @@ static void mhi_toggle_dev_wake(struct >> mhi_controller *mhi_cntrl) >> /* Handle device ready state transition */ >> int mhi_ready_state_transition(struct mhi_controller *mhi_cntrl) >> { >> - void __iomem *base = mhi_cntrl->regs; >> struct mhi_event *mhi_event; >> enum mhi_pm_state cur_state; >> struct device *dev = &mhi_cntrl->mhi_dev->dev; >> - u32 reset = 1, ready = 0; >> + u32 interval_us = 25000; /* poll register field every 25 >> milliseconds */ >> int ret, i; >> >> - /* Wait for RESET to be cleared and READY bit to be set by the >> device */ >> - wait_event_timeout(mhi_cntrl->state_event, >> - MHI_PM_IN_FATAL_STATE(mhi_cntrl->pm_state) || >> - mhi_read_reg_field(mhi_cntrl, base, MHICTRL, >> - MHICTRL_RESET_MASK, >> - MHICTRL_RESET_SHIFT, &reset) || >> - mhi_read_reg_field(mhi_cntrl, base, MHISTATUS, >> - MHISTATUS_READY_MASK, >> - MHISTATUS_READY_SHIFT, &ready) || >> - (!reset && ready), >> - msecs_to_jiffies(mhi_cntrl->timeout_ms)); >> - >> /* Check if device entered error state */ >> if (MHI_PM_IN_FATAL_STATE(mhi_cntrl->pm_state)) { >> dev_err(dev, "Device link is not accessible\n"); >> return -EIO; >> } >> >> - /* Timeout if device did not transition to ready state */ >> - if (reset || !ready) { >> - dev_err(dev, "Device Ready timeout\n"); >> + /* Wait for RESET to be cleared and READY bit to be set by the >> device */ >> + ret = mhi_poll_reg_field(mhi_cntrl, mhi_cntrl->regs, MHICTRL, >> + MHICTRL_RESET_MASK, MHICTRL_RESET_SHIFT, 0, >> + interval_us); >> + if (ret) { >> + dev_err(dev, "Device failed to clear MHI Reset\n"); >> + return -ETIMEDOUT; > > You should return the actual error code since there are couple of error > paths. > > Thanks, > Mani > Sure. With the update on patch #1, this will be taken care of properly as we return -ETIMEDOUT from the API. >> + } >> + >> + ret = mhi_poll_reg_field(mhi_cntrl, mhi_cntrl->regs, MHISTATUS, >> + MHISTATUS_READY_MASK, MHISTATUS_READY_SHIFT, 1, >> + interval_us); >> + if (ret) { >> + dev_err(dev, "Device failed to enter MHI Ready\n"); >> return -ETIMEDOUT; >> } >> >> -- >> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora >> Forum, >> a Linux Foundation Collaborative Project >> Thanks, Bhaumik --- The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project