From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8] crypto: Fix clocks and DMA configuration
Date: Thu, 2 May 2013 11:49:42 +0100 [thread overview]
Message-ID: <1367491790-9727-1-git-send-email-lee.jones@linaro.org> (raw)
This patch-set ensures any clocks that are obtained by the ux500
crypto drivers are prepared for use. We also request DMA channels and
configure them in the correct way using the new dmaengine API.
arch/arm/mach-ux500/board-mop500.c | 14 ++------------
drivers/crypto/ux500/cryp/cryp.h | 7 ++++++-
drivers/crypto/ux500/cryp/cryp_core.c | 31 ++++++++++++++++++++++++++++++-
drivers/crypto/ux500/hash/hash_alg.h | 5 ++++-
drivers/crypto/ux500/hash/hash_core.c | 24 ++++++++++++++++++++++--
5 files changed, 64 insertions(+), 17 deletions(-)
next reply other threads:[~2013-05-02 10:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 10:49 Lee Jones [this message]
2013-05-02 10:49 ` [PATCH 1/8] crypto: ux500/hash - Prepare clock before enabling it Lee Jones
2013-05-08 13:57 ` Ulf Hansson
2013-05-02 10:49 ` [PATCH 2/8] crypto: ux500/hash - Set DMA configuration though dma_slave_config() Lee Jones
2013-05-02 10:49 ` [PATCH 3/8] ARM: ux500: Stop passing Hash DMA channel config information though pdata Lee Jones
2013-05-02 10:49 ` [PATCH 4/8] crypto: ux500/cryp - Prepare clock before enabling it Lee Jones
2013-05-08 13:57 ` Ulf Hansson
2013-05-02 10:49 ` [PATCH 5/8] crypto: ux500/cryp - Set DMA configuration though dma_slave_config() Lee Jones
2013-05-02 10:49 ` [PATCH 6/8] ARM: ux500: Stop passing Cryp DMA channel config information though pdata Lee Jones
2013-05-02 10:49 ` [PATCH 7/8] crypto: ux500/[cryp|hash] - Show successful start-up in the bootlog Lee Jones
2013-05-02 10:49 ` [PATCH 8/8] ARM: ux500: Register Cyrp and Hash platform drivers on Snowball Lee Jones
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=1367491790-9727-1-git-send-email-lee.jones@linaro.org \
--to=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).