From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Tero Kristo <t-kristo@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
Paul Walmsley <paul@pwsan.com>,
Mike Turquette <mturquette@linaro.org>, Stefan Roese <sr@denx.de>
Subject: Re: Odd behavior with dpll4_m4x2_ck on omap3 + DT
Date: Wed, 28 Aug 2013 13:14:24 +0300 [thread overview]
Message-ID: <521DCD80.1060600@ti.com> (raw)
In-Reply-To: <521DC770.5050000@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]
On 28/08/13 12:48, Tero Kristo wrote:
> On 08/28/2013 12:22 PM, Tomi Valkeinen wrote:
>> Hi,
>>
>> I'm seeing odd clock behavior with Beagle, booting with DT. I'm using
>> v3.11-rc7 + DSS DT patches.
>
> I guess you are not using the clock DT patches? Just making sure I
> didn't break anything. :)
No, plain rc7 with my DSS DT patches.
>> So, for some reason, the first clk_set_rate goes wrong. Any ideas?
>
> Hmm, strange. I am not seeing similar behavior, but I am calling
> clk_set_rate in different location.... also I am using clock DT patches
> (don't try the current version though, as I am reworking them.)
>
> [ 0.000000] dpll4_ck: 432000000
> [ 0.000000] dpll4_m4_ck: 72000000
> [ 0.000000] dpll4_m4x2_ck: 144000000
> [ 0.000000] dss1_alwon_fck_3430es2: 144000000
> [ 0.000000] dpll4_ck: 432000000
> [ 0.000000] dpll4_m4_ck: 86400000
> [ 0.000000] dpll4_m4x2_ck: 172800000
> [ 0.000000] dss1_alwon_fck_3430es2: 172800000
>
> Do you see the error only when setting to some specific rate (86400000)
> or it doesn't matter?
I also tried setting to 72000000, with the same result.
Do you know if I can somehow easily get debug prints from the clock
framework, that could lighten up the issue?
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2013-08-28 10:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 9:22 Odd behavior with dpll4_m4x2_ck on omap3 + DT Tomi Valkeinen
2013-08-28 9:48 ` Tero Kristo
2013-08-28 10:14 ` Tomi Valkeinen [this message]
2013-08-28 11:40 ` Tero Kristo
2013-09-10 11:33 ` Stefan Roese
2013-09-10 12:12 ` Tero Kristo
2013-09-10 12:19 ` Tomi Valkeinen
2013-09-10 12:24 ` Tero Kristo
2013-09-10 12:40 ` Tomi Valkeinen
2013-09-10 13:17 ` Tero Kristo
2013-09-10 21:17 ` Mike Turquette
2013-09-10 21:57 ` Mike Turquette
2013-09-11 7:21 ` Tomi Valkeinen
2013-09-13 7:51 ` Stefan Roese
2013-09-13 11:34 ` Tero Kristo
2013-09-16 19:45 ` Mike Turquette
2013-09-27 8:41 ` Tomi Valkeinen
2013-09-27 11:24 ` Tero Kristo
2013-09-30 7:56 ` Tomi Valkeinen
2013-10-07 8:21 ` Paul Walmsley
2013-10-08 1:35 ` Mike Turquette
2013-10-13 20:17 ` Paul Walmsley
2013-09-10 12:25 ` Stefan Roese
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=521DCD80.1060600@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=paul@pwsan.com \
--cc=sr@denx.de \
--cc=t-kristo@ti.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;
as well as URLs for NNTP newsgroup(s).