mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter De Schrijver <pdeschrijver@nvidia.com>
To: Stephen Boyd <sboyd@codeaurora.org>
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: Mon, 13 Oct 2014 11:23:22 +0300	[thread overview]
Message-ID: <20141013082322.GD32045@tbergstrom-lnx.Nvidia.com> (raw)
In-Reply-To: <20141011002056.GJ5493@codeaurora.org>

On Fri, Oct 10, 2014 at 05:20:56PM -0700, Stephen Boyd wrote:
> 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.

It can change at runtime.

Cheers,

Peter.

      reply	other threads:[~2014-10-13  8:23 UTC|newest]

Thread overview: 11+ 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 ` [PATCH v2 1/4] clk: Recalc rate and accuracy in underscore functions if not caching 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 ` [PATCH v2 3/4] clk: Use lockless functions for debug printing 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 10:11   ` kiran.padwal
     [not found]   ` <20140928024131.19023.40641@quantum>
2014-09-30  0:12     ` Stephen Boyd
2014-10-08  1:09       ` Stephen Boyd
     [not found]         ` <20141009025923.4379.66113@quantum>
2014-10-10  8:24           ` Peter De Schrijver
2014-10-11  0:20             ` Stephen Boyd
2014-10-13  8:23               ` Peter De Schrijver [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=20141013082322.GD32045@tbergstrom-lnx.Nvidia.com \
    --to=pdeschrijver@nvidia.com \
    --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=sachin.kamat@linaro.org \
    --cc=sboyd@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome