[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c7956e65-d21b-8844-45d7-de06b8d3d4f0@codeaurora.org>
Date: Thu, 9 Jul 2020 13:00:28 +0530
From: Akash Asthana <akashast@...eaurora.org>
To: Douglas Anderson <dianders@...omium.org>,
Mark Brown <broonie@...nel.org>,
Andy Gross <agross@...nel.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>
Cc: linux-arm-msm@...r.kernel.org,
Rajendra Nayak <rnayak@...eaurora.org>,
georgi.djakov@...aro.org, swboyd@...omium.org,
mkshah@...eaurora.org, ctheegal@...eaurora.org, mka@...omium.org,
linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org
Subject: Re: [PATCH] spi: spi-geni-qcom: Set the clock properly at runtime
resume
Hi Doug,
>
> @@ -670,7 +674,13 @@ static int __maybe_unused spi_geni_runtime_resume(struct device *dev)
> if (ret)
> return ret;
>
> - return geni_se_resources_on(&mas->se);
> + ret = geni_se_resources_on(&mas->se);
> + if (ret)
> + return ret;
> +
> + dev_pm_opp_set_rate(mas->dev, mas->cur_sclk_hz);
> +
> + return 0;
> }
Should we fail to resume if error is returned from 'opp_set_rate'?
'spi_geni_prepare_message' use to fail for any error from
'opp_set_rate' before patch series "Avoid clock setting if not needed".
But now it's possible that 'prepare_message' can return success even
when opp are not at desired state(from previous resume call).
Regards,
Akash
>
> static int __maybe_unused spi_geni_suspend(struct device *dev)
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,\na Linux Foundation Collaborative Project
Powered by blists - more mailing lists