summaryrefslogtreecommitdiff
path: root/drivers/crypto
diff options
context:
space:
mode:
authorSteve Cornelius <steve.cornelius@freescale.com>2012-07-06 17:35:55 -0700
committerTerry Lv <r65388@freescale.com>2012-07-25 13:11:11 +0800
commite4bdc0bf1531ac4aab62ba822dc265c29eadf9da (patch)
tree35bd0ee0c03dd18460e53f20950e918d4e9906ba /drivers/crypto
parent631a53a12ecc759ae7a88e3a993e99f45e2cece6 (diff)
ENGR00215945-2: Fix directions in cache coherence functions
During a bug search, a review turned up two places where the wrong direction was used in dma_sync function calls. In practice. these compiled away to be inconsequential on the platform in question, but this may not be true on all platforms. Signed-off-by: Steve Cornelius <steve.cornelius@freescale.com> Signed-off-by: Terry Lv <r65388@freescale.com>
Diffstat (limited to 'drivers/crypto')
-rw-r--r--drivers/crypto/caam/caamhash.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/drivers/crypto/caam/caamhash.c b/drivers/crypto/caam/caamhash.c
index fe6af79419db..cdc3f3efef02 100644
--- a/drivers/crypto/caam/caamhash.c
+++ b/drivers/crypto/caam/caamhash.c
@@ -167,7 +167,7 @@ static inline dma_addr_t buf_map_to_sec4_sg(struct device *jrdev,
dma_addr_t buf_dma;
buf_dma = dma_map_single(jrdev, buf, buflen, DMA_TO_DEVICE);
- dma_sync_single_for_cpu(jrdev, buf_dma, buflen, DMA_TO_DEVICE);
+ dma_sync_single_for_device(jrdev, buf_dma, buflen, DMA_TO_DEVICE);
dma_to_sec4_sg_one(sec4_sg, buf_dma, buflen, 0);
return buf_dma;
@@ -556,8 +556,8 @@ static int ahash_setkey(struct crypto_ahash *ahash,
return -ENOMEM;
}
- dma_sync_single_for_cpu(jrdev, ctx->key_dma, ctx->split_key_pad_len,
- DMA_TO_DEVICE);
+ dma_sync_single_for_device(jrdev, ctx->key_dma, ctx->split_key_pad_len,
+ DMA_TO_DEVICE);
#ifdef DEBUG
print_hex_dump(KERN_ERR, "ctx.key@"xstr(__LINE__)": ",