From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: "ext Taneja, Archit" <archit@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: RE: [Query] OMAP: DSS2: Margin for downscaling in clock calculations
Date: Tue, 18 Jan 2011 16:19:29 +0200 [thread overview]
Message-ID: <1295360369.27310.18.camel@tubuntu> (raw)
In-Reply-To: <FCCFB4CDC6E5564B9182F639FC356087035F86FA74@dbde02.ent.ti.com>
On Tue, 2011-01-18 at 10:45 +0530, ext Taneja, Archit wrote:
> Hi,
>
> I was going through the DSS2 code which sets up the FCLK
> coming from PRCM and the DISPC divivors to get the required pixel
> clock.
>
> The function dss_calc_clock_div() does a brute force search across
> all possible values of: a) DPLL divisor whose output goes to DSS, b)
> DISPC_DIVISOR.LCD, c) DISPC_DIVISOR.pcd
>
> The combination which gives a clock frequency closest to the
> required pixel clock is chosen.
>
> Hence, it seems that the resultant DISPC_FCLK clock frequency doesn't
> take into account the extra margin needed for downscaling:
>
> Req dispc_fclk >= pck * hscale_ratio * vscale_ration * K
>
> Do you thing putting a further constraint (like DISPC_FCLK needs to be
> greater than a given value) should be a part of the calculations to
> ensure successful scaling?
It's been a while since I looked at the fclk requirements, but isn't the
current CONFIG_OMAP2_DSS_MIN_FCK_PER_PCK enough? It is quite hackish and
static, but a proper implementation is much harder (dynamically changing
the clocks depending on the scaling).
Or were there some additional restrictions?
Tomi
next prev parent reply other threads:[~2011-01-18 14:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 5:15 [Query] OMAP: DSS2: Margin for downscaling in clock calculations Taneja, Archit
2011-01-18 14:19 ` Tomi Valkeinen [this message]
2011-01-18 21:09 ` Taneja, Archit
2011-01-21 11:52 ` 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=1295360369.27310.18.camel@tubuntu \
--to=tomi.valkeinen@nokia.com \
--cc=archit@ti.com \
--cc=linux-omap@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.