public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Nikita Kiryanov <nikita@compulab.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 5/7] cm-t35: add support for dvi displays
Date: Tue, 29 Jan 2013 17:04:55 +0200	[thread overview]
Message-ID: <5107E517.20106@compulab.co.il> (raw)
In-Reply-To: <20130129140013.3496E2A08AC@gemini.denx.de>

Hi Wolfgang Denk,

On 01/29/2013 04:00 PM, Wolfgang Denk wrote:
> Dear Nikita Kiryanov,
>
> In message <1359463349-11649-6-git-send-email-nikita@compulab.co.il> you wrote:
>> Add support for dvi displays with user selectable dvi presets.
> ...
>> --- a/board/cm_t35/cm_t35.c
>> +++ b/board/cm_t35/cm_t35.c
>> @@ -216,6 +216,9 @@ static void cm_t3x_set_common_muxconf(void)
>>   	/* SB-T35 Ethernet */
>>   	MUX_VAL(CP(GPMC_NCS4),		(IEN  | PTU | EN  | M0)); /*GPMC_nCS4*/
>>
>> +	/* DVI enable */
>> +	MUX_VAL(CP(GPMC_NCS3),		(IDIS  | PTU | DIS  | M4));/*GPMC_nCS3*/
>
> Is it intentional and correct to always enable DVI, even when this is
> not configured by the user?

This simply prepares the mux that makes it possible to enable DVI.
The actual enabling of DVI is indeed conditional on user setup.

>
>
>> +/*
>> + * The frame buffer is allocated before we have the chance to parse user input.
>
> This seems broken to me.

Agreed.

>
> Please explain why you think so?

This isn't just my impression. A patch was submitted by Stephen Warren
to address this issue (http://patchwork.ozlabs.org/patch/212378/), but
it isn't in mainline yet.

>
>> + * vl_{col | row} to the maximal resolution supported by OMAP3.
>> + */
>> +vidinfo_t panel_info = {
>> +	.vl_col  = 1400,
>> +	.vl_row  = 1050,
>> +	.vl_bpix = LCD_BPP,
>> +	.cmap = (ushort *)0x80100000,
>
> Can we please avoid such hard coded magic numbers?

OK.

>
>
>> +/*
>> + * env_parse_displaytype() - parse display type.
>> + *
>> + * Parses the environment variable "displaytype", which contains the
>> + * name of the display type or preset, in which case it applies its
>> + * configurations.
>
> So we have yet another custom implementation for setting the display
> type?  Can we please agree on using common standard methods?  thanks.

Most of what is custom in this patchset is parsing of environment
variables. For actually setting up the DSS I do use common code
(specifically omap3_dss_panel_config() and related structs/defines).

>
>
> Best regards,
>
> Wolfgang Denk
>


-- 
Regards,
Nikita.

  reply	other threads:[~2013-01-29 15:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 12:42 [U-Boot] [PATCH V2 0/7] Add splash screen for CM-T35 Nikita Kiryanov
2013-01-29 12:42 ` [U-Boot] [PATCH V1 1/7] omap3: add useful dss defines Nikita Kiryanov
2013-01-29 13:55   ` Wolfgang Denk
2013-01-29 14:11     ` Nikita Kiryanov
2013-01-29 12:42 ` [U-Boot] [PATCH V2 2/7] omap3: allow dynamic selection of gfx_format Nikita Kiryanov
2013-01-29 13:52   ` Wolfgang Denk
2013-01-29 14:22     ` Nikita Kiryanov
2013-01-29 12:42 ` [U-Boot] [PATCH V2 3/7] lcd: prevent unaligned memory access when displaying splash screen Nikita Kiryanov
2013-01-29 13:46   ` Wolfgang Denk
2013-01-29 14:34     ` Nikita Kiryanov
2013-01-29 12:42 ` [U-Boot] [PATCH V1 4/7] lcd: add option for board specific splash screen preparation Nikita Kiryanov
2013-01-29 13:46   ` Wolfgang Denk
2013-01-29 14:44     ` Nikita Kiryanov
2013-01-29 12:42 ` [U-Boot] [PATCH V2 5/7] cm-t35: add support for dvi displays Nikita Kiryanov
2013-01-29 14:00   ` Wolfgang Denk
2013-01-29 15:04     ` Nikita Kiryanov [this message]
2013-01-29 12:42 ` [U-Boot] [PATCH V2 6/7] cm-t35: add support for user defined lcd parameters Nikita Kiryanov
2013-01-29 13:48   ` Wolfgang Denk
2013-01-30  8:00     ` Nikita Kiryanov
2013-01-29 12:42 ` [U-Boot] [PATCH V2 7/7] cm-t35: add support for loading splash image from NAND Nikita Kiryanov
2013-01-29 13:50   ` Wolfgang Denk
2013-01-30  8:08     ` Nikita Kiryanov

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=5107E517.20106@compulab.co.il \
    --to=nikita@compulab.co.il \
    --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