From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/3] crypto/fsl: fix snooping for write transactions
Date: Tue, 4 Aug 2015 08:56:38 -0700 [thread overview]
Message-ID: <55C0E0B6.1040002@freescale.com> (raw)
In-Reply-To: <1436365498-25890-2-git-send-email-horia.geanta@freescale.com>
On 07/08/2015 07:24 AM, Horia Geant? wrote:
> HW coherency won't work properly for CAAM write transactions
> if AWCACHE is left to default (POR) value - 4'b0001.
> It has to be programmed to 4'b0010.
>
> For platforms that have HW coherency support:
> -PPC-based: the update has no effect; CAAM coherency already works
> due to the IOMMU (PAMU) driver setting the correct memory coherency
> attributes
> -ARM-based: the update fixes cache coherency issues,
> since IOMMU (SMMU) driver is not programmed to behave similar to PAMU
>
> Fixes: b9eebfade974c ("fsl_sec: Add hardware accelerated SHA256 and SHA1")
> Signed-off-by: Horia Geant? <horia.geanta@freescale.com>
> Reviewed-by: Aneesh Bansal <aneesh.bansal@freescale.com>
> Reviewed-by: Mingkai Hu <Mingkai.Hu@freescale.com>
> ---
Applied to u-boot-fsl-qoriq master with minor change in subject. Thanks.
York
next prev parent reply other threads:[~2015-08-04 15:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 14:24 [U-Boot] [PATCH 1/3] crypto/fsl: fix "era" property value on LE platforms Horia Geantă
2015-07-08 14:24 ` [U-Boot] [PATCH 2/3] crypto/fsl: fix snooping for write transactions Horia Geantă
[not found] ` <55AACF9F.8090601@freescale.com>
2015-07-22 16:38 ` Ruchika Gupta
2015-08-04 15:56 ` York Sun [this message]
2015-07-08 14:24 ` [U-Boot] [PATCH 3/3] crypto/fsl: clean-up - use fdt_setprop_u32 helper Horia Geantă
[not found] ` <55AACFAC.5080902@freescale.com>
2015-07-22 16:38 ` Ruchika Gupta
2015-08-04 15:56 ` York Sun
[not found] ` <55AACF92.9070508@freescale.com>
2015-07-22 16:38 ` [U-Boot] [PATCH 1/3] crypto/fsl: fix "era" property value on LE platforms Ruchika Gupta
2015-08-04 15:56 ` 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=55C0E0B6.1040002@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