From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3][v5] crypto/fsl: SEC driver cleanup for 64 bit and endianness
Date: Fri, 30 Oct 2015 09:15:20 -0700 [thread overview]
Message-ID: <56339798.9060305@freescale.com> (raw)
In-Reply-To: <1446139683-2242-1-git-send-email-aneesh.bansal@freescale.com>
On 10/29/2015 10:28 AM, Aneesh Bansal wrote:
> The SEC driver code has been cleaned up to work for 64 bit
> physical addresses and systems where endianess of SEC block
> is different from the Core.
> Changes:
> 1. Descriptor created on Core is modified as per SEC block
> endianness before the job is submitted.
> 2. The read/write of physical addresses to Job Rings will
> be depend on endianness of SEC block as 32 bit low and
> high part of the 64 bit address will vary.
> 3. The 32 bit low and high part of the 64 bit address in
> descriptor will vary depending on endianness of SEC.
>
> Signed-off-by: Aneesh Bansal <aneesh.bansal@freescale.com>
> ---
> Changes in v5:
> Removed compile time warnings
Applied to u-boot-fsl-qoriq. Awaiting upstream. Thanks.
York
prev parent reply other threads:[~2015-10-30 16:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 17:28 [U-Boot] [PATCH 3/3][v5] crypto/fsl: SEC driver cleanup for 64 bit and endianness Aneesh Bansal
2015-10-30 16:15 ` York Sun [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=56339798.9060305@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