From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 4/4] ARM: ls102xa: allow all the peripheral access permissions as R/W.
Date: Thu, 13 Nov 2014 07:08:45 +0100 [thread overview]
Message-ID: <20141113070845.419d650f@lilith> (raw)
In-Reply-To: <1412737656-33561-5-git-send-email-Li.Xiubo@freescale.com>
Hello York,
On Wed, 8 Oct 2014 11:07:36 +0800, Xiubo Li <Li.Xiubo@freescale.com>
wrote:
> The Central Security Unit (CSU) allows secure world software to
> change the default access control policies of peripherals/bus
> slaves, determining which bus masters may access them. This
> allows peripherals to be separated into distinct security domains.
> Combined with SMMU configuration of the system masters privileges,
> these features provide protection against indirect unauthorized
> access to data.
>
> For now we configure all the peripheral access permissions as R/W.
>
> Signed-off-by: Xiubo Li <Li.Xiubo@freescale.com>
> ---
I see half this set is delegated to you and half to me. If you just give
your Acked-by: to patches 3 and 4, I will handle the whole set.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2014-11-13 6:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 3:07 [U-Boot] [PATCH v2 0/4] ls102xa: HYP/non-sec: for ls102xa Xiubo Li
2014-10-08 3:07 ` [U-Boot] [PATCH v2 1/4] ARM: HYP/non-sec: add the pen address byte reverting support Xiubo Li
2014-10-08 3:07 ` [U-Boot] [PATCH v2 2/4] ARM: HYP/non-sec: Fix the ARCH Timer frequency setting Xiubo Li
2014-10-08 3:07 ` [U-Boot] [PATCH v2 3/4] ls102xa: HYP/non-sec: support for ls102xa boards Xiubo Li
2014-10-08 3:07 ` [U-Boot] [PATCH v2 4/4] ARM: ls102xa: allow all the peripheral access permissions as R/W Xiubo Li
2014-11-13 6:08 ` Albert ARIBAUD [this message]
2014-11-13 6:09 ` York Sun
2014-11-13 16:50 ` York Sun
2014-11-14 6:55 ` Albert ARIBAUD
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=20141113070845.419d650f@lilith \
--to=albert.u.boot@aribaud.net \
--cc=u-boot@lists.denx.de \
/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