linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP2: use early init hook
Date: Mon, 24 Jan 2011 12:19:52 -0800	[thread overview]
Message-ID: <20110124201952.GD13589@atomide.com> (raw)
In-Reply-To: <20110123171344.GH30094@n2100.arm.linux.org.uk>

* Russell King - ARM Linux <linux@arm.linux.org.uk> [110123 09:12]:
> Move non-mapping and non-irq initialization code out of .map_io and
> .init_irq respectively into the new init_early hook.

Nice :)
 
> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
> ---
> I think I've updated this patch correctly for the new platforms merged
> into mainline.
> 
> Please ensure that new platforms merged after this patch also use the
> new structure, and note that the initializers should be listed in the
> following order:
> 
> 	.fixup
> 	.reserve
> 	.map_io
> 	.init_early
> 	.init_irq
> 	.timer
> 	.init_machine
> 
> This is the order in which they are called, so it helps to make sense
> when reading the board level code if they're arranged in called order.

OK, will do.

Will also add this also into omap-testing. Any other issues that
might remain should be easy to fix.

Acked-by: Tony Lindgren <tony@atomide.com>

  parent reply	other threads:[~2011-01-24 20:19 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-23 17:13 [PATCH] ARM: OMAP2: use early init hook Russell King - ARM Linux
2011-01-23 17:48 ` Russell King - ARM Linux
2011-01-24 20:17   ` Tony Lindgren
2011-01-24 20:26     ` Tony Lindgren
2011-01-24 21:52       ` Russell King - ARM Linux
2011-01-25  2:21         ` Tony Lindgren
2011-01-25  2:24           ` [PATCH] omap2+: Make omap_hwmod_late_init into core_initcall Tony Lindgren
2011-01-25  2:25           ` [PATCH] omap2+: Fix omap_serial_early_init to work with init_early hook Tony Lindgren
2011-01-27 18:01             ` Kevin Hilman
2011-01-25 19:27           ` [PATCH] omap: hwmod: Populate _mpu_rt_va later on in omap_hwmod_late_init Tony Lindgren
2011-01-25 19:29           ` [PATCH] ARM: OMAP2: use early init hook Tony Lindgren
2011-01-25 15:46     ` Poddar, Sourav
2011-01-25 19:28       ` Tony Lindgren
2011-01-26 10:16         ` Poddar, Sourav
2011-02-14 23:45     ` Tony Lindgren
2011-02-14 23:52       ` [PATCH] omap: Move omap2_check_revision and omap_sram_init out of map_io Tony Lindgren
2011-02-15  1:53         ` Tony Lindgren
2011-02-16 17:20           ` Tony Lindgren
2011-01-24 20:19 ` Tony Lindgren [this message]
2011-01-26  8:46 ` [PATCH] ARM: OMAP2: use early init hook Uwe Kleine-König
2011-01-26  8:52   ` Russell King - ARM Linux
2011-01-26  9:11     ` Uwe Kleine-König
2011-01-26 10:31       ` Russell King - ARM Linux
2011-02-07 15:35         ` [PATCH 1/4] ARM: imx: use .init_early to initialize cpu type and reset address Uwe Kleine-König
2011-02-07 15:35         ` [PATCH 2/4] ARM: mx3: use .init_early to initialize cpu type, reset address and iomuxer Uwe Kleine-König
2011-02-07 15:35         ` [PATCH 3/4] ARM: mx5: " Uwe Kleine-König
2011-02-07 15:35         ` [PATCH 4/4] ARM: mxc91231: use .init_early to initialize cpu type Uwe Kleine-König

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=20110124201952.GD13589@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).