All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Tero Kristo <t-kristo@ti.com>
Cc: "Sebastian Reichel" <sebastian.reichel@collabora.co.uk>,
	"Paul Walmsley" <paul@pwsan.com>,
	"Benoît Cousson" <bcousson@baylibre.com>,
	"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: Wed, 14 Jun 2017 00:57:51 -0700	[thread overview]
Message-ID: <20170614075750.GG3730@atomide.com> (raw)
In-Reply-To: <027b40b6-1961-275b-7b7e-00a51e86e8f3@ti.com>

* Tero Kristo <t-kristo@ti.com> [170613 07:46]:
> On 13/06/17 17:24, Sebastian Reichel wrote:
> > Hi,
> > 
> > On Tue, Jun 13, 2017 at 04:49:18PM +0300, Tero Kristo wrote:
> > > On 13/06/17 12:28, Sebastian Reichel wrote:
> > > > 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.
> > 
> > Thanks :)
> > 
> > > 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.
> > 
> > There is also a warning printed if DT references a missing hwmod
> > entry (that's how I noticed this in the first place). It's less
> > noisy, though. Since kernel builds and boots with any order and
> > crypto hardware does not work at the moment there is no real
> > problem with bisect. I suggest to merge the DTS patches normally
> > through the separate dt branch.
> 
> Yeah thats actually true also. Up to Tony to decide how he wants to handle
> these. The huge warning is mainly an annoyance.

Applying patches from both Sebastian's and Tero's sets into
split into omap-for-v4.13/dt and omap-for-v4.13/soc-v4 branches.

Thanks,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 0/5] OMAP4: crypto support
Date: Wed, 14 Jun 2017 00:57:51 -0700	[thread overview]
Message-ID: <20170614075750.GG3730@atomide.com> (raw)
In-Reply-To: <027b40b6-1961-275b-7b7e-00a51e86e8f3@ti.com>

* Tero Kristo <t-kristo@ti.com> [170613 07:46]:
> On 13/06/17 17:24, Sebastian Reichel wrote:
> > Hi,
> > 
> > On Tue, Jun 13, 2017 at 04:49:18PM +0300, Tero Kristo wrote:
> > > On 13/06/17 12:28, Sebastian Reichel wrote:
> > > > 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.
> > 
> > Thanks :)
> > 
> > > 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.
> > 
> > There is also a warning printed if DT references a missing hwmod
> > entry (that's how I noticed this in the first place). It's less
> > noisy, though. Since kernel builds and boots with any order and
> > crypto hardware does not work at the moment there is no real
> > problem with bisect. I suggest to merge the DTS patches normally
> > through the separate dt branch.
> 
> Yeah thats actually true also. Up to Tony to decide how he wants to handle
> these. The huge warning is mainly an annoyance.

Applying patches from both Sebastian's and Tero's sets into
split into omap-for-v4.13/dt and omap-for-v4.13/soc-v4 branches.

Thanks,

Tony

  reply	other threads:[~2017-06-14  7:57 UTC|newest]

Thread overview: 22+ 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 ` Sebastian Reichel
2017-06-13  9:28 ` [PATCHv2 1/5] ARM: dts: omap4: Fix aes entry Sebastian Reichel
2017-06-13  9:28   ` 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   ` Sebastian Reichel
2017-06-13  9:28 ` [PATCHv2 3/5] ARM: OMAP4: hwmod data: add aes1 Sebastian Reichel
2017-06-13  9:28   ` Sebastian Reichel
2017-06-13  9:28 ` [RFCv2 4/5] ARM: OMAP4: hwmod data: add aes2 Sebastian Reichel
2017-06-13  9:28   ` Sebastian Reichel
2017-06-13  9:28 ` [PATCHv2 5/5] ARM: OMAP4: hwmod data: add des Sebastian Reichel
2017-06-13  9:28   ` Sebastian Reichel
2017-06-13 13:49 ` [PATCHv2 0/5] OMAP4: crypto support Tero Kristo
2017-06-13 13:49   ` Tero Kristo
2017-06-13 13:49   ` Tero Kristo
2017-06-13 14:24   ` Sebastian Reichel
2017-06-13 14:24     ` Sebastian Reichel
2017-06-13 14:42     ` Tero Kristo
2017-06-13 14:42       ` Tero Kristo
2017-06-13 14:42       ` Tero Kristo
2017-06-14  7:57       ` Tony Lindgren [this message]
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=20170614075750.GG3730@atomide.com \
    --to=tony@atomide.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=t-kristo@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.