From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: realview: Fix PBX-A9 cache description
Date: Wed, 10 Aug 2016 22:46:39 +0200 [thread overview]
Message-ID: <4141561.enkVqu9s0z@wuerfel> (raw)
In-Reply-To: <1470830537-12307-1-git-send-email-linus.walleij@linaro.org>
On Wednesday, August 10, 2016 2:02:17 PM CEST Linus Walleij wrote:
> From: Robin Murphy <robin.murphy@arm.com>
>
> Clearly QEMU is very permissive in how its PL310 model may be set up,
> but the real hardware turns out to be far more particular about things
> actually being correct. Fix up the DT description so that the real
> thing actually boots:
>
> - The arm,data-latency and arm,tag-latency properties need 3 cells to
> be valid, otherwise we end up retaining the default 8-cycle latencies
> which leads pretty quickly to lockup.
> - The arm,dirty-latency property is only relevant to L210/L220, so get
> rid of it.
> - The cache geometry override also leads to lockup and/or general
> misbehaviour. Irritatingly, the manual doesn't state the actual PL310
> configuration, but based on the boardfile code and poking registers
> from the Boot Monitor, it would seem to be 8 sets of 16KB ways.
>
> With that, we can successfully boot to enjoy the fun of mismatched FPUs...
>
> Cc: stable at vger.kernel.org
> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
> Tested-by: Mark Rutland <mark.rutland@arm.com>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> ARM SoC folks: please apply this directly for fixes. I had
> queued it for worries of clashing with other updates, but I think
> it will be fine, and it needs to go in for v4.8.
>
Applied to fixes, thanks
Arnd
prev parent reply other threads:[~2016-08-10 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 12:02 [PATCH] ARM: dts: realview: Fix PBX-A9 cache description Linus Walleij
2016-08-10 20:46 ` Arnd Bergmann [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=4141561.enkVqu9s0z@wuerfel \
--to=arnd@arndb.de \
--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