linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Rajendra Nayak <rnayak@codeaurora.org>,
	Mike Turquette <mturquette@baylibre.com>
Cc: linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
	linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2 3/5] clk: qcom: Add MSM8996 Global Clock Control (GCC) driver
Date: Thu, 7 Jan 2016 15:55:33 -0800	[thread overview]
Message-ID: <568EFAF5.50507@codeaurora.org> (raw)
In-Reply-To: <568DF4C4.2080504@codeaurora.org>

On 01/06/16 21:16, Rajendra Nayak wrote:
> Stephen,
>
> On 12/01/2015 07:01 AM, Stephen Boyd wrote:
>> Add support for the global clock controller found on MSM8996
>> based devices. This should allow most non-multimedia device
>> drivers to probe and control their clocks.
> On my 8096 board I see the following orphan clocks,
>
> /sys/kernel/debug/clk # cat clk_orphan_summary
>    clock                         enable_cnt  prepare_cnt        rate   accuracy   phase
> ---------------------------------------------------------------------------------------                                                                                                                        -
>  gcc_ufs_rx_symbol_1_clk                  0            0           0          0 0
>  gcc_ufs_rx_symbol_0_clk                  0            0           0          0 0
>  gcc_ufs_tx_symbol_0_clk                  0            0           0          0 0
>  gcc_pcie_2_pipe_clk                      0            0           0          0 0
>  gcc_pcie_1_pipe_clk                      0            0           0          0 0
>  gcc_pcie_0_pipe_clk                      0            0           0          0 0
>  gcc_usb3_phy_pipe_clk                    0            0           0          0 0
>
> I was looking at some ufs clocks which lead me to this. something that needs to be fixed?
>

Hmm yes. This was a "TODO" because the data says there are parents for
these clocks, but they don't seem to exist in the global clock
controller. Perhaps they come from the phys? If my suspicion is right,
then those phy drivers need to register the source clocks and give them
some rate so that these clocks here aren't orphans. In the downstream
code they mark these clocks as root clocks, which doesn't seem right,
but I suppose that also works given that we don't seem to care about
rates, just on/off. It just feels hacky, so I left them as orphans for now.

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


  reply	other threads:[~2016-01-07 23:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01  1:31 [PATCH v2 0/5] Add support for MSM8996 clock controllers Stephen Boyd
2015-12-01  1:31 ` [PATCH v2 1/5] clk: divider: Cap table divider values to 'width' member Stephen Boyd
2015-12-01  1:31 ` [PATCH v2 2/5] clk: qcom: Add Alpha PLL support Stephen Boyd
2015-12-01  1:31 ` [PATCH v2 3/5] clk: qcom: Add MSM8996 Global Clock Control (GCC) driver Stephen Boyd
2015-12-16 23:30   ` [v2,3/5] " Andy Gross
2015-12-24  0:17     ` Michael Turquette
2016-01-07  5:16   ` [PATCH v2 3/5] " Rajendra Nayak
2016-01-07 23:55     ` Stephen Boyd [this message]
2015-12-01  1:31 ` [PATCH v2 4/5] clk: qcom: Add gfx3d ping-pong PLL frequency switching Stephen Boyd
2015-12-01  1:31 ` [PATCH v2 5/5] clk: qcom: Add MSM8996 Multimedia Clock Controller (MMCC) driver Stephen Boyd
2015-12-01  2:31 ` [PATCH v2 0/5] Add support for MSM8996 clock controllers Stephen Boyd

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=568EFAF5.50507@codeaurora.org \
    --to=sboyd@codeaurora.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=rnayak@codeaurora.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).