linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ивайло Димитров" <freemangordon@abv.bg>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: pdeschrijver@nvidia.com, pali.rohar@gmail.com, tony@atomide.com,
	linux@arm.linux.org.uk, linux-kernel@vger.kernel.org,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm: omap: RX-51: ARM errata 430973 workaround
Date: Wed, 6 Mar 2013 11:32:12 +0200 (EET)	[thread overview]
Message-ID: <107742828.129755.1362562332955.JavaMail.apache@mail81.abv.bg> (raw)

 




 >-------- Оригинално писмо --------
 >От:  Aaro Koskinen 
 >Относно: Re: [PATCH] arm: omap: RX-51: ARM errata 430973 workaround
 >До: Ивайло Димитров 
 >Изпратено на: Събота, 2013, Март 2 01:51:39 EET
 >
 >
 >On Fri, Mar 01, 2013 at 12:09:12PM +0200, Ивайло Димитров wrote:
 >> Unfortunately it is necessary, on RX-51 PPA/NOLO leaves IBE bit unset.
 >
 >You sure? I think you need to explain this more - the commit message in
 >the original patch is empty/missing...
 >
 >A.
 >

Yes, I am sure, NOLO leaves IBE bit in ACR unset, I've verified that by reading/printing the contents of ACR from both u-boot and the kernel itself. With IBE bit unset, "mcr p15, 0, rX, c7, c5, 6" - flush BTAC/BTB instruction(which is needed to workaround errata 430973) is a noop.

Yes, I am sure, IBE but must be set by using a call to PPA, on RX-51 setting that bit from the kernel (as it is done in the "ARM errata: Stale prediction on replaced interworking branch" kernel patch, see http://kerneltrap.org/mailarchive/git-commits-head/2009/5/3/5622724) does not work, see the comment at the end: "Note that setting specific bits in the ACTLR register may not be available in non-secure mode.". This is exactly the case for RX-51. I've verified that too.

If you need anything else elaborated on, I'm fine, just ask :)


Regards,
Ivo

             reply	other threads:[~2013-03-06  9:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06  9:32 Ивайло Димитров [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-03-30 22:31 [PATCH] arm: omap: RX-51: ARM errata 430973 workaround Ивайло Димитров
2013-03-31  7:37 ` Pavel Machek
2013-03-28  5:30 Ивайло Димитров
2013-03-28 15:58 ` Tony Lindgren
2013-03-01 10:09 Ивайло Димитров
2013-03-01 23:51 ` Aaro Koskinen
2013-03-01  7:47 Ивайло Димитров
2013-03-01 14:38 ` Nishanth Menon
2013-03-04 18:58   ` Tony Lindgren
2013-03-06 14:09     ` Pali Rohár
2013-03-06 17:51       ` Tony Lindgren
2013-03-06 19:13         ` Pali Rohár
2013-03-24 14:26           ` Pali Rohár
2013-03-27 20:56             ` Tony Lindgren
2013-03-27 21:05               ` Pali Rohár
2013-03-27 21:12                 ` Tony Lindgren
2013-03-28  9:50               ` Russell King - ARM Linux
2013-03-28 10:07                 ` Santosh Shilimkar
2013-03-28 15:53                   ` Tony Lindgren
2013-02-28  9:42 Pali Rohár
2013-02-28 14:40 ` Nishanth Menon
2013-03-01  9:43 ` Peter De Schrijver
2013-03-30 18:36 ` Pavel Machek

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=107742828.129755.1362562332955.JavaMail.apache@mail81.abv.bg \
    --to=freemangordon@abv.bg \
    --cc=aaro.koskinen@iki.fi \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=pali.rohar@gmail.com \
    --cc=pdeschrijver@nvidia.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 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).