linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Kconfig: Let ARM_ERRATA_364296 not depend on CONFIG_SMP
Date: Tue, 9 Jul 2013 09:37:13 +0100	[thread overview]
Message-ID: <20130709083713.GA26895@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <20130708215320.GU24642@n2100.arm.linux.org.uk>

On Mon, Jul 08, 2013 at 10:53:20PM +0100, Russell King - ARM Linux wrote:
> On Mon, Jul 08, 2013 at 06:38:09PM -0300, Fabio Estevam wrote:
> > From: Fabio Estevam <fabio.estevam@freescale.com>
> > 
> > imx_v6_v7_defconfig handles both multi-core and single-core SoCs, and it has 
> > CONFIG_SMP=y selected by default.
> > 
> > With such config we cannot select ARM_ERRATA_364296, as it depends on !SMP.
> > 
> > Let ARM_ERRATA_364296 be undependent on CONFIG_SMP, so that we can select
> > this erratum for the ARM1136 SoCs, even if CONFIG_SMP=y is enabled.
> 
> I'll wait for ARM Ltd folk to comment on this (they're at Linaro Connect
> at the moment which has extremely poor 'net connectivity from what I've
> been hearing).  We might need to bypass the workaround code in the non-SMP
> case.

The workaround (in proc-v6.S) checks the midr specifically for 1136 r0p2, so
it should be fine to remove the CONFIG_SMP dependency given that the 1136 is
UP only.

Will

  reply	other threads:[~2013-07-09  8:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08 21:38 [PATCH] ARM: Kconfig: Let ARM_ERRATA_364296 not depend on CONFIG_SMP Fabio Estevam
2013-07-08 21:53 ` Russell King - ARM Linux
2013-07-09  8:37   ` Will Deacon [this message]
2013-07-09  8:30 ` Dave Martin
2013-07-12 15:15 ` Catalin Marinas

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=20130709083713.GA26895@mudshark.cambridge.arm.com \
    --to=will.deacon@arm.com \
    --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;
as well as URLs for NNTP newsgroup(s).