From: Catalin Marinas <catalin.marinas@arm.com>
To: Rob Herring <robherring2@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Dave Martin <dave.martin@linaro.org>,
Will Deacon <Will.Deacon@arm.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Jon Hunter <jon-hunter@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: Fix errata 751472 handling on Cortex-A9 r1p*
Date: Thu, 15 Nov 2012 16:06:38 +0000 [thread overview]
Message-ID: <20121115160638.GA30579@arm.com> (raw)
In-Reply-To: <50A50C24.9010702@gmail.com>
On Thu, Nov 15, 2012 at 03:37:08PM +0000, Rob Herring wrote:
> On 11/15/2012 08:37 AM, Catalin Marinas wrote:
> > On Thu, Nov 15, 2012 at 02:31:33PM +0000, Rob Herring wrote:
> >> Does that work for Versatile Express CA9? It needs ARM_ERRATA_751472.
> >
> > On VE Linux runs in secure mode, so it's fine.
>
> WTF? You are contradicting yourself.
No, it was just a statement that you can enable this workaround on VE
CA9. Didn't realise you were referring to the MULTI_PLATFORM case (it's
afternoon and coffee here not that great).
> Don't determine secure mode or not,
> but apply work-arounds only in secure mode? How does a kernel built to
> boot on secure and non-secure chips know that? The requirement would be
> that every platform have proper work-arounds setup by the bootloader
> regardless of running in secure or non-secure mode.
Yes, so for such workarounds that require secure register access just
make them depend on !MULTI_PLATFORM. Of course, VE CA9 would be affected
since neither the boot loader nor boot monitor touch those bits (yet).
But they definitely should as I don't see any other way to support
multi-platform, especially when such bits need to be set long before the
DT is parsed.
--
Catalin
WARNING: multiple messages have this Message-ID (diff)
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Fix errata 751472 handling on Cortex-A9 r1p*
Date: Thu, 15 Nov 2012 16:06:38 +0000 [thread overview]
Message-ID: <20121115160638.GA30579@arm.com> (raw)
In-Reply-To: <50A50C24.9010702@gmail.com>
On Thu, Nov 15, 2012 at 03:37:08PM +0000, Rob Herring wrote:
> On 11/15/2012 08:37 AM, Catalin Marinas wrote:
> > On Thu, Nov 15, 2012 at 02:31:33PM +0000, Rob Herring wrote:
> >> Does that work for Versatile Express CA9? It needs ARM_ERRATA_751472.
> >
> > On VE Linux runs in secure mode, so it's fine.
>
> WTF? You are contradicting yourself.
No, it was just a statement that you can enable this workaround on VE
CA9. Didn't realise you were referring to the MULTI_PLATFORM case (it's
afternoon and coffee here not that great).
> Don't determine secure mode or not,
> but apply work-arounds only in secure mode? How does a kernel built to
> boot on secure and non-secure chips know that? The requirement would be
> that every platform have proper work-arounds setup by the bootloader
> regardless of running in secure or non-secure mode.
Yes, so for such workarounds that require secure register access just
make them depend on !MULTI_PLATFORM. Of course, VE CA9 would be affected
since neither the boot loader nor boot monitor touch those bits (yet).
But they definitely should as I don't see any other way to support
multi-platform, especially when such bits need to be set long before the
DT is parsed.
--
Catalin
next prev parent reply other threads:[~2012-11-15 16:06 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 18:53 [PATCH] ARM: Fix errata 751472 handling on Cortex-A9 r1p* Tony Lindgren
2012-11-14 18:53 ` Tony Lindgren
2012-11-14 19:01 ` Russell King - ARM Linux
2012-11-14 19:01 ` Russell King - ARM Linux
2012-11-14 19:19 ` Tony Lindgren
2012-11-14 19:19 ` Tony Lindgren
2012-11-14 19:06 ` Jon Hunter
2012-11-14 19:06 ` Jon Hunter
2012-11-14 19:21 ` Tony Lindgren
2012-11-14 19:21 ` Tony Lindgren
2012-11-14 20:22 ` Russell King - ARM Linux
2012-11-14 20:22 ` Russell King - ARM Linux
2012-11-14 20:32 ` Tony Lindgren
2012-11-14 20:32 ` Tony Lindgren
2012-11-14 21:57 ` Rob Herring
2012-11-14 21:57 ` Rob Herring
2012-11-14 22:21 ` Tony Lindgren
2012-11-14 22:21 ` Tony Lindgren
2012-11-15 0:54 ` Rob Herring
2012-11-15 0:54 ` Rob Herring
2012-11-15 2:08 ` Tony Lindgren
2012-11-15 2:08 ` Tony Lindgren
2012-11-15 11:01 ` Catalin Marinas
2012-11-15 11:01 ` Catalin Marinas
2012-11-15 12:41 ` Siarhei Siamashka
2012-11-15 12:41 ` Siarhei Siamashka
2012-11-15 13:36 ` Russell King - ARM Linux
2012-11-15 13:36 ` Russell King - ARM Linux
2012-11-15 13:52 ` Catalin Marinas
2012-11-15 13:52 ` Catalin Marinas
2012-11-15 15:14 ` Måns Rullgård
2012-11-15 15:14 ` Måns Rullgård
2012-11-15 14:31 ` Rob Herring
2012-11-15 14:31 ` Rob Herring
2012-11-15 14:37 ` Catalin Marinas
2012-11-15 14:37 ` Catalin Marinas
2012-11-15 15:37 ` Rob Herring
2012-11-15 15:37 ` Rob Herring
2012-11-15 16:06 ` Catalin Marinas [this message]
2012-11-15 16:06 ` Catalin Marinas
2012-11-16 10:05 ` Russell King - ARM Linux
2012-11-16 10:05 ` Russell King - ARM Linux
2012-11-16 17:13 ` Tony Lindgren
2012-11-16 17:13 ` Tony Lindgren
2012-11-16 18:41 ` Russell King - ARM Linux
2012-11-16 18:41 ` Russell King - ARM Linux
2012-11-16 9:59 ` Russell King - ARM Linux
2012-11-16 9:59 ` Russell King - ARM Linux
2012-11-16 18:09 ` Catalin Marinas
2012-11-16 18:09 ` Catalin Marinas
2012-11-16 18:39 ` Russell King - ARM Linux
2012-11-16 18:39 ` Russell King - ARM Linux
2012-11-17 10:46 ` Catalin Marinas
2012-11-17 10:46 ` Catalin Marinas
2012-11-15 9:22 ` Russell King - ARM Linux
2012-11-15 9:22 ` Russell King - ARM Linux
2012-12-12 0:46 ` Jon Masters
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=20121115160638.GA30579@arm.com \
--to=catalin.marinas@arm.com \
--cc=Will.Deacon@arm.com \
--cc=dave.martin@linaro.org \
--cc=jon-hunter@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=robherring2@gmail.com \
--cc=santosh.shilimkar@ti.com \
--cc=tony@atomide.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.