linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: disable errata work-arounds which access secure registers
Date: Fri, 04 Jan 2013 16:08:08 -0600	[thread overview]
Message-ID: <50E752C8.20608@gmail.com> (raw)
In-Reply-To: <CAOMZO5DP8kvfqG+uTbiRKeVe2aOKNs6DnGOBhK-WhGi9_7hV7Q@mail.gmail.com>

On 01/04/2013 03:45 PM, Fabio Estevam wrote:
> On Fri, Jan 4, 2013 at 7:39 PM, Fabio Estevam <festevam@gmail.com> wrote:
>>
>> Should we do like this?
> 
> Looks like this would be better (same as it was done for vexpress):
> 
> diff --git a/arch/arm/mach-imx/Kconfig b/arch/arm/mach-imx/Kconfig
> index 1ad0d76..3e628fd 100644
> --- a/arch/arm/mach-imx/Kconfig
> +++ b/arch/arm/mach-imx/Kconfig
> @@ -841,8 +841,6 @@ config SOC_IMX6Q
>         select ARCH_HAS_CPUFREQ
>         select ARCH_HAS_OPP
>         select ARM_CPU_SUSPEND if PM
> -       select ARM_ERRATA_743622
> -       select ARM_ERRATA_751472
>         select ARM_ERRATA_754322
>         select ARM_ERRATA_764369 if SMP
>         select ARM_ERRATA_775420
> 
> Rob, is this the correct approach?

Yes, that's the correct approach (along with updating the bootloader to
enable these work-arounds). I had this fix on my todo (the git
autobuilder caught it yesterday), but haven't gotten to it. So if you
could send it out that would be great.

Rob

      reply	other threads:[~2013-01-04 22:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-12 22:25 [PATCH 2/2] ARM: disable errata work-arounds which access secure registers Rob Herring
2012-12-14  0:17 ` Tony Lindgren
2013-01-04 21:29 ` Fabio Estevam
2013-01-04 21:39   ` Fabio Estevam
2013-01-04 21:45     ` Fabio Estevam
2013-01-04 22:08       ` Rob Herring [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=50E752C8.20608@gmail.com \
    --to=robherring2@gmail.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).