Linux clock framework development
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Taniya Das <quic_tdas@quicinc.com>
Cc: Ajit Pandey <quic_ajipan@quicinc.com>,
	Imran Shaik <quic_imrashai@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 0/2] clk: qcom: gcc: Update the force_mem_core for UFS ICE
Date: Mon, 19 May 2025 21:14:54 -0500	[thread overview]
Message-ID: <174770727726.36693.3666336524459019833.b4-ty@kernel.org> (raw)
In-Reply-To: <20250414-gcc_ufs_mem_core-v1-0-67b5529b9b5d@quicinc.com>


On Mon, 14 Apr 2025 14:30:39 +0530, Taniya Das wrote:
> The MCQ feature of UFS requires the both UFS ice and UFS phy axi clocks
> to have the force_mem_core bit set to allow retention after power
> collapse.
> 
> 

Applied, thanks!

[1/2] clk: qcom: gcc: Set FORCE_MEM_CORE_ON for gcc_ufs_axi_clk for 8650/8750
      commit: da94a81ea6c6f1cd2f389c5631e33c145ac7b35b
[2/2] clk: qcom: gcc-x1e80100: Set FORCE MEM CORE for UFS clocks
      commit: 201bf08ba9e26eeb0a96ba3fd5c026f531b31aed

Best regards,
-- 
Bjorn Andersson <andersson@kernel.org>

      parent reply	other threads:[~2025-05-20  2:15 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
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 ` Bjorn Andersson [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=174770727726.36693.3666336524459019833.b4-ty@kernel.org \
    --to=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_imrashai@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