From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: marzen-reference doesn't boot with CONFIG_PREEMPT
Date: Wed, 15 May 2013 11:30:26 +0000 [thread overview]
Message-ID: <1835543.BO2CSkQRhf@avalon> (raw)
In-Reply-To: <4961084.Cgj9yMUAgI@avalon>
Hi Simon,
On Wednesday 15 May 2013 12:47:16 Simon Horman wrote:
> On Wed, May 15, 2013 at 10:29:42AM +0900, Simon Horman wrote:
> > On Wed, May 15, 2013 at 03:05:18AM +0200, Laurent Pinchart wrote:
> > > On Wednesday 15 May 2013 09:23:59 Simon Horman wrote:
> > > > On Tue, May 14, 2013 at 09:08:07PM +0200, Laurent Pinchart wrote:
> > > > > But marzen does (renesas-next-20130513). Is that a known issue ?
> > > >
> > > > No, I was not aware of that.
> > > >
> > > > I would suspect, based on work on the kzm9g, that the problem
> > > > relates to driver initialisation order. In the case of kzm9g
> > > > my recollection is that the problem was resolved by initialising
> > > > clocksources earlier by changing their initcall level.
> > >
> > > Did that reach mainline ? I've tried booting kzm9g-reference with
> > > CONFIG_PREEMPT and have been unable to boot it as well with renesas-
> > > next-20130513. Maybe we should enable CONFIG_PREEMPT by default to catch
> > > similar issues in the future.
> >
> > It made it into 3.10-rc1 and has been in next for a while now.
> > So it seems that you have found a different problem.
> >
> > I'm ambivalent to setting CONFIG_PREEMPT by default.
>
> Hi Laurent,
>
> I have not been able to pin-point the cause of this problem nor come up with
> a fix. However, it does seem to be related to the early initialisation of
> devices and the following work around does allow booting marzen-reference
> with CONFIG_PREEMPT.
Thank you for the workaround. What prevents this patch (or a similar patch, as
it seems the SCIF and TMU devices would be instantiated twice) from being
applied to mainline ? Do we have a plan regarding what code we want to keep in
mach-shmobile and what we want to move to DT ?
> diff --git a/arch/arm/mach-shmobile/board-marzen-reference.c
> b/arch/arm/mach-shmobile/board-marzen-reference.c index f83b6d1..ac24cd7
> 100644
> --- a/arch/arm/mach-shmobile/board-marzen-reference.c
> +++ b/arch/arm/mach-shmobile/board-marzen-reference.c
> @@ -72,10 +72,11 @@ void __init marzen_init_irq(void)
> DT_MACHINE_START(MARZEN, "marzen")
> .smp = smp_ops(r8a7779_smp_ops),
> .map_io = r8a7779_map_io,
> - .init_early = r8a7779_init_delay,
> + .init_early = r8a7779_add_early_devices,
> .nr_irqs = NR_IRQS_LEGACY,
> .init_irq = marzen_init_irq,
> .init_machine = marzen_init,
> .init_time = shmobile_timer_init,
> .dt_compat = marzen_boards_compat_dt,
> + .init_time = r8a7779_earlytimer_init,
> MACHINE_END
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-05-15 11:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 19:08 marzen-reference doesn't boot with CONFIG_PREEMPT Laurent Pinchart
2013-05-15 0:23 ` Simon Horman
2013-05-15 1:05 ` Laurent Pinchart
2013-05-15 1:29 ` Simon Horman
2013-05-15 3:47 ` Simon Horman
2013-05-15 11:30 ` Laurent Pinchart [this message]
2013-05-16 1:05 ` Simon Horman
2013-05-16 3:47 ` Simon Horman
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=1835543.BO2CSkQRhf@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-sh@vger.kernel.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).