From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Stephen Boyd <sboyd@kernel.org>,
andy.gross@linaro.org, linux-arm-msm@vger.kernel.org,
linux-clk@vger.kernel.org
Cc: david.brown@linaro.org, mturquette@baylibre.com,
robh+dt@kernel.org, linux-soc@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
georgi.djakov@linaro.org
Subject: Re: [RFC PATCH] clk: qcom: rpmcc: Add support to XO buffered clocks
Date: Thu, 15 Mar 2018 18:04:42 +0000 [thread overview]
Message-ID: <256371b1-82aa-4fe4-b767-4025395082fd@linaro.org> (raw)
In-Reply-To: <152113633637.107923.1559162375425599621@swboyd.mtv.corp.google.com>
Thanks for the review comments,
On 15/03/18 17:52, Stephen Boyd wrote:
> Quoting srinivas.kandagatla@linaro.org (2018-03-15 07:37:24)
>> diff --git a/drivers/clk/qcom/clk-rpm.c b/drivers/clk/qcom/clk-rpm.c
>> index c60f61b10c7f..261f5505e714 100644
>> --- a/drivers/clk/qcom/clk-rpm.c
>> +++ b/drivers/clk/qcom/clk-rpm.c
>> @@ -56,6 +57,19 @@
>> }, \
>> }
>>
>> +#define DEFINE_CLK_RPM_XO_BUFFER(_platform, _name, _active, offset) \
>> + static struct clk_rpm _platform##_##_name = { \
>> + .rpm_clk_id = QCOM_RPM_CXO_BUFFERS, \
>> + .xo_offset = (offset), \
>> + .rate = 19200000, \
>
> Shouldn't these rates also come from parent, i.e. pxo_board? So drop
> this line?
Yep, will remove this.
>
>> + .hw.init = &(struct clk_init_data){ \
>> + .ops = &clk_rpm_fixed_ops, \
>> + .name = #_name, \
>> + .parent_names = (const char *[]){ "pxo_board" }, \
>> + .num_parents = 1, \
>> + }, \
>> + }
>> +
>> #define DEFINE_CLK_RPM_FIXED(_platform, _name, _active, r_id, r) \
>> static struct clk_rpm _platform##_##_name = { \
>> .rpm_clk_id = (r_id), \
>> @@ -128,6 +142,8 @@
>>
>> struct clk_rpm {
>> const int rpm_clk_id;
>> + const int xo_offset;
>> + u32 xo_buffer_value;
>> const bool active_only;
>> unsigned long rate;
>> bool enabled;
>> @@ -308,6 +330,11 @@ static void clk_rpm_fixed_unprepare(struct clk_hw *hw)
>> u32 value = 0;
>> int ret;
>>
>> + if (r->rpm_clk_id == QCOM_RPM_CXO_BUFFERS) {
>> + r->xo_buffer_value &= ~(QCOM_RPM_XO_MODE_ON << r->xo_offset);
>> + value = r->xo_buffer_value;
>> + }
>> +
>
> I seem to recall that the xo buffers are within the same "word" or
> something like that for each of the buffers. So we would need to make
> sure we don't overwrite the bits in there between clks that are
Code as it is will not work.
> enabling/disabling stuff. Maybe make some sort of shared variable they
> all point to and then put a mutex around it? May also be worth making
> more clk_ops at that point to not conflate with the simpler on/off code.
Yep, I will give something like that a try in next version.
-srini
>
prev parent reply other threads:[~2018-03-15 18:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 14:37 [RFC PATCH] clk: qcom: rpmcc: Add support to XO buffered clocks srinivas.kandagatla
2018-03-15 16:24 ` Srinivas Kandagatla
2018-03-15 17:52 ` Stephen Boyd
2018-03-15 18:04 ` Srinivas Kandagatla [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=256371b1-82aa-4fe4-b767-4025395082fd@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=andy.gross@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=georgi.djakov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=mturquette@baylibre.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).