From: Taniya Das <taniya.das@oss.qualcomm.com>
To: Joonhoe Kim <26rote@gmail.com>, andersson@kernel.org, sboyd@kernel.org
Cc: mturquette@baylibre.com, dmitry.baryshkov@oss.qualcomm.com,
konrad.dybcio@oss.qualcomm.com, abelvesa@kernel.org,
bmasney+clk@redhat.com, jbrunet+clk@baylibre.com,
nitin.rawat@oss.qualcomm.com, linux-arm-msm@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: qcom: gcc-kaanapali: Enable FORCE_MEM_CORE_ON for UFS AXI PHY clock
Date: Tue, 13 Oct 2026 13:04:13 +0530 [thread overview]
Message-ID: <2e4d9a74-cf38-416b-b3fb-15584301e540@oss.qualcomm.com> (raw)
In-Reply-To: <20261007143716.2161-1-26rote@gmail.com>
On 10/7/2026 8:07 PM, Joonhoe Kim wrote:
> As on SM8650, SM8750 and Eliza, the UFS AXI PHY clock needs
> FORCE_MEM_CORE_ON for the UFS controller in MCQ mode. Without it the MCQ
> configuration is lost over system suspend, and with MCQ enabled every
> resume from s2idle ends in an SMMU fault and a host reset.
>
> The UFS PHY ICE core clock already has the bit set; set it for the UFS
> PHY AXI clock as well.
>
> Fixes: d1919c375f21 ("clk: qcom: Add support for Global clock controller on Kaanapali")
> Assisted-by: LLM
> Signed-off-by: Joonhoe Kim <26rote@gmail.com>
> ---
> Tested on a Lenovo Legion Tab Y700 Gen 5 with MCQ enabled in its DT:
> the MCQ registers keep their values over s2idle, 7 of 7 resumes
> without a UFS error. Kaanapali was noted as the missing one in the
> Eliza thread [1].
>
> [1] https://lore.kernel.org/all/a0b6030f-be42-4f5d-a59c-
> db78912ff0de@oss.qualcomm.com/
>
> drivers/clk/qcom/gcc-kaanapali.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/clk/qcom/gcc-kaanapali.c b/drivers/clk/qcom/gcc-kaanapali.c
> index c9473fb79ccc..6834f43b72ca 100644
> --- a/drivers/clk/qcom/gcc-kaanapali.c
> +++ b/drivers/clk/qcom/gcc-kaanapali.c
> @@ -3484,6 +3484,7 @@ static void clk_kaanapali_regs_configure(struct device *dev, struct regmap *regm
>
> /* FORCE_MEM_CORE_ON for ufs phy ice core clocks */
> qcom_branch_set_force_mem_core(regmap, gcc_ufs_phy_ice_core_clk, true);
> + qcom_branch_set_force_mem_core(regmap, gcc_ufs_phy_axi_clk, true);
> }
>
Reviewed-by: Taniya Das <taniya.das@oss.qualcomm.com>
--
Thanks,
Taniya Das
prev parent reply other threads:[~2026-10-13 7:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 14:37 Joonhoe Kim
2026-10-09 18:22 ` Abel Vesa
2026-10-13 7:34 ` Taniya Das [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=2e4d9a74-cf38-416b-b3fb-15584301e540@oss.qualcomm.com \
--to=taniya.das@oss.qualcomm.com \
--cc=26rote@gmail.com \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=bmasney+clk@redhat.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=jbrunet+clk@baylibre.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=nitin.rawat@oss.qualcomm.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
all inboxes | Powered by JetHome®