U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/3] KW: Add kw_adjust_dram() weak function
Date: Tue, 26 Jun 2012 14:47:53 +0200	[thread overview]
Message-ID: <201206261447.53537.marex@denx.de> (raw)
In-Reply-To: <F766E4F80769BD478052FB6533FA745D1A2FDB39AD@SC-VEXCH4.marvell.com>

Dear Prafulla Wadaskar,

> > -----Original Message-----
> > From: Marek Vasut [mailto:marex at denx.de]
> > Sent: 26 June 2012 17:45
> > To: u-boot at lists.denx.de
> > Cc: Marek Vasut; Prafulla Wadaskar; Wolfgang Denk
> > Subject: [PATCH 2/3] KW: Add kw_adjust_dram() weak function
> > 
> > This function shall allow a board to adjust DRAM parameters in case
> > there are multiple versions of the board with different DRAM sizes.
> > 
> > Signed-off-by: Marek Vasut <marex@denx.de>
> > Cc: Prafulla Wadaskar <prafulla@marvell.com>
> > Cc: Wolfgang Denk <wd@denx.de>
> > ---
> > 
> >  arch/arm/cpu/arm926ejs/kirkwood/dram.c |   11 +++++++++++
> 
> Instead I would like to suggest to add function name as
> __kw_post_kwbconfig()

what about using board_early_init_f() ?

> This typically addresses to reconfigure the default configuration done by
> kwbimage.cfg, so the scope is not limited to DRAM configuration.
> 
> Regards..
> Prafulla . . .

Best regards,
Marek Vasut

  reply	other threads:[~2012-06-26 12:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-26 12:15 [U-Boot] [PATCH 1/3] KW: Move the memory register definitions into kirkwood.h Marek Vasut
2012-06-26 12:15 ` [U-Boot] [PATCH 2/3] KW: Add kw_adjust_dram() weak function Marek Vasut
2012-06-26 12:33   ` Prafulla Wadaskar
2012-06-26 12:47     ` Marek Vasut [this message]
2012-06-26 13:19       ` Prafulla Wadaskar
2012-06-26 12:15 ` [U-Boot] [PATCH 3/3] Kirkwood: Add support for Ka-Ro TK71 Marek Vasut
2012-06-26 12:30   ` Prafulla Wadaskar
2012-06-26 12:45     ` Marek Vasut
2012-06-26 13:48       ` Prafulla Wadaskar

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=201206261447.53537.marex@denx.de \
    --to=marex@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