From: marc_gonzalez@sigmadesigns.com (Marc Gonzalez)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 2/2] arm-soc: Add support for arm-based tango4 platforms
Date: Tue, 3 Nov 2015 18:04:32 +0100 [thread overview]
Message-ID: <5638E920.1030009@sigmadesigns.com> (raw)
In-Reply-To: <5638E2C3.4030402@oracle.com>
On 03/11/2015 17:37, Santosh Shilimkar wrote:
> On 11/3/2015 2:12 AM, M?ns Rullg?rd wrote:
>> Marc Gonzalez writes:
>>
>>> Santosh Shilimkar wrote:
>>>
>>>> Mark Rutland wrote:
>>>>
>>>>> We didn't. Having a look just now, the earliest example appears to be
>>>>> in OMAP4 L2 support patches back in 2009 [1]. I was not able to find a
>>>>> rationale.
>>>>>
>>>>> Given that the MMU is on (and speculative accesses are permitted) I
>>>>> can't see what the DSB achieves -- it can't quiesce the memory system.
>>>>>
>>>>> Santosh, any idea?
>>>>
>>>> IIRC, it was requirement from the OMAP ROM code to have a dsb before
>>>> we call the SMC routine. I can't recollect more than that now.
>>>
>>> In that case, shouldn't dsb have been added to the ROM code,
>>> on the "other side" of the smc, so as to not depend on Linux
>>> code "getting it right"?
>>
>> You're new to this, aren't you? :)
>
> :-) Indeed. ROM code is burned into the chip and can't be changed.
Oh, that kind of ROM... I thought EEPROM.
(Our secure OS is stored in NAND flash.)
If I'm bored, I'll try measuring the run-time difference with
and without dsb.
Regards.
next prev parent reply other threads:[~2015-11-03 17:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 15:17 [PATCH v8 0/2] Sigma Designs Tango4 port Marc Gonzalez
2015-11-02 15:18 ` [PATCH v8 1/2] arm-soc: Import initial tango4 device tree Marc Gonzalez
2015-11-02 16:01 ` Måns Rullgård
2015-11-02 17:11 ` Marc Gonzalez
2015-11-02 17:59 ` Måns Rullgård
2015-11-03 0:57 ` Måns Rullgård
2015-11-02 20:33 ` Florian Fainelli
2015-11-02 15:19 ` [PATCH v8 2/2] arm-soc: Add support for arm-based tango4 platforms Marc Gonzalez
2015-11-02 16:22 ` Måns Rullgård
2015-11-02 17:33 ` Marc Gonzalez
2015-11-02 18:01 ` Måns Rullgård
2015-11-02 18:26 ` Mark Rutland
2015-11-02 18:30 ` Måns Rullgård
2015-11-02 18:37 ` santosh shilimkar
2015-11-03 8:34 ` Marc Gonzalez
2015-11-03 10:12 ` Måns Rullgård
2015-11-03 16:37 ` santosh shilimkar
2015-11-03 17:04 ` Marc Gonzalez [this message]
2015-11-03 18:02 ` Måns Rullgård
2015-11-02 15:52 ` [PATCH v8 0/2] Sigma Designs Tango4 port Marc Gonzalez
2015-11-02 21:40 ` Arnd Bergmann
2015-11-03 9:00 ` Marc Gonzalez
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=5638E920.1030009@sigmadesigns.com \
--to=marc_gonzalez@sigmadesigns.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).