SUPERH platform development
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v2 5/8] ARM: shmobile: add sh73a0-specific timer initialisation to kzm9g-reference
Date: Wed, 13 Feb 2013 05:37:12 +0000	[thread overview]
Message-ID: <20130213053709.GA27103@verge.net.au> (raw)
In-Reply-To: <1360348712-29255-6-git-send-email-g.liakhovetski@gmx.de>

On Wed, Feb 13, 2013 at 02:04:43PM +0900, Magnus Damm wrote:
> Hi Simon,
> 
> On Wed, Feb 13, 2013 at 1:41 PM, Simon Horman <horms@verge.net.au> wrote:
> > On Wed, Feb 13, 2013 at 01:15:59PM +0900, Magnus Damm wrote:
> >> Hi Simon,
> >>
> >> On Wed, Feb 13, 2013 at 12:46 PM, Simon Horman <horms@verge.net.au> wrote:
> >> > On Fri, Feb 08, 2013 at 07:38:29PM +0100, Guennadi Liakhovetski wrote:
> >> >> This patch fixes failing boot of the kzm9g-reference kernel.
> >> >
> >> > Magnus specifically asked for the DT reference code not to use
> >> > early timers.
> >> >
> >> > As you have no doubt observed the current code doesn't work with SMP.
> >> > I have not been able to find a solution that does work with CONFIG_SMP
> >> > enabled without using early timers. I would welcome some ideas
> >> > on how to resolve this problem without using early timers.
> >>
> >> I have now tracked down and submitted a fix for the KZM9D regression
> >> you pointed me to earlier.
> >>
> >> Next step is to figure out what is wrong with KZM9G in DT-only mode.
> >> Can you guide me to reproduce off-list?
> >
> > I'd prefer to guide you on list so the knowledge is archived.
> 
> Ok, thanks, that's fine too of course.
> 
> > 1. Obtain the reference code.
> >
> >    I suggest the boards-kzm9g-reference branch of the renesas tree.
> >
> > 2. Configure
> >
> >    ARCH=arm make kzm9g_defconfig
> >
> >    Also, enable CONFIG_MACH_KZM9G_REFERENCE and CONFIG_ARM_APPENDED_DTB
> >
> >    N.B: CONFIG_ARM_APPENDED_DTB will be enabled by default in 3.8
> >
> > 3. Compile
> >
> > 4. Append arch/arm/boot/dts/sh73a0-kzm9g-reference.dtb to zImage and
> >    refresh uImage
> >
> > 4. Boot, you should see the boot halt at:
> >
> >    ...
> >    NR_IRQS:16 nr_irqs:16 16
> >    sched_clock: 32 bits at 128 Hz, resolution 7812500ns, wraps every 3489660920ms
> >    Console: colour dummy device 80x30
> >    console [tty0] enabled
> >    Calibrating delay loop (skipped) preset value.. 2287.41 BogoMIPS (lpj‰36512)
> >    pid_max: default: 32768 minimum: 301
> >    Mount-cache hash table entries: 512
> >    CPU: Testing write buffer coherency: ok
> >    CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
> >    Setting up static identity map for 0x4132aaf8 - 0x4132ab50
> 
> I assume someone has already tested the obvious things like booting
> with maxcpus=1 and checking if disabling TWD helps.

Yes.

  parent reply	other threads:[~2013-02-13  5:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-08 18:38 [PATCH v2 5/8] ARM: shmobile: add sh73a0-specific timer initialisation to kzm9g-reference Guennadi Liakhovetski
2013-02-13  3:46 ` Simon Horman
2013-02-13  4:15 ` Magnus Damm
2013-02-13  4:41 ` Simon Horman
2013-02-13  5:04 ` Magnus Damm
2013-02-13  5:37 ` Simon Horman [this message]
2013-02-13 10:08 ` Guennadi Liakhovetski
2013-02-13 11:00 ` Simon Horman
2013-02-13 14:22 ` Magnus Damm
2013-02-18  5:44 ` Magnus Damm
2013-02-18  6:51 ` 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=20130213053709.GA27103@verge.net.au \
    --to=horms@verge.net.au \
    --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