From: Imran Shaik <quic_imrashai@quicinc.com>
To: Taniya Das <quic_tdas@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@kernel.org>
Cc: Ajit Pandey <quic_ajipan@quicinc.com>,
Jagadeesh Kona <quic_jkona@quicinc.com>,
<linux-arm-msm@vger.kernel.org>, <linux-clk@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] clk: qcom: gcc: Set FORCE_MEM_CORE_ON for gcc_ufs_axi_clk for 8650/8750
Date: Fri, 2 May 2025 16:37:13 +0530 [thread overview]
Message-ID: <c86eb414-d11e-4e68-a61d-6034f989a71d@quicinc.com> (raw)
In-Reply-To: <20250414-gcc_ufs_mem_core-v1-1-67b5529b9b5d@quicinc.com>
On 4/14/2025 2:30 PM, Taniya Das wrote:
> Update the force mem core bit for UFS AXI clock to force the core on
> signal to remain active during halt state of the clk. If force mem
> core bit of the clock is not set, the memories of the subsystem will
> not retain the logic across power states. This is required for the MCQ
> feature of the UFS driver.
>
> Signed-off-by: Taniya Das <quic_tdas@quicinc.com>
> ---
> drivers/clk/qcom/gcc-sm8650.c | 2 ++
> drivers/clk/qcom/gcc-sm8750.c | 3 ++-
> 2 files changed, 4 insertions(+), 1 deletion(-)
>
Reviewed-by: Imran Shaik <quic_imrashai@quicinc.com>
Thanks,
Imran
next prev parent reply other threads:[~2025-05-02 11:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 9:00 [PATCH 0/2] clk: qcom: gcc: Update the force_mem_core for UFS ICE Taniya Das
2025-04-14 9:00 ` [PATCH 1/2] clk: qcom: gcc: Set FORCE_MEM_CORE_ON for gcc_ufs_axi_clk for 8650/8750 Taniya Das
2025-05-02 11:07 ` Imran Shaik [this message]
2025-04-14 9:00 ` [PATCH 2/2] clk: qcom: gcc-x1e80100: Set FORCE MEM CORE for UFS clocks Taniya Das
2025-05-02 11:08 ` Imran Shaik
2025-05-20 2:14 ` [PATCH 0/2] clk: qcom: gcc: Update the force_mem_core for UFS ICE Bjorn Andersson
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=c86eb414-d11e-4e68-a61d-6034f989a71d@quicinc.com \
--to=quic_imrashai@quicinc.com \
--cc=andersson@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=quic_ajipan@quicinc.com \
--cc=quic_jkona@quicinc.com \
--cc=quic_tdas@quicinc.com \
--cc=sboyd@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