From: Stephen Boyd <sboyd@codeaurora.org>
To: Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: Mike Turquette <mturquette@linaro.org>,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, ccross@android.com,
Barry Song <baohua@kernel.org>,
Sachin Kamat <sachin.kamat@linaro.org>,
Viresh Kumar <viresh.linux@gmail.com>
Subject: Re: [PATCH v2 4/4] clk: Use ww_mutexes for clk_prepare_{lock/unlock}
Date: Fri, 10 Oct 2014 17:20:56 -0700 [thread overview]
Message-ID: <20141011002056.GJ5493@codeaurora.org> (raw)
In-Reply-To: <20141010082434.GF29637@tbergstrom-lnx.Nvidia.com>
On 10/10, Peter De Schrijver wrote:
> > > drivers/clk/tegra/clk-pll.c:732: unsigned long input_rate =
> > > clk_get_rate(clk_get_parent(hw->clk));
> > > drivers/clk/tegra/clk-pll.c:1288: unsigned long input_rate =
> > > clk_get_rate(clk_get_parent(hw->clk));
>
> This is not so easy to change unfortunately. I will have to think of a solution.
>
Thanks. Does the input parent rate change at runtime or is it
fixed at boot? I'm hoping we can call _get_table_rate() once
before we register the clock or something.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 4/4] clk: Use ww_mutexes for clk_prepare_{lock/unlock}
Date: Fri, 10 Oct 2014 17:20:56 -0700 [thread overview]
Message-ID: <20141011002056.GJ5493@codeaurora.org> (raw)
In-Reply-To: <20141010082434.GF29637@tbergstrom-lnx.Nvidia.com>
On 10/10, Peter De Schrijver wrote:
> > > drivers/clk/tegra/clk-pll.c:732: unsigned long input_rate =
> > > clk_get_rate(clk_get_parent(hw->clk));
> > > drivers/clk/tegra/clk-pll.c:1288: unsigned long input_rate =
> > > clk_get_rate(clk_get_parent(hw->clk));
>
> This is not so easy to change unfortunately. I will have to think of a solution.
>
Thanks. Does the input parent rate change at runtime or is it
fixed at boot? I'm hoping we can call _get_table_rate() once
before we register the clock or something.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2014-10-11 0:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 1:01 [PATCH v2 0/4] Use wound/wait mutexes in the common clock framework Stephen Boyd
2014-09-04 1:01 ` Stephen Boyd
2014-09-04 1:01 ` [PATCH v2 1/4] clk: Recalc rate and accuracy in underscore functions if not caching Stephen Boyd
2014-09-04 1:01 ` Stephen Boyd
2014-09-04 1:01 ` [PATCH v2 2/4] clk: Make __clk_lookup() use a list instead of tree search Stephen Boyd
2014-09-04 1:01 ` Stephen Boyd
2014-09-04 1:01 ` [PATCH v2 3/4] clk: Use lockless functions for debug printing Stephen Boyd
2014-09-04 1:01 ` Stephen Boyd
2014-09-04 1:01 ` [PATCH v2 4/4] clk: Use ww_mutexes for clk_prepare_{lock/unlock} Stephen Boyd
2014-09-04 1:01 ` Stephen Boyd
2014-09-04 10:11 ` kiran.padwal at smartplayin.com
2014-09-04 10:11 ` kiran.padwal
2014-09-28 2:41 ` Mike Turquette
2014-09-28 2:41 ` Mike Turquette
2014-09-30 0:12 ` Stephen Boyd
2014-09-30 0:12 ` Stephen Boyd
2014-10-08 1:09 ` Stephen Boyd
2014-10-08 1:09 ` Stephen Boyd
2014-10-09 2:59 ` Mike Turquette
2014-10-09 2:59 ` Mike Turquette
2014-10-10 8:24 ` Peter De Schrijver
2014-10-10 8:24 ` Peter De Schrijver
2014-10-10 8:24 ` Peter De Schrijver
2014-10-11 0:20 ` Stephen Boyd [this message]
2014-10-11 0:20 ` Stephen Boyd
2014-10-13 8:23 ` Peter De Schrijver
2014-10-13 8:23 ` Peter De Schrijver
2014-10-13 8:23 ` Peter De Schrijver
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=20141011002056.GJ5493@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=baohua@kernel.org \
--cc=ccross@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=pdeschrijver@nvidia.com \
--cc=sachin.kamat@linaro.org \
--cc=viresh.linux@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.