From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] i.MX25: Prepare for LCD driver in board adaptation
Date: Thu, 26 Apr 2012 11:57:04 +0200 [thread overview]
Message-ID: <20120426115704.3acbc345@wker> (raw)
In-Reply-To: <1334919709-5870-1-git-send-email-timo@exertus.fi>
Hi Timo,
sorry for my late reply.
On Fri, 20 Apr 2012 14:01:48 +0300
"Timo Ketola" <timo@exertus.fi> wrote:
> Dear Stefano, Anatolij, Scott,
>
> On 18.04.2012 13:47, Stefano Babic wrote:
> > On 18/04/2012 10:54, Timo Ketola wrote:
> >> Signed-off-by: Timo Ketola <timo@exertus.fi>
> ...
> >> diff --git a/drivers/video/mx2fb.c b/drivers/video/mx2fb.c
> >> new file mode 100644
> >> index 0000000..9ee4a3e
> >
> > IMHO it is better if you use the video API instead of the old LCD
> > interface, that means using CONFIG_VIDEO. You have then to implement a
> > video_hw_init() function for your initialisation. I think there are
> > advantages doing that, and recently some drivers moved to this API, for
> > example the driver for i.MX3 (mx3fb.c).
>
> I agree on that but unfortunately I'm short on time. What if I
> implement the driver in my board folder instead? I suppose there is not
> too much interest to get generic LCD support for i.MX2 because it is
> not yet there and architecture is a little oldish.
I would prefer not including the driver in the board code. The
disadvantage of using the video API is increased code size. If you
do not need the framebuffer console, then using the LCD interface
is okay.
> There should still be register definitions in the imx-regs.h like I
> propose in this patch. Or should I keep them too in my board folder?
No, better keep them in imx-regs.h.
If you are going to update and resubmit your mx2fb patch, then please
base your work on the u-boot-samsung tree [1] as there are another lcd
driver changes in this tree. Or wait until samsung tree will be merged
and then rebase your work on top of u-boot tree.
Thanks,
Anatolij
[1] http://git.denx.de/?p=u-boot/u-boot-samsung.git;a=summary
next prev parent reply other threads:[~2012-04-26 9:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 8:54 [U-Boot] [PATCH 0/1] i.MX2: Support splash screen Timo Ketola
2012-04-18 8:54 ` [U-Boot] [PATCH] " Timo Ketola
2012-04-18 9:26 ` Wolfgang Denk
2012-04-18 10:47 ` Stefano Babic
2012-04-20 11:01 ` [U-Boot] [PATCH] i.MX25: Prepare for LCD driver in board adaptation Timo Ketola
2012-04-20 11:01 ` [U-Boot] [PATCH] i.MX25: lcdc: Add register definitions Timo Ketola
2012-04-26 11:53 ` Anatolij Gustschin
2012-04-26 9:57 ` Anatolij Gustschin [this message]
2012-04-26 11:18 ` [U-Boot] [PATCH] i.MX25: Prepare for LCD driver in board adaptation Timo Ketola
2012-04-26 12:01 ` Anatolij Gustschin
2012-04-26 11:51 ` [U-Boot] [PATCH] i.MX2: Support splash screen Anatolij Gustschin
2012-04-26 14:37 ` Timo Ketola
2012-04-26 15:30 ` Anatolij Gustschin
2012-04-18 9:26 ` [U-Boot] [PATCH 0/1] " Wolfgang Denk
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=20120426115704.3acbc345@wker \
--to=agust@denx.de \
--cc=u-boot@lists.denx.de \
/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