From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Rajendra Nayak <rnayak@ti.com>
Cc: NeilBrown <neilb@suse.de>,
linux-omap <linux-omap@vger.kernel.org>,
Paul Walmsley <paul@pwsan.com>
Subject: Re: Strange OMAP3 LCD display regression - bisected.
Date: Mon, 3 Jun 2013 10:39:02 +0300 [thread overview]
Message-ID: <51AC4816.7050807@ti.com> (raw)
In-Reply-To: <51AC46D4.9020503@ti.com>
[-- Attachment #1: Type: text/plain, Size: 783 bytes --]
On 03/06/13 10:33, Rajendra Nayak wrote:
> Tomi,
>
>>
>> Odd, indeed. Without reverting the patch, the DSS uses a clock from the
>> PRCM as func clock and for pixel clock. As the common clock framework is
>> somehow involved in the breakage, maybe (pure guess) something related
>> to the PRCM clock is configured wrong.
>
> So whats the specific PRCM clock thats used here? I can go check if there is
> something different in the way its modeled with/without common clk.
I don't know which OMAP version we're talking about, but I guess it's
OMAP3xxx.
From the TRM, it's DPLL4_ALWON_FCLKOUTM4X2 for OMAP34xx and OMAP36xx.
Although that is a bit odd, as I think the x2 is only for OMAP34xx.
Maybe the clock name is wrong for OMAP36xx on my TRM...
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2013-06-03 7:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-02 6:50 Strange OMAP3 LCD display regression - bisected NeilBrown
2013-06-03 7:24 ` Tomi Valkeinen
2013-06-03 7:33 ` Rajendra Nayak
2013-06-03 7:39 ` Tomi Valkeinen [this message]
2013-06-03 8:57 ` NeilBrown
2013-06-03 9:24 ` Tomi Valkeinen
2013-06-03 7:40 ` Paul Walmsley
2013-06-03 8:13 ` jean-philippe francois
2013-06-03 11:20 ` NeilBrown
2013-06-03 12:16 ` Tomi Valkeinen
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=51AC4816.7050807@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=neilb@suse.de \
--cc=paul@pwsan.com \
--cc=rnayak@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