All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Georgi Djakov <georgi.djakov@linaro.org>
Cc: mturquette@linaro.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2] clk: qcom: Add MSM8916 Global Clock Controller support
Date: Fri, 06 Mar 2015 14:12:58 -0800	[thread overview]
Message-ID: <54FA266A.2020502@codeaurora.org> (raw)
In-Reply-To: <20150305195838.GA11174@codeaurora.org>

On 03/05/15 11:58, Stephen Boyd wrote:
>
> I guess this is ok, but it makes me uneasy. We don't do any bimc
> PLL voting downstream because this PLL is completely under the
> control of the RPM. For all we know, the RPM hasn't configured
> the PLL to be in FSM voting mode so this may not even work.
> Furthermore, if we have clk_pll_ops then we'll go and try to
> turn off the PLL when the last software entity on the kernel side
> is done using it. Unfortunately, this PLL may be used by
> something else that the RPM is managing and so turning it off is
> going to break things.
>
> We mostly need this here to get the right rate for the bus clocks
> (which are usually constantly changing rate anyway so modeling it
> in the kernel is ok but not perfect). The best solution is
> probably to add some read-only PLL ops (clk_pll_ro_ops?) that we
> can put on the bimc_pll and drop the voting thing completely. The
> read-only ops would just detect the rate of the PLL and not
> support anything else.

Ah I looked back at the code and I think it may work out to leave the
PLL voting as is. If the RPM has configured it for voting, then our PLL
ops will bail out early in the enable/disable path. And voting isn't
going to hurt anything so that part should be alright. I hope that the
RPM is actually putting it in voting mode though and not leaving it
under their direct control. That shouldn't be happening but it'd be
worth a check.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2015-03-06 22:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-25 16:44 [PATCH v2] clk: qcom: Add MSM8916 Global Clock Controller support Georgi Djakov
2015-03-04 10:53 ` Archit Taneja
2015-03-05 19:58 ` Stephen Boyd
2015-03-06 22:12   ` Stephen Boyd [this message]
2015-03-09 17:26   ` Georgi Djakov

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=54FA266A.2020502@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=georgi.djakov@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@linaro.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 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.