All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/fsl-booke: Work around erratum A-006958
Date: Mon, 15 Jul 2013 11:55:11 -0500	[thread overview]
Message-ID: <1373907311.8183.298@snotra> (raw)
In-Reply-To: <87mwpojr6d.fsf@linux.vnet.ibm.com> (from aneesh.kumar@linux.vnet.ibm.com on Mon Jul 15 01:03:22 2013)

On 07/15/2013 01:03:22 AM, Aneesh Kumar K.V wrote:
> Scott Wood <scottwood@freescale.com> writes:
>=20
>=20
>=20
> > diff --git a/arch/powerpc/platforms/Kconfig.cputype =20
> b/arch/powerpc/platforms/Kconfig.cputype
> > index ae0aaea..7f0e2e5 100644
> > --- a/arch/powerpc/platforms/Kconfig.cputype
> > +++ b/arch/powerpc/platforms/Kconfig.cputype
> > @@ -165,6 +165,17 @@ config PPC_E500MC
> >  	  such as e5500/e6500), and must be disabled for running on
> >  	  e500v1 or e500v2.
> >
> > +config FSL_ERRATUM_A_006958
> > +	bool
> > +	depends on PPC_E500MC && PPC64
> > +	default y
> > +	help
> > +	  Workaround for erratum A-006958, which says that 64-bit
> > +	  timebase reads are not atomic.  The workaround is to fall back
> > +	  to the 32-bit method of reading timebase.  Note that timebase
> > +	  is readable by userspace, so any non-vdso userspace accesses
> > +	  will need to have the workaround applied separately.
> > +
> >  config PPC_FPU
> >  	bool
> >  	default y if PPC64
>=20
>=20
> I am completely new to this area, so ignore if it is silly. But how do
> we expect to select this config ? Should that happen via .config ?

It will automatically be selected if PPC_E500MC and PPC64 are both =20
selected.

-Scott=

  reply	other threads:[~2013-07-15 16:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-13  1:03 [PATCH] powerpc/fsl-booke: Work around erratum A-006958 Scott Wood
2013-07-15  6:03 ` Aneesh Kumar K.V
2013-07-15 16:55   ` Scott Wood [this message]
2013-07-15  8:45 ` David Laight
2013-07-15 16:53   ` Scott Wood
2013-07-15 22:15     ` Scott Wood
2013-07-16  8:28       ` David Laight
2013-07-16 18:16         ` Scott Wood

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=1373907311.8183.298@snotra \
    --to=scottwood@freescale.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.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 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.