From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Add inverted clock polarity support for Atmel LCD driver
Date: Sun, 19 Jul 2009 11:34:23 +0200 [thread overview]
Message-ID: <20090719093423.GC31924@game.jcrosoft.org> (raw)
In-Reply-To: <4A625C14.8020306@denx.de>
> This definition in struct vidinfo for Atmel LCD
> /* LCD configuration register */
> u_long vl_sync; /* Horizontal / vertical sync */
> u_long vl_bpix; /* Bits per pixel, 0 = 1, 1 = 2, 2 = 4, 3 = 8,
> 4 = 16 */
> u_long vl_tft; /* 0 = passive, 1 = TFT */
>
> is confusing. If these fields are supposed to contain flags
> for LCD configuration register LCDCON2 then we should define
> only one "u_long lcdcon2" field containing all the flags/fields
> for sync polarity, bpp, clock polarity, scan mode, display type,
> interface width, LCDD, LCDDEN polarities, LCDDOTCLK mode and memory
> ordering format. We are wasting tree u_longs here and are not even
> able to use half of the possible settings for LCDCON2 register.
> I would rather fix the struct vidinfo for Atmel LCD so that
> people could set needed flags in the board code, e.g.:
>
> vidinfo_t panel_info = {
> ...
> lcdcon2: ATMEL_LCDC_INVLINE_INVERTED |
> ATMEL_LCDC_INVFRAME_INVERTED |
> ATMEL_LCDC_INVCLK_INVERTED;
> ...
> }
I disagree here we must not make the panel_info atmel specific that way
we can add fields to pass atmel specific info which are pass via
struct atmel_lcdfb_info in Linux
But we need to be sync with linux as possible to simplify port and bugfix.
btw on Linux you do not specify it directly you specific this
FB_SYNC_HOR_HIGH_ACT => ATMEL_LCDC_INVLINE_INVERTED
FB_SYNC_VERT_HIGH_ACT => ATMEL_LCDC_INVFRAME_INVERTED
Best Regards,
J.
next prev parent reply other threads:[~2009-07-19 9:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 15:56 [U-Boot] [PATCH] Add inverted clock polarity support for Atmel LCD driver Dimitar Dimitrov
2009-07-15 15:58 ` [U-Boot] [PATCH 02/03 v3] Add support for Olimex SAM9-L9261 SBC Dimitar Dimitrov
2009-07-18 21:09 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-15 16:00 ` [U-Boot] [PATCH 03/03 v3] Add support for Olimex SAM9-L9260 SBC Dimitar Dimitrov
2009-07-18 21:13 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-18 19:18 ` [U-Boot] [PATCH] Add inverted clock polarity support for Atmel LCD driver Anatolij Gustschin
2009-07-25 20:28 ` Anatolij Gustschin
2009-07-18 20:58 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-18 23:34 ` Anatolij Gustschin
2009-07-19 9:34 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2009-11-22 21:01 ` Wolfgang Denk
2009-11-24 19:47 ` Dimitar Dimitrov
2009-12-05 0:10 ` 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=20090719093423.GC31924@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--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