crypto: omap-sham - change the DMA threshold value to a define

Currently the threshold value was hardcoded in the driver. Having a define
for it makes it easier to configure.

Signed-off-by: Tero Kristo <t-kristo@ti.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>

diff --git a/drivers/crypto/omap-sham.c b/drivers/crypto/omap-sham.c
index 855898977d38539b2443043e45952bb9a198e403..5c95bf97c13291c8f33c1dc21d79aaf0726fe350 100644 (file)
--- a/drivers/crypto/omap-sham.c
+++ b/drivers/crypto/omap-sham.c
@@ -137,6 +137,7 @@
 #define OMAP_ALIGNED           __attribute__((aligned(sizeof(u32))))
 
 #define BUFLEN                 PAGE_SIZE
+#define OMAP_SHA_DMA_THRESHOLD 256
 
 struct omap_sham_dev;
 
@@ -1435,10 +1436,11 @@ static int omap_sham_final(struct ahash_request *req)
        /*
         * OMAP HW accel works only with buffers >= 9.
         * HMAC is always >= 9 because ipad == block size.
-        * If buffersize is less than 240, we use fallback SW encoding,
-        * as using DMA + HW in this case doesn't provide any benefit.
+        * If buffersize is less than DMA_THRESHOLD, we use fallback
+        * SW encoding, as using DMA + HW in this case doesn't provide
+        * any benefit.
         */
-       if (!ctx->digcnt && ctx->bufcnt < 240)
+       if (!ctx->digcnt && ctx->bufcnt < OMAP_SHA_DMA_THRESHOLD)
                return omap_sham_final_shash(req);
        else if (ctx->bufcnt)
                return omap_sham_enqueue(req, OP_FINAL);