From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: "Murthy, Raghuveer" <raghuveer.murthy@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 0/3] OMAP: DSS2: Fix for DISPC core functional clock divider
Date: Thu, 3 Mar 2011 18:12:56 +0200 [thread overview]
Message-ID: <1299168776.2615.154.camel@deskari> (raw)
In-Reply-To: <1299166080-15380-1-git-send-email-raghuveer.murthy@ti.com>
On Thu, 2011-03-03 at 09:27 -0600, Murthy, Raghuveer wrote:
> OMAP4 has 2 LCD channels and corresponding DISPC_DIVISOR1 and DISPC_DIVISOR2
> registers to configure the pixel clock frequency, for the respective LCD
> displays.
>
> There is also DISPC_DIVISOR register, which by default has the ENABLE bit
> set to zero, for backward compatibility mode. Hence the logical clock divider of
> DISPC_DIVISOR1.LCD, gets used for core func clk configuration. The default value
> of DISPC_DIVISOR1.LCD is 4.
>
> If only the secondary LCD is enabled, at high pixel resolutions the core clk
> lags behind the pixel clock, causing stair-step effect (diagonal lines with
> tearing) on the display.
>
> Hence DISPC_DIVISOR.ENABLE is set to 1, and the core functional clock is set
> independently and exclusively in DISPC_DIVISOR.LCD.
>
> - Added the above as dss_features
Thanks, applied.
Tomi
prev parent reply other threads:[~2011-03-03 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 15:27 [PATCH v3 0/3] OMAP: DSS2: Fix for DISPC core functional clock divider Raghuveer Murthy
2011-03-03 15:27 ` [PATCH v3 1/3] OMAP: DSS2: Adding dss_features for independent core clk divider Raghuveer Murthy
2011-03-03 15:27 ` [PATCH v3 2/3] OMAP: DSS2: Renaming register macro DISPC_DIVISOR(ch) Raghuveer Murthy
2011-03-03 15:28 ` [PATCH v3 3/3] OMAP4: DSS2: Using dss_features to set independent core clock divider Raghuveer Murthy
2011-03-03 16:12 ` Tomi Valkeinen [this message]
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=1299168776.2615.154.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=raghuveer.murthy@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