From: Sricharan R <sricharan@codeaurora.org>
To: Vinod <vkoul@kernel.org>
Cc: bjorn.andersson@linaro.org, ohad@wizery.com, robh+dt@kernel.org,
mark.rutland@arm.com, andy.gross@linaro.org,
david.brown@linaro.org, linux-remoteproc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
sibis@codeaurora.org
Subject: Re: [PATCH V6 5/5] remoteproc: qcom: Add q6v5-wcss rproc ops
Date: Tue, 22 May 2018 14:32:48 +0530 [thread overview]
Message-ID: <4d21e075-68c5-b2a7-c7fd-ce5b6a195166@codeaurora.org> (raw)
In-Reply-To: <20180518122946.GC31996@vkoul-mobl>
Hi,
On 5/18/2018 5:59 PM, Vinod wrote:
> On 14-05-18, 16:16, Sricharan R wrote:
>
>> +static int q6v5_wcss_start(struct rproc *rproc)
>> +{
>> + struct q6v5 *qproc = rproc->priv;
>> + int ret = 0;
>
> Superfluous initialization
>
ok.
>> +
>> + ret = q6v5_clk_enable(qproc->dev, qproc->active_clks,
>> + qproc->active_clk_count);
>> + if (ret) {
>> + dev_err(qproc->dev, "failed to enable clocks\n");
>> + return ret;
>> + }
>> +
>> + /* Release Q6 and WCSS reset */
>> + ret = reset_control_deassert(qproc->wcss_reset);
>> + if (ret)
>> + dev_err(qproc->dev, "wcss_reset failed\n");
>> +
>> + ret = reset_control_deassert(qproc->wcss_q6_reset);
>> + if (ret)
>> + dev_err(qproc->dev, "wcss_q6_reset failed\n");
>
> shouldn't we abort on these two errors?
>
ha right. will fix it.
>> +
>> + /* Lithium configuration - clock gating and bus arbitration */
>> + ret = regmap_update_bits(qproc->halt_map,
>> + qproc->halt_nc + TCSR_GLOBAL_CFG0,
>> + 0x1F, 0x14);
>> + if (ret)
>> + return ret;
>> +
>> + ret = regmap_update_bits(qproc->halt_map,
>> + qproc->halt_nc + TCSR_GLOBAL_CFG1,
>> + 1, 0);
>> + if (ret)
>> + return ret;
>> +
>> + /* Write bootaddr to EVB so that Q6WCSS will jump there after reset */
>> + writel(rproc->bootaddr >> 4, qproc->reg_base + QDSP6SS_RST_EVB);
>> +
>> + ret = q6v5_reset(qproc);
>> + if (ret)
>> + return ret;
>
> all these returns, aren't we leaving device in some dangling state?
>
hmm ok. clocks and resets have to be reverted. will add error handling here.
>> +static int q6v5_wcss_powerdown(struct q6v5 *qproc)
>> +{
>> + unsigned int val = 0;
>
> superfluous initialization
>
ok.
>> + int ret;
>> +
>> + /* 1 - Assert WCSS/Q6 HALTREQ */
>> + q6v5proc_halt_axi_port(qproc, qproc->halt_map, qproc->halt_modem);
>> +
>> + /* 2 - Enable WCSSAON_CONFIG */
>> + val = readl(qproc->rmb_base + SSCAON_CONFIG);
>> + val |= SSCAON_ENABLE;
>> + writel(val, qproc->rmb_base + SSCAON_CONFIG);
>> +
>> + /* 3 - Set SSCAON_CONFIG */
>> + val |= BIT(15);
>> + val &= ~BIT(16);
>> + val &= ~BIT(17);
>> + val &= ~BIT(18);
>
> shouldn't bit 15 thru 18 be defined on what they mean?
>
hmm, ok. would define them.
>> +static int q6v5_q6_powerdown(struct q6v5 *qproc)
>> +{
>> + int i = 0, ret;
>> + unsigned int val = 0;
>> +
>> + /* 1 - Halt Q6 bus interface */
>> + q6v5proc_halt_axi_port(qproc, qproc->halt_map, qproc->halt_q6);
>> +
>> + /* 2 - Disable Q6 Core clock */
>> + val = readl(qproc->reg_base + QDSP6SS_GFMUX_CTL_REG);
>> + val &= ~Q6SS_CLK_ENABLE;
>> + writel(val, qproc->reg_base + QDSP6SS_GFMUX_CTL_REG);
>> +
>> + /* 3 - Clamp I/O */
>> + val = readl(qproc->reg_base + QDSP6SS_PWR_CTL_REG);
>> + val |= Q6SS_CLAMP_IO;
>> + writel(val, qproc->reg_base + QDSP6SS_PWR_CTL_REG);
>> +
>> + /* 4 - Clamp WL */
>> + val |= QDSS_BHS_ON;
>> + writel(val, qproc->reg_base + QDSP6SS_PWR_CTL_REG);
>> +
>> + /* 5 - Clear Erase standby */
>> + val &= ~Q6SS_L2DATA_STBY_N;
>> + writel(val, qproc->reg_base + QDSP6SS_PWR_CTL_REG);
>> +
>> + /* 6 - Clear Sleep RTN */
>> + val &= ~Q6SS_SLP_RET_N;
>> + writel(val, qproc->reg_base + QDSP6SS_PWR_CTL_REG);
>> +
>> + /* 7 - turn off QDSP6 memory foot/head switch one bank at a time */
>> + for (i = 0; i < 20; i++) {
>> + val = readl(qproc->reg_base + QDSP6SS_MEM_PWR_CTL);
>> + val &= ~BIT(i);
>> + writel(val, qproc->reg_base + QDSP6SS_MEM_PWR_CTL);
>> + mdelay(1);
>> + }
>> + /* 8 - Assert QMC memory RTN */
>> + val = readl(qproc->reg_base + QDSP6SS_PWR_CTL_REG);
>> + val |= QDSP6v56_CLAMP_QMC_MEM;
>> + writel(val, qproc->reg_base + QDSP6SS_PWR_CTL_REG);
>> +
>> + /* 9 - Turn off BHS */
>> + val &= ~QDSP6v56_BHS_ON;
>> + writel(val, qproc->reg_base + QDSP6SS_PWR_CTL_REG);
>> + udelay(1);
>> + /* 10 - Wait till BHS Reset is done */
>
> would help in readability if you can be consistent and add empty lines after each
> step as done for rest of the routine
>
ok.
>> +static int q6v5_wcss_stop(struct rproc *rproc)
>> +{
>> + struct q6v5 *qproc = rproc->priv;
>> + int ret = 0;
>
> this one too, I think if you run with sparse, it should warn you about these
>
ok, sure would check.
>> +
>> + qproc->running = false;
>> +
>> + /* WCSS powerdown */
>> + qcom_smem_state_update_bits(qproc->state, BIT(qproc->stop_bit),
>> + BIT(qproc->stop_bit));
>> +
>> + ret = wait_for_completion_timeout(&qproc->stop_done,
>> + msecs_to_jiffies(5000));
>> + if (ret == 0) {
>> + dev_err(qproc->dev, "timed out on wait\n");
>> + return -ETIMEDOUT;
>> + }
>> +
>> + qcom_smem_state_update_bits(qproc->state, BIT(qproc->stop_bit), 0);
>> +
>> + ret = q6v5_wcss_powerdown(qproc);
>> + if (ret)
>> + return ret;
>> +
>> + /* Q6 Power down */
>> + ret = q6v5_q6_powerdown(qproc);
>> + if (ret)
>> + return ret;
>> +
>> + return 0;
>
> this could be optimized to:
> return q6v5_q6_powerdown()
>
ok.
Regards,
Sricharan
--
"QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
prev parent reply other threads:[~2018-05-22 9:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 10:46 [PATCH V6 0/5] Add support for Hexagon q6v5-wcss integrated core Sricharan R
2018-05-14 10:46 ` [PATCH V6 1/5] remoteproc: qcom: mdt_loader: Make the firmware authentication optional Sricharan R
2018-05-14 10:46 ` [PATCH V6 2/5] remoteproc: qcom: Push reset ops, rproc ops in to of_match data Sricharan R
2018-05-14 10:46 ` [PATCH V6 3/5] remoteproc: qcom: Split the head and tail of the q5v5-pil rproc reset function Sricharan R
2018-05-18 12:22 ` Vinod
2018-05-22 8:50 ` Sricharan R
2018-05-14 10:46 ` [PATCH V6 4/5] remoteproc: qcom: Add support for q6v5-wcss pil Sricharan R
2018-05-14 10:46 ` [PATCH V6 5/5] remoteproc: qcom: Add q6v5-wcss rproc ops Sricharan R
2018-05-18 12:29 ` Vinod
2018-05-22 9:02 ` Sricharan R [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4d21e075-68c5-b2a7-c7fd-ce5b6a195166@codeaurora.org \
--to=sricharan@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ohad@wizery.com \
--cc=robh+dt@kernel.org \
--cc=sibis@codeaurora.org \
--cc=vkoul@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome