From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, 2/2] ARM: keystone2: Add missing privilege ID settings
Date: Fri, 1 Apr 2016 21:56:28 -0400 [thread overview]
Message-ID: <20160402015628.GS23166@bill-the-cat> (raw)
In-Reply-To: <1458746059-17893-3-git-send-email-nm@ti.com>
On Wed, Mar 23, 2016 at 10:14:19AM -0500, Nishanth Menon wrote:
> Add missing Privilege ID settings for KS2 SoCs.
>
> Based on:
> K2H/K: Table 6-7. Privilege ID Settings from SPRS866E (Nov 2013)
> http://www.ti.com/lit/ds/symlink/66ak2h14.pdf (page 99)
> K2L: Table 7-7. Privilege ID Settings from SPRS930 (April 2015)
> http://www.ti.com/lit/ds/symlink/66ak2l06.pdf (page 71)
> K2E: Table 7-7. Privilege ID Settings from SPRS865D (Mar 2015)
> http://www.ti.com/lit/ds/symlink/66ak2e05.pdf (page 75)
> K2G: Table 3-16. PrivIDs from SPRUHY8 (Jan 2016)
> http://www.ti.com/lit/ug/spruhy8/spruhy8.pdf (page 238)
>
> Overall mapping:
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160401/0d980545/attachment.sig>
prev parent reply other threads:[~2016-04-02 1:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 15:14 [U-Boot] [PATCH 0/2] ARM: keystone2: Fix missing privilege ID Nishanth Menon
2016-03-23 15:14 ` [U-Boot] [PATCH 1/2] ARM: keystone2: Refactor MSMC macros to avoid #ifdeffery Nishanth Menon
2016-03-24 2:42 ` Lokesh Vutla
2016-03-25 22:59 ` Tom Rini
2016-04-02 1:56 ` [U-Boot] [U-Boot, " Tom Rini
2016-03-23 15:14 ` [U-Boot] [PATCH 2/2] ARM: keystone2: Add missing privilege ID settings Nishanth Menon
2016-03-24 2:43 ` Lokesh Vutla
2016-03-25 22:59 ` Tom Rini
2016-04-02 1:56 ` Tom Rini [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=20160402015628.GS23166@bill-the-cat \
--to=trini@konsulko.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