public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Cousson, Benoit" <b-cousson@ti.com>
Cc: "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	Santosh Shilimkar <santosh.shilimkar@ti.com>
Subject: Re: [PATCH 2/3] ARM: OMAP: Move omap2_init_common_devices out of init_early
Date: Wed, 24 Aug 2011 05:20:50 -0700	[thread overview]
Message-ID: <20110824122049.GA2963@atomide.com> (raw)
In-Reply-To: <4E54EA5E.8010603@ti.com>

* Cousson, Benoit <b-cousson@ti.com> [110824 04:38]:
> Hi Tony,
> 
> On 8/24/2011 1:54 PM, Tony Lindgren wrote:
> >There's no need to call omap2_init_common_devices from init_early.
> >It reprograms the memory timings for some boards, so it's better to
> >do it later so we have a chance to get console messages if something
> >goes wrong.
> 
> BTW, I did some comment on that function in my OMAP4 device-tree
> series, because the name is misleading.
> That function is just initializing the SDRC controller present in
> OMAP2 & 3. OMAP4 platform should not even call it.
> In fact, I'm now wondering were the OMAP4 EMIF is configured?

Probably nowhere currently?
 
> void __init omap2_init_common_devices(struct omap_sdrc_params *sdrc_cs0,
>                                       struct omap_sdrc_params *sdrc_cs1)
> {
>         if (cpu_is_omap24xx() || omap3_has_sdrc()) {
>                 omap2_sdrc_init(sdrc_cs0, sdrc_cs1);
>                 _omap2_init_reprogram_sdrc();
>         }
> }
> 
> I guess it used to do much more than that in the past.
> 
> Shouldn't we rename it to clarify its purpose?

Yeah we might as well rename it to omap_init_sdrc since we're
patching it. Will post an updated patch.

Tony

  parent reply	other threads:[~2011-08-24 12:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24 11:54 [PATCH 0/3] omap cleanup for makefile and init_early Tony Lindgren
2011-08-24 11:54 ` [PATCH 1/3] omap2+: Use Kconfig symbol in Makefile instead of obj-y Tony Lindgren
2011-08-24 11:54 ` [PATCH 2/3] ARM: OMAP: Move omap2_init_common_devices out of init_early Tony Lindgren
2011-08-24 12:11   ` Cousson, Benoit
2011-08-24 12:18     ` Santosh
2011-08-24 12:20     ` Tony Lindgren [this message]
2011-08-24 13:32       ` Tony Lindgren
2011-08-24 11:54 ` [PATCH 3/3] ARM: OMAP: Introduce SoC specific early_init Tony Lindgren
2011-08-24 12:48   ` Igor Grinberg
2011-08-24 13:35     ` Tony Lindgren

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=20110824122049.GA2963@atomide.com \
    --to=tony@atomide.com \
    --cc=b-cousson@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=santosh.shilimkar@ti.com \
    /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