From: Imran Shaik <quic_imrashai@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: 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>,
<netdev@vger.kernel.org>, Ajit Pandey <quic_ajipan@quicinc.com>,
Jagadeesh Kona <quic_jkona@quicinc.com>
Subject: Re: [PATCH V4 2/4] clk: qcom: branch: Add mem ops support for branch2 clocks
Date: Thu, 23 Nov 2023 11:50:59 +0530 [thread overview]
Message-ID: <6f7ee679-38be-abfd-a71c-d33e15c79c7d@quicinc.com> (raw)
In-Reply-To: <90885d90-2e25-404b-b3a3-13d134801146@linaro.org>
On 11/23/2023 1:39 AM, Konrad Dybcio wrote:
>
>
> On 11/17/23 10:55, Imran Shaik wrote:
>> From: Taniya Das <quic_tdas@quicinc.com>
>>
>> Add the support for mem ops implementation to handle the sequence of
>> enable/disable of the memories in ethernet PHY, prior to enable/disable
>> of the respective clocks, which helps retain the respecive block's
>> register contents.
>>
>> Signed-off-by: Taniya Das <quic_tdas@quicinc.com>
>> Signed-off-by: Imran Shaik <quic_imrashai@quicinc.com>
>> ---
>> drivers/clk/qcom/clk-branch.c | 39 +++++++++++++++++++++++++++++++++++
>> drivers/clk/qcom/clk-branch.h | 21 +++++++++++++++++++
>> 2 files changed, 60 insertions(+)
>>
>> diff --git a/drivers/clk/qcom/clk-branch.c
>> b/drivers/clk/qcom/clk-branch.c
>> index fc4735f74f0f..61bdd2147bed 100644
>> --- a/drivers/clk/qcom/clk-branch.c
>> +++ b/drivers/clk/qcom/clk-branch.c
>> @@ -1,6 +1,7 @@
>> // SPDX-License-Identifier: GPL-2.0
>> /*
>> * Copyright (c) 2013, The Linux Foundation. All rights reserved.
>> + * Copyright (c) 2023, Qualcomm Innovation Center, Inc. All rights
>> reserved.
>> */
>> #include <linux/kernel.h>
>> @@ -134,6 +135,44 @@ static void clk_branch2_disable(struct clk_hw *hw)
>> clk_branch_toggle(hw, false, clk_branch2_check_halt);
>> }
>> +static int clk_branch2_mem_enable(struct clk_hw *hw)
>> +{
>> + struct clk_mem_branch *mem_br = to_clk_mem_branch(hw);
>> + struct clk_branch branch = mem_br->branch;
>> + const char *name = clk_hw_get_name(&branch.clkr.hw);
> Bit of a microoptimization, but adding this implicitly in the WARN
> would only execute clk_hw_get_name when necessary
>
Sure, will remove this line and use the clk_hw_get_name implicitly in WARN.
>> + u32 val;
>> + int ret;
>> +
>> + regmap_update_bits(branch.clkr.regmap, mem_br->mem_enable_reg,
>> + mem_br->mem_enable_ack_mask, mem_br->mem_enable_ack_mask);
> It's quite a nit from me, but it would be nice to have the next line
> aligned
> with the opening brace (with a tab size of 8)
>
> Konrad
Sure, will align the lines and post another series.
Thanks,
Imran
next prev parent reply other threads:[~2023-11-23 6:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 9:55 [PATCH V4 0/4] Add support for Qualcomm ECPRI clock controller Imran Shaik
2023-11-17 9:55 ` [PATCH V4 1/4] dt-bindings: clock: qcom: Add ECPRICC clocks for QDU1000 and QRU1000 Imran Shaik
2023-11-17 9:55 ` [PATCH V4 2/4] clk: qcom: branch: Add mem ops support for branch2 clocks Imran Shaik
2023-11-22 20:09 ` Konrad Dybcio
2023-11-23 6:20 ` Imran Shaik [this message]
2023-11-17 9:55 ` [PATCH V4 3/4] clk: qcom: Add ECPRICC driver support for QDU1000 and QRU1000 Imran Shaik
2023-11-17 9:55 ` [PATCH V4 4/4] arm64: dts: qcom: qdu1000: Add ECPRI clock controller Imran Shaik
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=6f7ee679-38be-abfd-a71c-d33e15c79c7d@quicinc.com \
--to=quic_imrashai@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.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=netdev@vger.kernel.org \
--cc=quic_ajipan@quicinc.com \
--cc=quic_jkona@quicinc.com \
--cc=quic_tdas@quicinc.com \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).