From: Cyril Chemparathy <cyril@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v5 2/3] ARM1176: TI: TNETV107X soc initial support
Date: Sun, 02 May 2010 18:56:44 -0400 [thread overview]
Message-ID: <4BDE032C.8080009@ti.com> (raw)
In-Reply-To: <4BD6F6B8.3090503@bumblecow.com>
Hi Tom,
Thanks for the excellent review.
[...]
>> +static struct async_emif_config default_async_emif_config[NUM_CS] = {
>> + { /* CS0 */
>> + .mode = ASYNC_EMIF_MODE_NAND,
>> + .select_strobe = ASYNC_EMIF_CS0_SELECT_STROBE,
>> + .extend_wait = ASYNC_EMIF_CS0_EXTEND_WAIT,
>> + .wr_setup = ASYNC_EMIF_CS0_WR_SETUP,
>> + .wr_strobe = ASYNC_EMIF_CS0_WR_STROBE,
>> + .wr_hold = ASYNC_EMIF_CS0_WR_HOLD,
>> + .rd_setup = ASYNC_EMIF_CS0_RD_SETUP,
>> + .rd_strobe = ASYNC_EMIF_CS0_RD_STROBE,
>> + .rd_hold = ASYNC_EMIF_CS0_RD_HOLD,
>> + .turn_around = ASYNC_EMIF_CS0_TURN_AROUND,
>> + .width = ASYNC_EMIF_CS0_WIDTH,
>> + },
[...]
> A better place for all the preceding code would be in an arch *.h
> The NUM_CS should likely be a CONFIG_ paramter.
I have moved this over to board code instead, since the board should
determine these based on the connected device's timings.
[...]
>> +static const struct pll_init_data plls[] = {
>> + [SYS_PLL] = {
>> + .config_enable = CONFIG_PLL_SYS_CONFIG,
>> + .pll = SYS_PLL,
>> + .internal_osc = CONFIG_PLL_SYS_INT_OSC,
>> + .external_freq = CONFIG_PLL_SYS_EXT_FREQ,
>> +#if (CONFIG_PLL_SYS_CONFIG)
>> + .pll_freq = CONFIG_PLL_SYS_PLL_FREQ,
>> + .div_freq = {
>> + CONFIG_PLL_SYS_ARM1176_CLK,
>> + CONFIG_PLL_SYS_DSP_CLK,
>> + CONFIG_PLL_SYS_DDR_CLK,
>> + CONFIG_PLL_SYS_FULL_CLK,
>> + CONFIG_PLL_SYS_LCD_CLK,
>> + CONFIG_PLL_SYS_VLYNQ_REF_CLK,
>> + CONFIG_PLL_SYS_TSC_CLK,
>> + CONFIG_PLL_SYS_HALF_CLK,
>> + },
>> +#endif
>> + },
[...]
> Similar to above, the preceeding code is better placed in an arch *.h
> Please move.
Again, moved these initializations to board code instead. Some boards
may opt to run at different rates.
[...]
>> +static const struct pin_config pin_table[] = {
>> + TNETV107X_MUX_CFG(0, 0, MUX_MODE_1),
>> + TNETV107X_MUX_CFG(0, 0, MUX_MODE_2),
>
> Change these immedates '0, 0' into #defines
> Apply globally
These are register indices and bit shifts, not really amenable to macro
definition. I have put in a comment for the column contents.
Regards
Cyril.
prev parent reply other threads:[~2010-05-02 22:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 14:29 [U-Boot] [PATCH v5 0/3] TI: tnetv107x patch series Cyril Chemparathy
2010-04-19 14:29 ` [U-Boot] [PATCH v5 1/3] ARM1176: Coexist with other ARM1176 platforms Cyril Chemparathy
2010-04-19 14:29 ` [U-Boot] [PATCH v5 2/3] ARM1176: TI: TNETV107X soc initial support Cyril Chemparathy
2010-04-19 14:29 ` [U-Boot] [PATCH v5 3/3] TI: TNETV107X EVM " Cyril Chemparathy
2010-04-27 14:39 ` Tom Rix
2010-04-27 14:37 ` [U-Boot] [PATCH v5 2/3] ARM1176: TI: TNETV107X soc " Tom Rix
2010-05-02 22:56 ` Cyril Chemparathy [this message]
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=4BDE032C.8080009@ti.com \
--to=cyril@ti.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