From: Tony Lindgren <tony@atomide.com>
To: "Ghorai, Sukumar" <s-ghorai@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v5 1/5] omap gpmc: enable irq mode in gpmc
Date: Fri, 5 Nov 2010 14:12:39 -0700 [thread overview]
Message-ID: <20101105211238.GT9264@atomide.com> (raw)
In-Reply-To: <2A3DCF3DA181AD40BDE86A3150B27B6B0356AEEDE2@dbde02.ent.ti.com>
* Ghorai, Sukumar <s-ghorai@ti.com> [101028 07:02]:
> Tony,
>
> > -----Original Message-----
> > From: Ghorai, Sukumar
> > Sent: Wednesday, September 29, 2010 12:08 PM
> > To: 'Tony Lindgren'
> > Cc: linux-omap@vger.kernel.org; linux-mtd@lists.infradead.org; linux-arm-
> > kernel@lists.infradead.org
> > Subject: RE: [PATCH v5 1/5] omap gpmc: enable irq mode in gpmc
> >
> >
> [..snip..]
>
> > > > diff --git a/arch/arm/mach-omap2/board-3430sdp.c b/arch/arm/mach-
> > > omap2/board-3430sdp.c
> > > > index 67b95b5..549cd62 100644
> > > > --- a/arch/arm/mach-omap2/board-3430sdp.c
> > > > +++ b/arch/arm/mach-omap2/board-3430sdp.c
> > > > @@ -328,6 +328,7 @@ static void __init omap_3430sdp_init_irq(void)
> > > > omap3_pm_init_cpuidle(omap3_cpuidle_params_table);
> > > > omap2_init_common_hw(hyb18m512160af6_sdrc_params, NULL);
> > > > omap_init_irq();
> > > > + gpmc_init();
> > > > omap_gpio_init();
> > > > }
> > > ...
> > >
> > > You can avoid adding gpmc_init() by making it a subsys_initcall().
> > > Just make sure you return early from it with if (!cpu_class_is_omap2()).
> > [Ghorai] will do
> > >
> [Ghorai] I was trying this and no success, as nand_init() get called before subsys_initcall(gpmc_init);
>
> 126 MACHINE_START(OMAP_ZOOM3, "OMAP Zoom3 board")
> ..
> 130 .init_irq = omap_zoom_init_irq,
> 131 .init_machine = omap_zoom_init,
> ..
>
> Step-(n):
> kernel_init() -> customize_machine()
> -> omap_zoom_init() -> gpmc_nand_init() -> which call gpmc
> functions, that's crashing, as gpmc is not initialized.
>
> Step-(n+1):
> Followed by subsys_initcall(gpmc_init)
>
> So I will incorporate the other input and will re-submit.
> [..snip..]
I don't see why you could not make gpmc_nand_init happen later?
Also, some of these calls can be moved to omap2_init_common_hw()?
Tony
next prev parent reply other threads:[~2010-11-05 21:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 13:37 [PATCH v5 0/5] nand prefetch-irq support and ecc layout chanage Sukumar Ghorai
2010-09-27 13:37 ` [PATCH v5 1/5] omap gpmc: enable irq mode in gpmc Sukumar Ghorai
2010-09-28 22:27 ` Tony Lindgren
2010-09-29 6:37 ` Ghorai, Sukumar
2010-10-28 14:11 ` Ghorai, Sukumar
2010-11-05 21:12 ` Tony Lindgren [this message]
2010-11-16 14:32 ` Ghorai, Sukumar
2010-09-27 13:37 ` [PATCH v5 2/5] omap3: nand: prefetch in irq mode support Sukumar Ghorai
2010-09-28 22:29 ` Tony Lindgren
2010-09-29 6:02 ` Ghorai, Sukumar
2010-09-27 13:37 ` [PATCH v5 3/5] omap3: nand: configurable fifo threshold to gain the throughput Sukumar Ghorai
2010-09-27 13:37 ` [PATCH v5 4/5] omap: nand: ecc layout select from board file Sukumar Ghorai
2010-09-27 13:37 ` [PATCH v5 5/5] omap: nand: making ecc layout as compatible with romcode ecc Sukumar Ghorai
2010-09-27 13:58 ` Premi, Sanjeev
2010-09-27 14:02 ` Ghorai, Sukumar
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=20101105211238.GT9264@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=s-ghorai@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;
as well as URLs for NNTP newsgroup(s).