From: "Horia Geantă" <horia.geanta@nxp.com> To: Herbert Xu <herbert@gondor.apana.org.au> Cc: "David S. Miller" <davem@davemloft.net>, Dan Douglass <dan.douglass@nxp.com>, Tudor Ambarus <tudor-dan.ambarus@nxp.com>, "Cristian Stoica" <cristian.stoica@nxp.com>, <linux-crypto@vger.kernel.org> Subject: [PATCH 00/12] crypto: caam - fixes Date: Fri, 10 Feb 2017 14:07:13 +0200 [thread overview] Message-ID: <1486728445-13047-1-git-send-email-horia.geanta@nxp.com> (raw) This batch consists mostly of DMA API related fixes and simplifications. Since no no arch calls: dma_debug_add_bus(&platform_bus_type); DMA API debugging does not have the chance to report leaks when modules are removed. I am not sure why dma_debug_add_bus() is not used for the platform bus, however when I did that for testing purposes, I could notice quite a few problems in caam driver. Thanks, Horia Horia Geantă (11): crypto: caam - don't include unneeded headers crypto: caam - check return code of dma_set_mask_and_coherent() crypto: caam - fix HW S/G in ablkcipher_giv_edesc_alloc() crypto: caam - check sg_count() return value crypto: caam - replace sg_count() with sg_nents_for_len() crypto: caam - use dma_map_sg() return code crypto: caam - don't dma_map key for hash algorithms crypto: caam - fix DMA API leaks for multiple setkey() calls crypto: caam - fix error path for ctx_dma mapping failure crypto: caam - abstract ahash request double buffering crypto: caam - fix state buffer DMA (un)mapping Tudor Ambarus (1): crypto: caam - fix JR IO mapping if one fails drivers/crypto/caam/caamalg.c | 589 ++++++++++++++++----------------------- drivers/crypto/caam/caamhash.c | 268 +++++++++--------- drivers/crypto/caam/ctrl.c | 33 ++- drivers/crypto/caam/error.c | 2 - drivers/crypto/caam/jr.c | 19 +- drivers/crypto/caam/sg_sw_sec4.h | 11 - 6 files changed, 407 insertions(+), 515 deletions(-) -- 2.4.4
next reply other threads:[~2017-02-10 12:07 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-02-10 12:07 Horia Geantă [this message] 2017-02-10 12:07 ` [PATCH 01/12] crypto: caam - don't include unneeded headers Horia Geantă 2017-02-10 12:07 ` [PATCH 02/12] crypto: caam - check return code of dma_set_mask_and_coherent() Horia Geantă 2017-02-10 12:07 ` [PATCH 03/12] crypto: caam - fix JR IO mapping if one fails Horia Geantă 2017-02-10 12:07 ` [PATCH 04/12] crypto: caam - fix HW S/G in ablkcipher_giv_edesc_alloc() Horia Geantă 2017-02-10 12:07 ` [PATCH 05/12] crypto: caam - check sg_count() return value Horia Geantă 2017-02-10 12:07 ` [PATCH 06/12] crypto: caam - replace sg_count() with sg_nents_for_len() Horia Geantă 2017-02-10 12:07 ` [PATCH 07/12] crypto: caam - use dma_map_sg() return code Horia Geantă 2017-02-10 12:07 ` [PATCH 08/12] crypto: caam - don't dma_map key for hash algorithms Horia Geantă 2017-02-10 12:07 ` [PATCH 09/12] crypto: caam - fix DMA API leaks for multiple setkey() calls Horia Geantă 2017-02-10 12:07 ` [PATCH 10/12] crypto: caam - fix error path for ctx_dma mapping failure Horia Geantă 2017-02-10 12:07 ` [PATCH 11/12] crypto: caam - abstract ahash request double buffering Horia Geantă 2017-02-10 12:07 ` [PATCH 12/12] crypto: caam - fix state buffer DMA (un)mapping Horia Geantă 2017-02-15 5:33 ` [PATCH 00/12] crypto: caam - fixes Herbert Xu
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=1486728445-13047-1-git-send-email-horia.geanta@nxp.com \ --to=horia.geanta@nxp.com \ --cc=cristian.stoica@nxp.com \ --cc=dan.douglass@nxp.com \ --cc=davem@davemloft.net \ --cc=herbert@gondor.apana.org.au \ --cc=linux-crypto@vger.kernel.org \ --cc=tudor-dan.ambarus@nxp.com \ --subject='Re: [PATCH 00/12] crypto: caam - fixes' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).