From: Jeffrey Hugo <jhugo@codeaurora.org>
To: Marc Gonzalez <marc.w.gonzalez@free.fr>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Nicolas Dechesne <nicolas.dechesne@linaro.org>,
Niklas Cassel <niklas.cassel@linaro.org>,
Andy Gross <andy.gross@linaro.org>
Cc: MSM <linux-arm-msm@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: WIP: UFS on apq8098
Date: Tue, 4 Dec 2018 10:31:54 -0700 [thread overview]
Message-ID: <7a7ccedd-c6b2-6789-c76e-ad2ddcd53e2a@codeaurora.org> (raw)
In-Reply-To: <1dbb2f0b-0ad1-e622-a9c4-9ff7284dbee7@codeaurora.org>
On 12/4/2018 10:21 AM, Jeffrey Hugo wrote:
> On 12/4/2018 10:11 AM, Marc Gonzalez wrote:
>> On 04/12/2018 18:05, Jeffrey Hugo wrote:
>>
>>> mount -t debugfs none /sys/kernel/debug
>>
>> Doh!
>>
>> # cat /sys/kernel/debug/clk/clk_summary
>> enable prepare
>> protect duty
>> clock count count count
>> rate accuracy phase cycle
>> ---------------------------------------------------------------------------------------------
>>
>> gcc_usb_phy_cfg_ahb2phy_clk 0 0 0
>> 0 0 0 50000
>> gcc_usb3_phy_pipe_clk 0 0 0
>> 0 0 0 50000
>> gcc_usb30_sleep_clk 0 0 0
>> 0 0 0 50000
>> gcc_ufs_unipro_core_clk 0 0 0
>> 0 0 0 50000
>
> Yeah, this clock has no parent, and is one of the ones that is a delta
> from the downsteam per your logs.
From what I can tell from the documentation, this is sourced from
ufs_unipro_core_clk_src, which is inturn sourced from gpll0_out_main.
I'm guessing gcc-msm8998.c needs to be updated to reflect this. It
would also be good to check this against the downstream kernel.
Let me know if you want me to have a look at any other specific clocks.
--
Jeffrey Hugo
Qualcomm Datacenter Technologies as an affiliate of Qualcomm
Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-12-04 17:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 15:18 WIP: UFS on apq8098 Marc Gonzalez
2018-12-03 15:27 ` Jeffrey Hugo
2018-12-03 15:47 ` Jeffrey Hugo
2018-12-03 15:53 ` Marc Gonzalez
2018-12-03 16:03 ` Jeffrey Hugo
2018-12-03 16:13 ` Marc Gonzalez
2018-12-03 16:18 ` Jeffrey Hugo
2018-12-03 16:22 ` Marc Gonzalez
2018-12-03 16:09 ` Bjorn Andersson
2018-12-03 16:53 ` Marc Gonzalez
2018-12-04 15:23 ` Marc Gonzalez
2018-12-04 15:45 ` Jeffrey Hugo
2018-12-04 16:14 ` Jeffrey Hugo
2018-12-04 16:17 ` Marc Gonzalez
2018-12-04 16:35 ` Jeffrey Hugo
2018-12-04 17:03 ` Marc Gonzalez
2018-12-04 17:05 ` Jeffrey Hugo
2018-12-04 17:11 ` Marc Gonzalez
2018-12-04 17:21 ` Jeffrey Hugo
2018-12-04 17:31 ` Jeffrey Hugo [this message]
2018-12-06 16:15 ` Marc Gonzalez
2018-12-06 16:45 ` Evan Green
2018-12-07 8:57 ` Marc Gonzalez
2018-12-07 9:29 ` Marc Gonzalez
2018-12-07 12:10 ` Marc Gonzalez
2018-12-07 17:14 ` Evan Green
2018-12-12 17:34 ` Marc Gonzalez
2018-12-13 10:51 ` Marc Gonzalez
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=7a7ccedd-c6b2-6789-c76e-ad2ddcd53e2a@codeaurora.org \
--to=jhugo@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=marc.w.gonzalez@free.fr \
--cc=nicolas.dechesne@linaro.org \
--cc=niklas.cassel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox