From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 1/5] ARM: cache-l2x0: add 'smc' identifier
Date: Tue, 29 Jan 2013 12:22:56 +0000 [thread overview]
Message-ID: <20130129122255.GI2637@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20130129114926.GA14624@bnru10>
On Tue, Jan 29, 2013 at 05:19:27PM +0530, Srinidhi Kasagar wrote:
> On Tue, Jan 29, 2013 at 12:33:25 +0100, Russell King - ARM Linux wrote:
> > On Tue, Jan 29, 2013 at 03:43:31PM +0530, srinidhi kasagar wrote:
> > > Add 'smc' (Secure Monitor Call) identifier to differentiates
> > > the platforms which implements this.
> >
> > This patch makes no sense.
> >
> > So, if setting 'smc' in the DT description is supposed to mean that
> > the platform has a secure monitor then...
> >
> > > + is_smc = of_property_read_bool(np, "smc");
> > > +
> > > + if (is_smc) {
> > > + /* set the debug interface */
> > > + outer_cache.set_debug = pl310_set_debug;
> > > + }
> >
> > Now, let's look at what pl310_set_debug() does:
> >
> > static void pl310_set_debug(unsigned long val)
> > {
> > writel_relaxed(val, l2x0_base + L2X0_DEBUG_CTRL);
>
> You can do this operation (write to DEBUG_CTRL) only if SMC is implemented.
Err... no. You can do it if you're running in secure mode without a
secure monitor, because the security stuff doesn't get in the way.
What other platforms do is up to them, and up to *how* the secure monitor
is implemented, not *if*.
> > }
> >
> > Can you explain where the secure monitor call is there please, because
> > I can't see one. In fact, this is the function used when there _isn't_
> > a secure monitor. So this patch just seems totally wrong to me.
So this is going to be difficult because you only ever answer half an
email? So, I repeat the question above.
next prev parent reply other threads:[~2013-01-29 12:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 10:13 [PATCH v1 1/5] ARM: cache-l2x0: add 'smc' identifier srinidhi kasagar
2013-01-29 11:33 ` Russell King - ARM Linux
2013-01-29 11:38 ` Srinidhi Kasagar
2013-01-29 11:44 ` Russell King - ARM Linux
2013-01-29 11:49 ` Srinidhi Kasagar
2013-01-29 12:22 ` Russell King - ARM Linux [this message]
2013-01-30 5:06 ` Srinidhi Kasagar
2013-01-29 15:37 ` Tomasz Figa
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=20130129122255.GI2637@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).