From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCHv4 5/6] ARM: ls102xa: allow all the peripheral access permission as R/W.
Date: Thu, 11 Dec 2014 11:28:21 -0800 [thread overview]
Message-ID: <5489F055.2070000@freescale.com> (raw)
In-Reply-To: <1416562859-37857-6-git-send-email-Li.Xiubo@freescale.com>
On 11/21/2014 01:40 AM, Xiubo Li 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>
> Acked-by: York Sun <yorksun@freescale.com>
> ---
Applied to u-boot-fsl-qoriq master, awaiting upstream.
York
next prev parent reply other threads:[~2014-12-11 19:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 9:40 [U-Boot] [PATCHv4 0/6] ls102xa: HYP/non-sec: for ls102xa Xiubo Li
2014-11-21 9:40 ` [U-Boot] [PATCHv4 1/6] ARM: HYP/non-sec: add the pen address BE mode support Xiubo Li
2014-12-11 19:08 ` York Sun
2014-11-21 9:40 ` [U-Boot] [PATCHv4 2/6] ARM: HYP/non-sec: Fix the ARCH Timer frequency setting Xiubo Li
2014-12-11 20:57 ` York Sun
2014-11-21 9:40 ` [U-Boot] [PATCHv4 3/6] ls1021a: adding a secondary core boot address and kick functions Xiubo Li
2014-12-11 19:27 ` York Sun
2014-11-21 9:40 ` [U-Boot] [PATCHv4 4/6] ls102xa: changing a few targets' configurations Xiubo Li
2014-12-11 19:27 ` York Sun
2014-11-21 9:40 ` [U-Boot] [PATCHv4 5/6] ARM: ls102xa: allow all the peripheral access permission as R/W Xiubo Li
2014-12-11 19:28 ` York Sun [this message]
2014-11-21 9:40 ` [U-Boot] [PATCHv4 6/6] ARM: ls102xa: Setting device's stream id for SMMUs Xiubo Li
2014-12-11 19:28 ` York Sun
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=5489F055.2070000@freescale.com \
--to=yorksun@freescale.com \
--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