devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: l2x0: add L210 write allocate override flag
Date: Mon, 18 Mar 2019 23:14:05 +0100	[thread overview]
Message-ID: <CACRpkdba=cp-jGvh+pN_Qg5cTFM+=052wiijQMra81QOG62cVQ@mail.gmail.com> (raw)
In-Reply-To: <20190318140439.xmfh66mbktpd55l2@shell.armlinux.org.uk>

On Mon, Mar 18, 2019 at 3:04 PM Russell King - ARM Linux admin
<linux@armlinux.org.uk> wrote:
> On Mon, Mar 18, 2019 at 09:30:53AM +0100, Linus Walleij wrote:
> > This adds support for setting the flag bit "write allocate
> > override" to the L210 variant.
> >
> > The "write allocate override" bit is used on the Nomadik STn8815
> > and is necessary to properly make use of the L210 cache on that
> > machine without sporadic crashes.
> >
> > After this the platform can boot and run without any out-of-tree
> > patches.
>
> This is not something that should be done by the kernel but by the
> firmware - needing this bit set is a basic requirement of having
> the caches enabled, and if (eg) the boot loader enables the caches
> it too will suffer this problem.

I see your point. This U-Boot port does not enable the cache, I guess
because it was a bit unusual for ARM926EJ-S machines to have
L2 cache at  the time, and I remember U-Boot was not using L2CC for
a long time (maybe still not?).

The Nomadik was unstable for years and then I looked at the
outoftree vendor kernel and saw that it sets this bit and since I did that
it has been rock solid.

I can of course try to recompile and reflash the U-Boot for this
board but it is stored in NAND flash and if I break it, ugh, I have
toasted this board and I only have one. So I'm scared about that.

I have been carrying this as an out-of-tree patch for years and I can of
course continue to do so, I just felt it was a bit sad so I tried
to diet down the previous patch to the single bit the Nomadik
needs to set up for it's L2CC to work.

Yours,
Linus Walleij

  reply	other threads:[~2019-03-18 22:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18  8:30 [PATCH] ARM: l2x0: add L210 write allocate override flag Linus Walleij
2019-03-18  8:41 ` Stefan Agner
2019-03-18 14:04 ` Russell King - ARM Linux admin
2019-03-18 22:14   ` Linus Walleij [this message]
2019-03-31  6:40     ` Rob Herring

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='CACRpkdba=cp-jGvh+pN_Qg5cTFM+=052wiijQMra81QOG62cVQ@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    /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).