From: Holger Schurig <holgerschurig@gmail.com>
To: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: i.MX6 frame buffer inside barebox?
Date: Wed, 18 Jun 2014 16:26:48 +0200 [thread overview]
Message-ID: <CAOpc7mFqu1ov94naTWtCiJMXxNk5RLa=mSL-eh3SwFXNoP1UGg@mail.gmail.com> (raw)
Hi, I'm a bit puzzled. I compiled my barebox with
CONFIG_CMD_SPLASH=y
CONFIG_VIDEO=y
CONFIG_DRIVER_VIDEO_IMX_IPUV3=y
CONFIG_DRIVER_VIDEO_IMX_IPUV3_LVDS=y
CONFIG_DRIVER_VIDEO_SIMPLEFB=y
and some entries in the device tree about it (see below). And when I
boot barebox, I see /dev/fb0.
However, the LVDS signals don't come out of the CPU, e.g. LVDS_CLK0_P
/ LVDS_CLK0_N is silent. Do I need something to enable the drive as
well? Simply writing to /dev/fb0, e.g. with the "splash" or "mw -d
/dev/fdb0" command, doesn't seem to do the magic.
As soon as I boot Linux, the LVDS signals come to live. That I cannot
yet see if it's correct because of an backlight issue is some entirely
different issue :-)
Also, what I noticed is that some clocks with "ipu" in their name are
on, others are off:
barebox:/ clk_dump
...
ipu1_sel (rate 528000000, enabled)
ipu1_podf (rate 264000000, enabled)
2400000.ipu_di0_pixel (rate 264000000, enabled)
2400000.ipu_di1_pixel (rate 264000000, enabled)
ipu2_sel (rate 528000000, enabled)
ipu2_podf (rate 264000000, enabled)
2800000.ipu_di0_pixel (rate 264000000, enabled)
2800000.ipu_di1_pixel (rate 264000000, enabled)
...
pll5_video (rate 288000000, disabled)
pll5_post_div (rate 72000000, disabled)
pll5_video_div (rate 72000000, disabled)
ldb_di0_sel (rate 72000000, disabled)
ldb_di0_div_3_5 (rate 20571428, disabled)
ldb_di0_podf (rate 10285714, disabled)
ldb_di1_sel (rate 72000000, disabled)
ldb_di1_div_3_5 (rate 20571428, disabled)
ldb_di1_podf (rate 10285714, disabled)
ipu1_di0_pre_sel (rate 72000000, disabled)
ipu1_di0_pre (rate 24000000, disabled)
ipu1_di0_sel (rate 24000000, disabled)
ipu1_di1_pre_sel (rate 72000000, disabled)
ipu1_di1_pre (rate 24000000, disabled)
ipu1_di1_sel (rate 24000000, disabled)
ipu2_di0_pre_sel (rate 72000000, disabled)
ipu2_di0_pre (rate 24000000, disabled)
ipu2_di0_sel (rate 24000000, disabled)
ipu2_di1_pre_sel (rate 72000000, disabled)
ipu2_di1_pre (rate 24000000, disabled)
ipu2_di1_sel (rate 24000000, disabled)
...
What part of barebox is responsible to enable the needed clocks?
&ldb {
status = "okay";
lvds-channel@0 {
status = "okay";
fsl,data-mapping = "spwg";
fsl,data-width = <18>;
display-timings {
timing0: 800x600 {
clock-frequency = <35338240>;
hactive = <800>;
vactive = <600>;
hfront-porch = <46>;
hback-porch = <100>;
hsync-len = <20>;
hsync-active = <1>;
vfront-porch = <12>;
vback-porch = <23>;
vsync-len = <10>;
vsync-active = <1>;
};
};
};
};
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2014-06-18 14:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 14:26 Holger Schurig [this message]
2014-06-18 19:58 ` Sascha Hauer
2014-06-23 7:25 ` Holger Schurig
2014-06-23 7:43 ` Sascha Hauer
2014-06-23 8:42 ` Holger Schurig
2014-06-23 10:03 ` Sascha Hauer
2014-06-23 16:57 ` Robert Schwebel
2014-06-25 13:46 ` Holger Schurig
2014-06-26 5:55 ` Sascha Hauer
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='CAOpc7mFqu1ov94naTWtCiJMXxNk5RLa=mSL-eh3SwFXNoP1UGg@mail.gmail.com' \
--to=holgerschurig@gmail.com \
--cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox