From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Devi Priya <quic_devipriy@quicinc.com>,
agross@kernel.org, andersson@kernel.org,
konrad.dybcio@linaro.org, mturquette@baylibre.com,
sboyd@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
catalin.marinas@arm.com, will@kernel.org, p.zabel@pengutronix.de,
richardcochran@gmail.com, arnd@arndb.de, geert+renesas@glider.be,
neil.armstrong@linaro.org, nfraprado@collabora.com,
rafal@milecki.pl, linux-arm-msm@vger.kernel.org,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org
Cc: quic_saahtoma@quicinc.com
Subject: Re: [PATCH 2/6] clk: qcom: gcc-ipq9574: Mark nssnoc clocks as critical
Date: Tue, 11 Jul 2023 13:25:12 +0300 [thread overview]
Message-ID: <8433cbfa-52c5-90c5-1e4c-0b13236d2153@linaro.org> (raw)
In-Reply-To: <20230711093529.18355-3-quic_devipriy@quicinc.com>
On 11/07/2023 12:35, Devi Priya wrote:
> Mark nssnoc clocks as critical as they are to be turned on to access
> nss port tx/rx clocks.
Can you please clarify, if these are turned off, one can not access
nsscc clocks? Then the nsscc should be the consumer of these clocks
(instead of declaring them as critical). May be using pm_clk for nsscc
will work. If not, you'll have to do that manually from
runtime_suspend/runtime_resume callbacks.
>
> Signed-off-by: Devi Priya <quic_devipriy@quicinc.com>
> ---
> drivers/clk/qcom/gcc-ipq9574.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/clk/qcom/gcc-ipq9574.c b/drivers/clk/qcom/gcc-ipq9574.c
> index 6914f962c893..b68addc6f687 100644
> --- a/drivers/clk/qcom/gcc-ipq9574.c
> +++ b/drivers/clk/qcom/gcc-ipq9574.c
> @@ -2166,7 +2166,7 @@ static struct clk_branch gcc_nssnoc_nsscc_clk = {
> &pcnoc_bfdcd_clk_src.clkr.hw
> },
> .num_parents = 1,
> - .flags = CLK_SET_RATE_PARENT,
> + .flags = CLK_SET_RATE_PARENT | CLK_IS_CRITICAL,
> .ops = &clk_branch2_ops,
> },
> },
> @@ -2565,7 +2565,7 @@ static struct clk_branch gcc_nssnoc_snoc_clk = {
> &system_noc_bfdcd_clk_src.clkr.hw
> },
> .num_parents = 1,
> - .flags = CLK_SET_RATE_PARENT,
> + .flags = CLK_SET_RATE_PARENT | CLK_IS_CRITICAL,
> .ops = &clk_branch2_ops,
> },
> },
> @@ -2582,7 +2582,7 @@ static struct clk_branch gcc_nssnoc_snoc_1_clk = {
> &system_noc_bfdcd_clk_src.clkr.hw
> },
> .num_parents = 1,
> - .flags = CLK_SET_RATE_PARENT,
> + .flags = CLK_SET_RATE_PARENT | CLK_IS_CRITICAL,
> .ops = &clk_branch2_ops,
> },
> },
--
With best wishes
Dmitry
next prev parent reply other threads:[~2023-07-11 10:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 9:35 [PATCH 0/6] Add NSS clock controller support for IPQ9574 Devi Priya
2023-07-11 9:35 ` [PATCH 1/6] clk: qcom: clk-alpha-pll: Add NSS HUAYRA ALPHA PLL support for ipq9574 Devi Priya
2023-07-11 10:46 ` Dmitry Baryshkov
2023-07-11 9:35 ` [PATCH 2/6] clk: qcom: gcc-ipq9574: Mark nssnoc clocks as critical Devi Priya
2023-07-11 10:25 ` Dmitry Baryshkov [this message]
2023-08-24 5:24 ` Devi Priya
2023-07-11 9:35 ` [PATCH 3/6] dt-bindings: clock: Add ipq9574 NSSCC clock and reset definitions Devi Priya
2023-07-11 9:54 ` Krzysztof Kozlowski
2023-07-17 6:10 ` Devi Priya
2023-08-24 5:18 ` Kathiravan T
2023-08-24 5:23 ` Devi Priya
2023-08-24 8:47 ` Konrad Dybcio
2023-08-25 8:56 ` Devi Priya
2023-07-11 9:35 ` [PATCH 4/6] clk: qcom: Add NSS clock Controller driver for IPQ9574 Devi Priya
2023-07-11 9:56 ` Krzysztof Kozlowski
2023-07-18 9:12 ` Devi Priya
2023-07-11 10:50 ` Dmitry Baryshkov
2023-07-18 9:13 ` Devi Priya
2023-07-13 5:37 ` Simon Horman
2023-07-17 6:36 ` Devi Priya
2023-07-11 9:35 ` [PATCH 5/6] arm64: dts: qcom: ipq9574: Add support for nsscc node Devi Priya
2023-07-11 9:57 ` Krzysztof Kozlowski
2023-08-24 5:25 ` Devi Priya
2023-07-11 9:35 ` [PATCH 6/6] arm64: defconfig: Build NSS Clock Controller driver for IPQ9574 Devi Priya
2023-07-11 10:48 ` Dmitry Baryshkov
2023-08-24 5:25 ` Devi Priya
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=8433cbfa-52c5-90c5-1e4c-0b13236d2153@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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=neil.armstrong@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=nfraprado@collabora.com \
--cc=p.zabel@pengutronix.de \
--cc=quic_devipriy@quicinc.com \
--cc=quic_saahtoma@quicinc.com \
--cc=rafal@milecki.pl \
--cc=richardcochran@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).