From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 3/3] omap hw crypto updates for v3.10 merge window
Date: Tue, 2 Apr 2013 10:29:11 -0700 [thread overview]
Message-ID: <mailman.5.1364923763.1198.linux-arm-kernel@lists.infradead.org> (raw)
In-Reply-To: <pull-1364923751-842943>
The following changes since commit 78e52e026d288aad88b46bff0d94b05e145c4583:
ARM: OMAP2+: clock data: Remove CK_* flags (2013-03-18 09:57:39 -0600)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.10/crypto-signed
for you to fetch changes up to f13acab6594451da8b5bd39db0c0513aba592a8d:
Merge tag 'omap-devel-a-for-3.10' of git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending into omap-for-v3.10/crypto (2013-04-01 10:07:28 -0700)
----------------------------------------------------------------
Omap crypto related bus level changes via Paul Walmsley <paul@pwsan.com>:
For OMAP2+ SoCs, convert the SHA/MD5 and AES accelerator integration
code and data to use hwmod and omap_device. This is a prerequisite for
moving the hwmod code out of arch/arm.
Basic test logs are available at:
http://www.pwsan.com/omap/testlogs/sham_aes_integration_devel_3.10/20130330155313/
----------------------------------------------------------------
Mark A. Greer (13):
ARM: OMAP2xxx: hwmod: Convert SHAM crypto device data to hwmod
ARM: OMAP2xxx: hwmod: Add DMA support for SHAM module
ARM: OMAP3xxx: hwmod: Convert SHAM crypto device data to hwmod
ARM: OMAP2+: Remove unnecessary message when no SHA IP is present
ARM: OMAP2+: Only manually add hwmod data when DT not used.
ARM: AM33XX: Add sha0 crypto clock data
ARM: AM33XX: hwmod: Update and uncomment SHA0 module data
ARM: OMAP2xxx: hwmod: Convert AES crypto devcie data to hwmod
ARM: OMAP3xxx: hwmod: Convert AES crypto device data to hwmod
ARM: OMAP2+: Remove unnecessary message when no AES IP is present
ARM: OMAP2+: Only manually add hwmod data when DT not used.
ARM: AM33XX: Add aes0 crypto clock data
ARM: AM33XX: hwmod: Update and uncomment AES0 module data
Tony Lindgren (1):
Merge tag 'omap-devel-a-for-3.10' of git://git.kernel.org/.../pjw/omap-pending into omap-for-v3.10/crypto
arch/arm/mach-omap2/cclock2430_data.c | 4 +-
arch/arm/mach-omap2/cclock33xx_data.c | 10 ++
arch/arm/mach-omap2/cclock3xxx_data.c | 2 +
arch/arm/mach-omap2/devices.c | 149 +++---------------
arch/arm/mach-omap2/omap_hwmod_2420_data.c | 2 +
arch/arm/mach-omap2/omap_hwmod_2430_data.c | 2 +
.../mach-omap2/omap_hwmod_2xxx_interconnect_data.c | 36 +++++
arch/arm/mach-omap2/omap_hwmod_2xxx_ipblock_data.c | 81 ++++++++++
arch/arm/mach-omap2/omap_hwmod_33xx_data.c | 92 +++++++++--
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 172 +++++++++++++++++++--
arch/arm/mach-omap2/omap_hwmod_common_data.h | 4 +
11 files changed, 401 insertions(+), 153 deletions(-)
next prev parent reply other threads:[~2013-04-02 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 17:29 [GIT PULL 1/3] omap non critical fixes for v3.10 merge window Tony Lindgren
2013-04-02 17:29 ` [GIT PULL 2/3] omap cleanup " Tony Lindgren
2013-04-02 17:29 ` Tony Lindgren [this message]
2013-04-08 16:24 ` [GIT PULL 1/3] omap non critical fixes " Arnd Bergmann
2013-04-08 17:06 ` Tony Lindgren
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=mailman.5.1364923763.1198.linux-arm-kernel@lists.infradead.org \
--to=tony@atomide.com \
--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).