From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Abel Vesa <abel.vesa@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Luca Weiss <luca.weiss@fairphone.com>,
Taniya Das <taniya.das@oss.qualcomm.com>,
Taniya Das <quic_tdas@quicinc.com>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Subject: Re: [PATCH v3 5/6] clk: qcom: Add support for Global clock controller on Eliza
Date: Tue, 17 Feb 2026 10:26:26 +0100 [thread overview]
Message-ID: <f3394308-ee08-45db-a0fb-569d1cdd7fca@oss.qualcomm.com> (raw)
In-Reply-To: <cqx6t5tcshcqyof4aaeawa7gyocaokzyqjmyxgxis7xsfc4wwg@jeggol3ifwu7>
On 2/17/26 8:57 AM, Abel Vesa wrote:
> On 26-02-16 16:57:24, Konrad Dybcio wrote:
>> On 2/16/26 2:43 PM, Abel Vesa wrote:
>>> From: Taniya Das <taniya.das@oss.qualcomm.com>
>>>
>>> Add support for Global clock controller for Eliza Qualcomm SoC.
>>>
>>> Signed-off-by: Taniya Das <taniya.das@oss.qualcomm.com>
>>> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
>>> Signed-off-by: Abel Vesa <abel.vesa@oss.qualcomm.com>
>>> ---
>>
>> Do we need force_mem_on on UFS clocks?
>
> Not sure yet as UFS isn't up.
FWIW downstream does that for this platform and it seems to be the
case on most recent platforms too
Konrad
next prev parent reply other threads:[~2026-02-17 9:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 13:43 [PATCH v3 0/6] clk: qcom: Add support for basic clocks providers on Eliza SoC Abel Vesa
2026-02-16 13:43 ` [PATCH v3 1/6] dt-bindings: clock: qcom: document the Eliza Global Clock Controller Abel Vesa
2026-02-17 10:31 ` Krzysztof Kozlowski
2026-02-16 13:43 ` [PATCH v3 2/6] dt-bindings: clock: qcom: Document the Eliza TCSR " Abel Vesa
2026-02-16 13:43 ` [PATCH v3 3/6] dt-bindings: clock: qcom-rpmhcc: Add RPMHCC for Eliza Abel Vesa
2026-02-16 13:43 ` [PATCH v3 4/6] clk: qcom: rpmh: Add support for Eliza rpmh clocks Abel Vesa
2026-02-16 15:05 ` Konrad Dybcio
2026-02-16 17:14 ` Abel Vesa
2026-02-16 13:43 ` [PATCH v3 5/6] clk: qcom: Add support for Global clock controller on Eliza Abel Vesa
2026-02-16 15:38 ` Konrad Dybcio
2026-02-17 7:58 ` Abel Vesa
2026-02-17 10:15 ` Konrad Dybcio
2026-02-23 10:48 ` Abel Vesa
2026-02-16 15:57 ` Konrad Dybcio
2026-02-17 7:57 ` Abel Vesa
2026-02-17 9:26 ` Konrad Dybcio [this message]
2026-02-23 10:50 ` Abel Vesa
2026-02-17 13:50 ` Krzysztof Kozlowski
2026-02-16 13:43 ` [PATCH v3 6/6] clk: qcom: Add TCSR clock driver for Eliza Abel Vesa
2026-02-16 15:08 ` Konrad Dybcio
2026-02-17 2:10 ` kernel test robot
2026-02-17 7:53 ` Abel Vesa
2026-02-17 2:31 ` kernel test robot
2026-02-17 7:53 ` Abel Vesa
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=f3394308-ee08-45db-a0fb-569d1cdd7fca@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=abel.vesa@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=mturquette@baylibre.com \
--cc=quic_tdas@quicinc.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=taniya.das@oss.qualcomm.com \
/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