From: swarren@wwwdotorg•org (Stephen Warren)
To: linux-arm-kernel@lists•infradead.org
Subject: [V2] arm: pj4: check cpu id for pj4 cp0 access
Date: Thu, 20 Mar 2014 13:04:05 -0600 [thread overview]
Message-ID: <532B3BA5.7080209@wwwdotorg.org> (raw)
In-Reply-To: <20140318201537.GA20942@beef>
On 03/18/2014 02:15 PM, Matt Porter wrote:
> On Fri, Jun 14, 2013 at 05:03:57AM -0400, Chao Xie wrote:
>> Check cpu id in pj4_cp0_init. So for no-PJ4 V7 cpus,
>> pj4_cpu0_init just return.
>> This fix will help to make the all the V7 cpus(pj4 and no-PJ4)
>> use same platform code.
>>
>> Signed-off-by: Chao Xie <chao.xie@marvell•com>
>> Acked-by: Arnd Bergmann <arnd@arndb•de>
>
> This patch fixes a boot failure in next now that ARCH_DOVE (and thus
> CPU_PJ4) are enabled in multi_v7_defconfig. I verified that boot works
> again in next with the BCM28155-AP board.
>
> Tested-by: Matt Porter <mporter@linaro•org>
This also solves the Tegra SoC boot failures with next-20130320.
Tested-by: Stephen Warren <swarren@nvidia•com>
prev parent reply other threads:[~2014-03-20 19:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 9:03 [PATCH V2] arm: pj4: check cpu id for pj4 cp0 access Chao Xie
2013-06-14 14:30 ` Arnd Bergmann
2014-03-18 20:15 ` [V2] " Matt Porter
2014-03-18 20:19 ` Kevin Hilman
2014-03-18 20:32 ` Russell King - ARM Linux
2014-03-19 1:36 ` Chao Xie
2014-03-20 19:04 ` Stephen Warren [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=532B3BA5.7080209@wwwdotorg.org \
--to=swarren@wwwdotorg$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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