From: patrice.chotard@st•com (Patrice Chotard)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: sti: Implement dummy L2 cache's write_sec
Date: Tue, 28 Jun 2016 13:55:36 +0200 [thread overview]
Message-ID: <577265B8.5030009@st.com> (raw)
In-Reply-To: <20160628094914.GI1041@n2100.armlinux.org.uk>
Hi Russell
On 06/28/2016 11:49 AM, Russell King - ARM Linux wrote:
> On Tue, Jun 28, 2016 at 11:40:37AM +0200, patrice.chotard at st.com wrote:
>> From: Patrice Chotard <patrice.chotard@st•com>
>>
>> This patch implements the write_sec callback that handle PL310
>> secure registers writes.
>> This callback is just a stub for now, to avoid system crash.
>> Later, it could handle SMC calls so that TZ handles the needed writes.
> Is there much point having the L2 cache DT node enabled if you have
> no support for the writes, which are required for the hardware to be
> enabled?
>
It's similar to what has been done for ux500 machine, in non secure
mode, we
can't write in L2 cache secure registers.
Patrice
prev parent reply other threads:[~2016-06-28 11:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 9:40 [PATCH] ARM: sti: Implement dummy L2 cache's write_sec patrice.chotard at st.com
2016-06-28 9:49 ` Russell King - ARM Linux
2016-06-28 11:55 ` Patrice Chotard [this message]
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=577265B8.5030009@st.com \
--to=patrice.chotard@st$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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