From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] temporarily disable rk3288-smp
Date: Thu, 4 Dec 2014 23:35:30 -0800 [thread overview]
Message-ID: <20141205073530.GG29274@quad.lixom.net> (raw)
In-Reply-To: <201411281237.01480.arnd@arndb.de>
On Fri, Nov 28, 2014 at 12:37:01PM +0100, Arnd Bergmann wrote:
> On Saturday 22 November 2014, Heiko St?bner wrote:
> > it looks like not all bootloaders like the recently introduced
> > rk3288-smp-support. Uninitialized CNTVOFF registers of the
> > architected timer produce rcu stalls on some boards.
> >
> > Both Olof and Kevin were affected by this. On Kevin's board
> > we could simply upgrade u-boot to a version behaving correctly
> > while Olof's board uses coreboot where no fix for this exists
> > currently. Also as far as I know Olof's board is the only one
> > in circulation using coreboot, but it would still be nice to keep
> > the boot tests working for the time being.
> >
> > There exist an alternative approach for solving issues like this
> > consisting of
> > - clocksource: arch_timer: Fix code to use physical timers when requested [0]
> > - clocksource: arch_timer: Allow the device tree to specify uninitialized timer registers [1]
> >
> >
> > So to keep Olof's boottests working, disable the rk3288-smp until this
> > gets sorted. Interested parties with a working bootloader can of course
> > always simply re-insert the enable-method to have working smp.
> >
>
> Pulled into next/dt, thanks!
And I've just now reverted the disablement patch since I picked up those two
dependencies. Thanks, all.
-Olof
prev parent reply other threads:[~2014-12-05 7:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-22 21:08 [GIT PULL] temporarily disable rk3288-smp Heiko Stübner
2014-11-28 11:37 ` Arnd Bergmann
2014-12-05 7:35 ` Olof Johansson [this message]
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=20141205073530.GG29274@quad.lixom.net \
--to=olof@lixom.net \
--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