From: Gary Thomas <gary@mlbassoc.com>
To: Tomi Valkeinen <tomi.valkeinen@nokia.com>
Cc: OMAP Linux discussion <linux-omap@vger.kernel.org>
Subject: DSS2 clocking
Date: Wed, 21 Oct 2009 06:42:41 -0600 [thread overview]
Message-ID: <4ADF01C1.3020602@mlbassoc.com> (raw)
I'm using DSS2, currently just with a frame buffer to a
[VGA/RGB] monitor.
I'm trying to understand how to set the timing parameters
for my device. The simple 'omapfb.mode=1024x768-24@75'
doesn't quite cut it for some of the devices I need to
use.
Questions:
* How can I get different pixel clocks? I seem to always
end up with 61714285:
# cat /tmp/dbg/omapdss/clk
- dss -
internal clk count 2
dss_ick 83000000 1
dss1_alwon_fck 123428570 1
dss2_alwon_fck 13000000 0
dss_tv_fck 54000000 0
dss_96m_fck 96000000 0
- dispc -
dispc fclk source = dss1_alwon_fclk
pixel clk = 123428570 / 1 / 2 = 61714285
* How can I control the waveform? In particular, the
size and shape of the "porches"? My display seems to
need these settings:
61714,1024/26/162/136,768/3/29/6
I'd like to get this behaviour, either from the boot line
or ideally by default.
* The display also seems to want the sync pulses to be
asserted low (inverted?). Currently, I have this "hard-wired"
into my display device, but I'd also like this to be adjustable.
Thanks for any pointers, etc.
Note: I'm using Tomi's tree from roughly late July
http://www.bat.org/~tomba/git/linux-omap-dss.git
7ae220f46384b34e72b8c3b0c2075a674a3f74fe
Thanks for any pointers
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next reply other threads:[~2009-10-21 12:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 12:42 Gary Thomas [this message]
2009-10-22 8:29 ` DSS2 clocking 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=4ADF01C1.3020602@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@nokia.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