From: Hector Palacios <hector.palacios@digi.com>
To: Fabio Estevam <fabio.estevam@freescale.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Marek Vasut <marex@denx.de>,
"shawn.guo@linaro.org" <shawn.guo@linaro.org>,
"festevam@gmail.com" <festevam@gmail.com>
Subject: Re: mxsfb on i.MX28 uses bypassed ref_xtal 24MHz clock for LCD
Date: Mon, 20 May 2013 16:59:41 +0200 [thread overview]
Message-ID: <519A3A5D.6090703@digi.com> (raw)
In-Reply-To: <519639A5.9070807@freescale.com>
Dear Fabio,
On 05/17/2013 04:07 PM, Fabio Estevam wrote:
> On 05/17/2013 10:57 AM, Hector Palacios wrote:
>
>> On the MX28EVK board with the Seiko 4.3" LCD, I do not see the penguin
>> or any image in v3.8 or v3.9 though the framebuffer device is present
>> and correctly loaded and backlight on.
>> This LCD works in kernel v2.6.35 with the same 24MHz frequency.
>> @Fabio, does this LCD work out of the box on v3.9? Am I missing something?
>
> Yes, works fine here.
>
> Make sure you update both the kernel and dtb files on your tests.
Agh. Now it works on the EVK. I had something wrong with the backlight (maybe a bad DTB).
Do you have any comment on the fact that the lcdif clock is bypassed to the 24MHz ref
clock? Doesn't this make useless the definition of pixelclk for the different displays
in mach-mxs.c?
You can only obtain whole divisors of this frequency (24, 12, 6, 4), which may not be
accurate enough to fit some displays.
Regards,
--
Héctor Palacios
next prev parent reply other threads:[~2013-05-20 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 13:57 mxsfb on i.MX28 uses bypassed ref_xtal 24MHz clock for LCD Hector Palacios
2013-05-17 14:07 ` Fabio Estevam
2013-05-20 14:59 ` Hector Palacios [this message]
2013-05-20 15:11 ` Fabio Estevam
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=519A3A5D.6090703@digi.com \
--to=hector.palacios@digi.com \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=shawn.guo@linaro.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