public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tero Kristo <t-kristo@ti.com>
To: "Sebastian Reichel" <sebastian.reichel@collabora.co.uk>,
	"Sebastian Reichel" <sre@kernel.org>,
	"Tony Lindgren" <tony@atomide.com>,
	"Paul Walmsley" <paul@pwsan.com>,
	"Benoît Cousson" <bcousson@baylibre.com>
Cc: Russell King <linux@armlinux.org.uk>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 0/5] OMAP4: crypto support
Date: Tue, 13 Jun 2017 16:49:18 +0300	[thread overview]
Message-ID: <ab778bfd-9397-4cb0-0741-557da57bba83@ti.com> (raw)
In-Reply-To: <20170613092847.16732-1-sebastian.reichel@collabora.co.uk>

On 13/06/17 12:28, Sebastian Reichel wrote:
> Hi,
> 
> This adds crypto support for OMAP4, which was missing for some reason.
> This fixes error about missing hwmod on Droid 4. IP-Cores for AES and
> DES are working according to selftest.
> 
> Changes since PATCHv1:
>   * remove patch adding des_fck to DT
>   * add patch removing aes[12]_fck from DT
>   * add patch renaming hwmod aes to aes1 in DT
>   * update hwmod patches according to feedback from Tero
>   * add patch for aes2 hwmod
> 
> -- Sebastian

I just posted a few extra patches on top of this series, for adding the 
missing dts data for aes2 and adding sham accelerator also. The dts data 
should be applied first if you want to avoid any issues with hwmod core 
complaining about missing DT data, so the sequencing of this series and 
mine need to be done carefully.

The patches themselves in this series look fine now, so:

Acked-by: Tero Kristo <t-kristo@ti.com>

> 
> Sebastian Reichel (5):
>    ARM: dts: omap4: Fix aes entry
>    ARM: dts: omap4.dtsi: remove aes[12]_fck
>    ARM: OMAP4: hwmod data: add aes1
>    ARM: OMAP4: hwmod data: add aes2
>    ARM: OMAP4: hwmod data: add des
> 
>   arch/arm/boot/dts/omap4.dtsi               |   4 +-
>   arch/arm/boot/dts/omap44xx-clocks.dtsi     |  16 -----
>   arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 100 +++++++++++++++++++++++++++++
>   3 files changed, 102 insertions(+), 18 deletions(-)
> 

  parent reply	other threads:[~2017-06-13 13:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13  9:28 [PATCHv2 0/5] OMAP4: crypto support Sebastian Reichel
2017-06-13  9:28 ` [PATCHv2 1/5] ARM: dts: omap4: Fix aes entry Sebastian Reichel
2017-06-13  9:28 ` [PATCHv2 2/5] ARM: dts: omap4.dtsi: remove aes[12]_fck Sebastian Reichel
2017-06-13  9:28 ` [PATCHv2 3/5] ARM: OMAP4: hwmod data: add aes1 Sebastian Reichel
2017-06-13  9:28 ` [RFCv2 4/5] ARM: OMAP4: hwmod data: add aes2 Sebastian Reichel
2017-06-13  9:28 ` [PATCHv2 5/5] ARM: OMAP4: hwmod data: add des Sebastian Reichel
2017-06-13 13:49 ` Tero Kristo [this message]
2017-06-13 14:24   ` [PATCHv2 0/5] OMAP4: crypto support Sebastian Reichel
2017-06-13 14:42     ` Tero Kristo
2017-06-14  7:57       ` 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=ab778bfd-9397-4cb0-0741-557da57bba83@ti.com \
    --to=t-kristo@ti.com \
    --cc=bcousson@baylibre.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=paul@pwsan.com \
    --cc=sebastian.reichel@collabora.co.uk \
    --cc=sre@kernel.org \
    --cc=tony@atomide.com \
    /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