From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: omap: RX-51: ARM errata 430973 workaround
Date: Thu, 28 Mar 2013 08:53:30 -0700 [thread overview]
Message-ID: <20130328155330.GS10155@atomide.com> (raw)
In-Reply-To: <5154165C.4050604@ti.com>
* Santosh Shilimkar <santosh.shilimkar@ti.com> [130328 03:10]:
> On Thursday 28 March 2013 03:20 PM, Russell King - ARM Linux wrote:
> > On Wed, Mar 27, 2013 at 01:56:07PM -0700, Tony Lindgren wrote:
> >> * Pali Roh?r <pali.rohar@gmail.com> [130324 07:31]:
> >>> it is possible to upstream errata 430973 workaround for RX-51?
> >>
> >> I think we should make the SMC handling a generic function for ARM.
> >>
> >> AFAIK just the SMC call numbering is different for various
> >> implementations. So the handler and passing of the parameters
> >> seems like it should be generic.
> >
> > SMC calls vary greatly in how they are handled. The only thing that's
> > generic is issuing the SMC call. All the setup and what arguments are
> > required are completely different from SoC to SoC.
> >
> > For example, some SoCs require arguments passed via memory. Others like
> > OMAP its via registers.
>
> Exactly. As somebody said on the list, that code looks identical but
> it is not. An SMC with barrier instruction is mostly common and nothing
> more than that.
Thanks all, case closed then. There's no way to come up with a generic
SMC function.
Regards,
Tony
next prev parent reply other threads:[~2013-03-28 15:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <517283541.62064.1362124023621.JavaMail.apache@mail81.abv.bg>
2013-03-01 14:38 ` [PATCH] arm: omap: RX-51: ARM errata 430973 workaround 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 [this message]
[not found] <1838509461.25809.1364682678664.JavaMail.apache@mail83.abv.bg>
2013-03-31 7:37 ` Pavel Machek
[not found] <24838523.73311.1364448607026.JavaMail.apache@mail82.abv.bg>
2013-03-28 15:58 ` Tony Lindgren
[not found] <604513288.26328.1362132552062.JavaMail.apache@mail83.abv.bg>
2013-03-01 23:51 ` Aaro Koskinen
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=20130328155330.GS10155@atomide.com \
--to=tony@atomide.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).