aboutsummaryrefslogtreecommitdiff
path: root/drivers/crypto
AgeCommit message (Collapse)AuthorFilesLines
2014-06-23crypto: qat - Fix build problem with O=Herbert Xu1-1/+1
qat adds -I to the ccflags. Unfortunately it uses CURDIR which breaks when make is invoked with O=. This patch replaces CURDIR with $(src) which should work with/without O=. Signed-off-by: Herbert Xu <[email protected]>
2014-06-20crypto: caam - remove duplicate FIFOST_CONT_MASK defineDan Carpenter1-1/+0
The FIFOST_CONT_MASK define is cut and pasted twice so we can delete the second instance. Signed-off-by: Dan Carpenter <[email protected]> Acked-by: Kim Phillips <[email protected]> Acked-by: Marek Vasut <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-06-20crypto: qat - Update to makefilesTadeusz Struk2-0/+2
Update to makefiles etc. Don't update the firmware/Makefile yet since there is no FW binary in the crypto repo yet. This will be added later. v3 - removed change to ./firmware/Makefile Reviewed-by: Bruce W. Allan <[email protected]> Signed-off-by: Tadeusz Struk <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-06-20crypto: qat - Intel(R) QAT DH895xcc acceleratorTadeusz Struk9-0/+1499
This patch adds DH895xCC hardware specific code. It hooks to the common infrastructure and provides acceleration for crypto algorithms. Acked-by: John Griffin <[email protected]> Reviewed-by: Bruce W. Allan <[email protected]> Signed-off-by: Tadeusz Struk <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-06-20crypto: qat - Intel(R) QAT accelengine part of fw loaderTadeusz Struk3-0/+1605
This patch adds acceleration engine handler part the firmware loader. Acked-by: Bo Cui <[email protected]> Reviewed-by: Bruce W. Allan <[email protected]> Signed-off-by: Karen Xiang <[email protected]> Signed-off-by: Pingchaox Yang <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-06-20crypto: qat - Intel(R) QAT ucode part of fw loaderTadeusz Struk2-0/+1569
This patch adds microcode part of the firmware loader. v4 - splits FW loader part into two smaller patches. Acked-by: Bo Cui <[email protected]> Reviewed-by: Bruce W. Allan <[email protected]> Signed-off-by: Karen Xiang <[email protected]> Signed-off-by: Pingchaox Yang <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-06-20crypto: qat - Intel(R) QAT crypto interfaceTadeusz Struk3-0/+1401
This patch adds qat crypto interface. Acked-by: John Griffin <[email protected]> Reviewed-by: Bruce W. Allan <[email protected]> Signed-off-by: Tadeusz Struk <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-06-20crypto: qat - Intel(R) QAT FW interfaceTadeusz Struk4-0/+1155
This patch adds FW interface structure definitions. Acked-by: John Griffin <[email protected]> Reviewed-by: Bruce W. Allan <[email protected]> Signed-off-by: Tadeusz Struk <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-06-20crypto: qat - Intel(R) QAT transport codeTadeusz Struk5-0/+1204
This patch adds a code that implements communication channel between the driver and the firmware. Acked-by: John Griffin <[email protected]> Reviewed-by: Bruce W. Allan <[email protected]> Signed-off-by: Tadeusz Struk <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-06-20crypto: qat - Intel(R) QAT driver frameworkTadeusz Struk15-0/+2676
This patch adds a common infractructure that will be used by all Intel(R) QuickAssist Technology (QAT) devices. v2 - added ./drivers/crypto/qat/Kconfig and ./drivers/crypto/qat/Makefile v4 - splits common part into more, smaller patches Acked-by: John Griffin <[email protected]> Reviewed-by: Bruce W. Allan <[email protected]> Signed-off-by: Tadeusz Struk <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-06-20crypto: ccp - Add platform device support for arm64Tom Lendacky5-2/+270
Add support for the CCP on arm64 as a platform device. Signed-off-by: Tom Lendacky <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-06-20crypto: ccp - Modify PCI support in prep for arm64 supportTom Lendacky2-27/+15
Modify the PCI device support in prep for supporting the CCP as a platform device for arm64. Signed-off-by: Tom Lendacky <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-06-20crypto: drivers - Add 2 missing __exit_pJean Delvare2-2/+2
References to __exit functions must be wrapped with __exit_p. Signed-off-by: Jean Delvare <[email protected]> Cc: "David S. Miller" <[email protected]> Cc: Robert Jennings <[email protected]> Cc: Marcelo Henrique Cerri <[email protected]> Cc: Fionnuala Gunter <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-06-20crypto: caam - Introduce the use of the managed version of kzallocHimangi Saraogi1-6/+6
This patch moves data allocated using kzalloc to managed data allocated using devm_kzalloc and cleans now unnecessary kfrees in probe and remove functions. Also, linux/device.h is added to make sure the devm_*() routine declarations are unambiguously available. Earlier, in the probe function ctrlpriv was leaked on the failure of ctrl = of_iomap(nprop, 0); as well as on the failure of ctrlpriv->jrpdev = kzalloc(...); . These two bugs have been fixed by the patch. The following Coccinelle semantic patch was used for making the change: identifier p, probefn, removefn; @@ struct platform_driver p = { .probe = probefn, .remove = removefn, }; @prb@ identifier platform.probefn, pdev; expression e, e1, e2; @@ probefn(struct platform_device *pdev, ...) { <+... - e = kzalloc(e1, e2) + e = devm_kzalloc(&pdev->dev, e1, e2) ... ?-kfree(e); ...+> } @rem depends on prb@ identifier platform.removefn; expression e; @@ removefn(...) { <... - kfree(e); ...> } Signed-off-by: Himangi Saraogi <[email protected]> Acked-by: Julia Lawall <[email protected]> Reviewed-by: Marek Vasut <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-06-11crypto/nx: disable NX on little endian buildsAnton Blanchard1-1/+1
The NX driver has endian issues so disable it for now. Signed-off-by: Anton Blanchard <[email protected]> Signed-off-by: Benjamin Herrenschmidt <[email protected]>
2014-06-07Merge git://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6 ↵Linus Torvalds22-428/+582
into next Pull crypto updates from Herbert Xu: "Here is the crypto update for 3.16: - Added test vectors for SHA/AES-CCM/DES-CBC/3DES-CBC. - Fixed a number of error-path memory leaks in tcrypt. - Fixed error-path memory leak in caam. - Removed unnecessary global mutex from mxs-dcp. - Added ahash walk interface that can actually be asynchronous. - Cleaned up caam error reporting. - Allow crypto_user get operation to be used by non-root users. - Add support for SSS module on Exynos. - Misc fixes" * git://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6: (60 commits) crypto: testmgr - add aead cbc des, des3_ede tests crypto: testmgr - Fix DMA-API warning crypto: cesa - tfm->__crt_alg->cra_type directly crypto: sahara - tfm->__crt_alg->cra_name directly crypto: padlock - tfm->__crt_alg->cra_name directly crypto: n2 - tfm->__crt_alg->cra_name directly crypto: dcp - tfm->__crt_alg->cra_name directly crypto: cesa - tfm->__crt_alg->cra_name directly crypto: ccp - tfm->__crt_alg->cra_name directly crypto: geode - Don't use tfm->__crt_alg->cra_name directly crypto: geode - Weed out printk() from probe() crypto: geode - Consistently use AES_KEYSIZE_128 crypto: geode - Kill AES_IV_LENGTH crypto: geode - Kill AES_MIN_BLOCK_SIZE crypto: mxs-dcp - Remove global mutex crypto: hash - Add real ahash walk interface hwrng: n2-drv - Introduce the use of the managed version of kzalloc crypto: caam - reinitialize keys_fit_inline for decrypt and givencrypt crypto: s5p-sss - fix multiplatform build hwrng: timeriomem - remove unnecessary OOM messages ...
2014-05-28crypto/nx/nx-842: dev_set_drvdata can no longer failJean Delvare1-6/+1
Don't check if dev_set_drvdata() failed, it can't, and it returns void now. Signed-off-by: Jean Delvare <[email protected]> Cc: Robert Jennings <[email protected]> Cc: Marcelo Henrique Cerri <[email protected]> Cc: Fionnuala Gunter <[email protected]> Reported-by: Stephen Rothwell <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
2014-05-22crypto: cesa - tfm->__crt_alg->cra_type directlyMarek Vasut1-2/+2
The checking for the type of algorithm implementation is pretty strange here. Use regular flags to check for the type instead. Signed-off-by: Marek Vasut <[email protected]> Cc: Bill Pemberton <[email protected]> Cc: Herbert Xu <[email protected]> Cc: Kent Yoder <[email protected]> Cc: Jamie Iles <[email protected]> Cc: Phil Sutter <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-05-22crypto: sahara - tfm->__crt_alg->cra_name directlyMarek Vasut1-1/+1
Signed-off-by: Marek Vasut <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-05-22crypto: padlock - tfm->__crt_alg->cra_name directlyMarek Vasut1-1/+1
Signed-off-by: Marek Vasut <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-05-22crypto: n2 - tfm->__crt_alg->cra_name directlyMarek Vasut1-2/+2
Signed-off-by: Marek Vasut <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-05-22crypto: dcp - tfm->__crt_alg->cra_name directlyMarek Vasut1-1/+1
Signed-off-by: Marek Vasut <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-05-22crypto: cesa - tfm->__crt_alg->cra_name directlyMarek Vasut1-1/+1
Signed-off-by: Marek Vasut <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-05-22crypto: ccp - tfm->__crt_alg->cra_name directlyMarek Vasut1-2/+2
Signed-off-by: Marek Vasut <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-05-22crypto: geode - Don't use tfm->__crt_alg->cra_name directlyMarek Vasut1-2/+2
Use a standard accessor instead of directly digging into a structure. Signed-off-by: Marek Vasut <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-05-22crypto: geode - Weed out printk() from probe()Marek Vasut1-2/+2
Signed-off-by: Marek Vasut <[email protected]> Cc: Benjamin Herrenschmidt <[email protected]> Cc: Dmitry Kasatkin <[email protected]> Cc: Eric Bénard <[email protected]> Cc: Jussi Kivilinna <[email protected]> Cc: Kent Yoder <[email protected]> Cc: Michal Ludvig <[email protected]> Cc: Varun Wadekar <[email protected]> Cc: Vladimir Zapolskiy <[email protected]> Cc: [email protected] Signed-off-by: Herbert Xu <[email protected]>
2014-05-22crypto: geode - Consistently use AES_KEYSIZE_128Marek Vasut1-3/+1
Consistently use AES_KEYSIZE_128 instead of arbitrary defined value. Signed-off-by: Marek Vasut <[email protected]> Cc: Benjamin Herrenschmidt <[email protected]> Cc: Dmitry Kasatkin <[email protected]> Cc: Eric Bénard <[email protected]> Cc: Jussi Kivilinna <[email protected]> Cc: Kent Yoder <[email protected]> Cc: Michal Ludvig <[email protected]> Cc: Varun Wadekar <[email protected]> Cc: Vladimir Zapolskiy <[email protected]> Cc: [email protected] Signed-off-by: Herbert Xu <[email protected]>
2014-05-22crypto: geode - Kill AES_IV_LENGTHMarek Vasut2-2/+1
The AES IV length is always 128bits, just use the define from aes.h Signed-off-by: Marek Vasut <[email protected]> Cc: Benjamin Herrenschmidt <[email protected]> Cc: Dmitry Kasatkin <[email protected]> Cc: Eric Bénard <[email protected]> Cc: Jussi Kivilinna <[email protected]> Cc: Kent Yoder <[email protected]> Cc: Michal Ludvig <[email protected]> Cc: Varun Wadekar <[email protected]> Cc: Vladimir Zapolskiy <[email protected]> Cc: [email protected] Signed-off-by: Herbert Xu <[email protected]>
2014-05-22crypto: geode - Kill AES_MIN_BLOCK_SIZEMarek Vasut2-10/+9
This is actually defined in include/crypto/aes.h , no need to have a a different symbol for the same thing twice. Signed-off-by: Marek Vasut <[email protected]> Cc: Benjamin Herrenschmidt <[email protected]> Cc: Dmitry Kasatkin <[email protected]> Cc: Eric Bénard <[email protected]> Cc: Jussi Kivilinna <[email protected]> Cc: Kent Yoder <[email protected]> Cc: Michal Ludvig <[email protected]> Cc: Varun Wadekar <[email protected]> Cc: Vladimir Zapolskiy <[email protected]> Cc: [email protected] Signed-off-by: Herbert Xu <[email protected]>
2014-05-22crypto: mxs-dcp - Remove global mutexFabio Estevam1-34/+16
Remove mutex_lock from probe in order to avoid the following warning: [ 8.526613] Freeing unused kernel memory: 232K (c0683000 - c06bd000) starting pid 56, tty '': '/etc/rc.d/rcS' [ 9.110314] [ 9.111864] ===================================== [ 9.116603] [ BUG: init/1 still has locks held! ] [ 9.121488] 3.15.0-rc4-next-20140509-00001-g319564e #1154 Not tainted [ 9.128071] ------------------------------------- [ 9.132825] 1 lock held by init/1: [ 9.136252] #0: (global_mutex){+.+.+.}, at: [<c0387d68>] mxs_dcp_probe+0x14 [ 9.144196] [ 9.144196] stack backtrace: [ 9.148888] CPU: 0 PID: 1 Comm: init Not tainted 3.15.0-rc4-next-20140509-004 [ 9.157610] [<c000da40>] (unwind_backtrace) from [<c000bda4>] (show_stack+0x) [ 9.165595] [<c000bda4>] (show_stack) from [<c00153d4>] (do_fork+0x2c8/0x3cc) [ 9.172921] [<c00153d4>] (do_fork) from [<c0015550>] (sys_vfork+0x20/0x2c) [ 9.179973] [<c0015550>] (sys_vfork) from [<c0009580>] (ret_fast_syscall+0x0) Signed-off-by: Fabio Estevam <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-05-13crypto: caam - reinitialize keys_fit_inline for decrypt and givencryptVakul Garg1-0/+3
Re-initialize keys_fit_inline to avoid using its stale encrypt() shared descriptor value prior to building descriptors for the decrypt() and givencrypt() cases. Signed-off-by: Vakul Garg <[email protected]> [reworded commit text, enhanced code readability] Signed-off-by: Kim Phillips <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-05-13crypto: s5p-sss - fix multiplatform buildArnd Bergmann1-3/+0
As we are preparing to enable multiplatform support on EXYNOS, we can no longer include mach/*.h or plat/*.h headers from device drivers. The s5p-sss driver was just enabled for EXYNOS when it used to be used only on s5pv210, and it includes two samsung platform specific header files for historic reasons. Fortunately, it no longer actually needs them, so we can remove the #includes and avoid the problem Signed-off-by: Arnd Bergmann <[email protected]> Cc: Naveen Krishna Chatradhi <[email protected]> Cc: Tomasz Figa <[email protected]> Cc: <[email protected]> Cc: Vladimir Zapolskiy <[email protected]> Reviewed-by: Jingoo Han <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-05-08crypto: s5p-sss - Look for the next request in the queueNaveen Krishna Chatradhi1-5/+12
Currently, the driver enqueues a request only if the busy bit is false. And every request initiates a dequeue. If 2 requests arrive simultaneously, only one of them will be dequeued. To avoid this senario, we will enqueue the next request irrespective of the system condition (that is what queue is here for). Also schedule at a tasklet immediatly after the current request is done. The tasklet will dequeue the next request in the queue, giving continuous loop. tasklet will exit if there are no requests in the queue. Signed-off-by: Naveen Krishna Chatradhi <[email protected]> CC: David S. Miller <[email protected]> CC: <[email protected]> Acked-by: Vladimir Zapolskiy <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-05-08crypto: s5p-sss - Use clk_prepare/clk_unprepareNaveen Krishna Chatradhi1-3/+7
This patch set adds use of clk_prepare/clk_unprepare as required by generic clock framework. Signed-off-by: Naveen Krishna Chatradhi <[email protected]> Reviewed-by: Tomasz Figa <[email protected]> CC: David S. Miller <[email protected]> CC: <[email protected]> Acked-by: Vladimir Zapolskiy <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-05-08crypto: s5p-sss - validate iv before memcpyNaveen Krishna Chatradhi1-1/+2
This patch adds code to validate "iv" buffer before trying to memcpy the contents Signed-off-by: Naveen Krishna Chatradhi <[email protected]> Reviewed-by: Tomasz Figa <[email protected]> CC: David S. Miller <[email protected]> CC: <[email protected]> Acked-by: Vladimir Zapolskiy <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-05-08crypto: s5p-sss - Let Exynos SoCs select SSS driverNaveen Krishna Chatradhi1-3/+3
This patch modifies Kconfig such that ARCH_EXYNOS SoCs which includes (Exynos4210, Exynos5250 and Exynos5420) can also select Samsung SSS(Security SubSystem) driver. Signed-off-by: Naveen Krishna Chatradhi <[email protected]> Reviewed-by: Tomasz Figa <[email protected]> CC: David S. Miller <[email protected]> CC: <[email protected]> Acked-by: Vladimir Zapolskiy <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-05-08crypto: s5p-sss - Add support for SSS module on ExynosNaveen Krishna Chatradhi1-24/+83
This patch adds new compatible and variant struct to support the SSS module on Exynos4 (Exynos4210), Exynos5 (Exynos5420 and Exynos5250) for which 1. AES register are at an offset of 0x200 and 2. hash interrupt is not available Signed-off-by: Naveen Krishna Chatradhi <[email protected]> Reviewed-by: Tomasz Figa <[email protected]> CC: David S. Miller <[email protected]> CC: <[email protected]> Acked-by: Vladimir Zapolskiy <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-05-08crypto: s5p-sss - Add device tree supportNaveen Krishna Chatradhi1-0/+8
This patch adds device tree support to the s5p-sss.c crypto driver. Signed-off-by: Naveen Krishna Chatradhi <[email protected]> CC: David S. Miller <[email protected]> CC: <[email protected]> Acked-by: Vladimir Zapolskiy <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-05-08crypto: s5p-sss - Use platform_get_irq() instead of _byname()Naveen Krishna Chatradhi1-12/+12
This patch uses the platform_get_irq() instead of the platform_get_irq_byname(). Making feeder control interrupt as resource "0" and hash interrupt as "1". reasons for this change. 1. Cannot find any Arch which is currently using this driver 2. Samsung Exynos4 and 5 SoCs only use the feeder control interrupt 3. Patches adding support for DT and H/W version are in pipeline Signed-off-by: Naveen Krishna Chatradhi <[email protected]> Reviewed-by: Tomasz Figa <[email protected]> CC: David S. Miller <[email protected]> CC: <[email protected]> Acked-by: Vladimir Zapolskiy <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-05-08crypto: caam - Fix the 'quoted string split across lines'Marek Vasut1-59/+18
Fix the checkpatch warnings that the strings were split across multiple lines. Checkpatch now complains about lines over 80, but this is better, since we can actually grep the source code for these strings now. Signed-off-by: Marek Vasut <[email protected]> Cc: Herbert Xu <[email protected]> Cc: Horia Geanta <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-05-08crypto: caam - Sweep the remnantsMarek Vasut1-21/+20
Clean up the remnants from the rework. Constify function arguments. Note that checkpatch again complains about this space before newline, but this is the original code behavior, so I'm keeping it. Signed-off-by: Marek Vasut <[email protected]> Cc: Herbert Xu <[email protected]> Cc: Horia Geanta <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-05-08crypto: caam - Kill SPRINTFCAT() with fireMarek Vasut1-10/+0
This macro is just like an encyclopedia of string handling done wrong. This must die. This is so wrong on so many levels. Signed-off-by: Marek Vasut <[email protected]> Cc: Herbert Xu <[email protected]> Cc: Horia Geanta <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-05-08crypto: caam - Clean up report_deco_status()Marek Vasut1-18/+13
Clean this function up and rework it into sensible shape. This function now contains one single dev_err() instead of the previous insanity full of memory allocation, chaotic string handling and use of SPRINTFCAT(). Signed-off-by: Marek Vasut <[email protected]> Cc: Herbert Xu <[email protected]> Cc: Horia Geanta <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-05-08crypto: caam - Clean up report_ccb_status()Marek Vasut1-25/+20
Clean this function up and rework it into sensible shape. This function now contains one single dev_err() instead of the previous insanity full of memory allocation, possible stack overwriting, chaotic string handling and use of SPRINTFCAT(). Signed-off-by: Marek Vasut <[email protected]> Cc: Herbert Xu <[email protected]> Cc: Horia Geanta <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-05-08crypto: caam - Dissolve report_jump_idx()Marek Vasut1-15/+17
Just dissolve this function so it's not in the way of applying further white magic cleanup down the line. Signed-off-by: Marek Vasut <[email protected]> Cc: Herbert Xu <[email protected]> Cc: Horia Geanta <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-05-08crypto: caam - Kill the easy targetsMarek Vasut1-12/+17
Fix the functions which can be obviously done right with a simple dev_err() now. While at it, further press the on-stack allocation of buffer for sprintf() voodoo down into the abominated functions. This patch cleans up most of the functions and leaves just two remaining functions, report_ccb_status() and report_deco_status() ugly and unhappy. Signed-off-by: Marek Vasut <[email protected]> Cc: Herbert Xu <[email protected]> Cc: Horia Geanta <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-05-08crypto: caam - Pass error type into the functionsMarek Vasut1-10/+21
Pass the error type string into the functions, so they can handle the printing of the string. This is now still using the very unsafe sprintf(), but we will fix that. While at this, pass the device pointer too, so we can dev_err() functions readily when we start fixing this proper. Signed-off-by: Marek Vasut <[email protected]> Cc: Herbert Xu <[email protected]> Cc: Horia Geanta <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-05-08crypto: caam - Implement fast-path for error codes with no handlerMarek Vasut1-2/+10
Implement fast-path error code printout for errors with no associated handler function. This reduces calls to this kmalloc() nonsense in SPRINTFCAT() already. Note that the format of output is compatible with the old code, even if -- exposed like this -- it looks a bit weird. Checkpatch complains on this one as well. Signed-off-by: Marek Vasut <[email protected]> Cc: Herbert Xu <[email protected]> Cc: Horia Geanta <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-05-08crypto: caam - Pull all the error codes outMarek Vasut1-143/+147
Pull the error code <-> error string mapping tables out of the function so the code becomes readable. This lets me see the real flesh of the functions, without all that flab clouding the view. Note: There is a checkpatch issue with quoted strings across multiple lines. I will fix that in a subsequent patch to keep the changes small and separate. Signed-off-by: Marek Vasut <[email protected]> Cc: Herbert Xu <[email protected]> Cc: Horia Geanta <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
2014-05-08crypto: caam - Contain caam_jr_strstatus() uglinessMarek Vasut6-53/+24
The tentacles of this function were firmly attached to various places in the CAAM code. Just cut them, or this cthulhu function will sprout them anew. Signed-off-by: Marek Vasut <[email protected]> Cc: Herbert Xu <[email protected]> Cc: Horia Geanta <[email protected]> Signed-off-by: Herbert Xu <[email protected]>