All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Fernandes <joelf@ti.com>
To: "Mark A. Greer" <mgreer@animalcreek.com>
Cc: Benoit Cousson <bcousson@baylibre.com>,
	Lokesh Vutla <lokeshvutla@ti.com>, Paul Walmsley <paul@pwsan.com>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/2] ARM: dts: Add SHAM and AES DT information
Date: Fri, 23 Aug 2013 11:53:50 -0500	[thread overview]
Message-ID: <5217939E.40903@ti.com> (raw)
In-Reply-To: <20130822212402.GA30504@animalcreek.com>

On 08/22/2013 04:24 PM, Mark A. Greer wrote:
> On Thu, Aug 22, 2013 at 10:34:06AM +0200, Benoit Cousson wrote:
>> Hi Lokesh,
>>
>> On 22/08/2013 05:50, Lokesh Vutla wrote:
>>> Hi Benoit,
>>> On Wednesday 21 August 2013 07:11 PM, Benoit Cousson wrote:
>>>> Hi Mark,
>>>>
>>>> In fact I cannot even apply these patches since they are referring the the edma controller node that does not seem to be there in 3.11-rc6.
>>>>
>>>> Is this EDMA series supposed to be merged for 3.12? If this is the case, where can I find a reference GIT for it?
>>> The following EDMA support dt patch series from Joel is needed :
>>> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg92176.html
>>> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg92177.html
>>
>> Thanks, it works a little bit better with these patches :-)
> 
> Yeah, sorry.
> 
> Given Mark Rutland's comments in another email, let me respin and send v3.
> I'll put a comment about the dependencies this time.

Just sanity tested these patches on v3.11-rc6 too.

Drivers register successfully after passing the boot crypto testmgr tests.

bash-4.2# cat /proc/crypto | grep -i omap
driver       : ctr-aes-omap
driver       : cbc-aes-omap
driver       : ecb-aes-omap
driver       : omap-hmac-sha256
driver       : omap-hmac-sha224
driver       : omap-sha256
driver       : omap-sha224
driver       : omap-hmac-md5
driver       : omap-hmac-sha1
driver       : omap-md5
driver       : omap-sha1


Thanks,

-Joel

WARNING: multiple messages have this Message-ID (diff)
From: joelf@ti.com (Joel Fernandes)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] ARM: dts: Add SHAM and AES DT information
Date: Fri, 23 Aug 2013 11:53:50 -0500	[thread overview]
Message-ID: <5217939E.40903@ti.com> (raw)
In-Reply-To: <20130822212402.GA30504@animalcreek.com>

On 08/22/2013 04:24 PM, Mark A. Greer wrote:
> On Thu, Aug 22, 2013 at 10:34:06AM +0200, Benoit Cousson wrote:
>> Hi Lokesh,
>>
>> On 22/08/2013 05:50, Lokesh Vutla wrote:
>>> Hi Benoit,
>>> On Wednesday 21 August 2013 07:11 PM, Benoit Cousson wrote:
>>>> Hi Mark,
>>>>
>>>> In fact I cannot even apply these patches since they are referring the the edma controller node that does not seem to be there in 3.11-rc6.
>>>>
>>>> Is this EDMA series supposed to be merged for 3.12? If this is the case, where can I find a reference GIT for it?
>>> The following EDMA support dt patch series from Joel is needed :
>>> http://www.mail-archive.com/linux-omap at vger.kernel.org/msg92176.html
>>> http://www.mail-archive.com/linux-omap at vger.kernel.org/msg92177.html
>>
>> Thanks, it works a little bit better with these patches :-)
> 
> Yeah, sorry.
> 
> Given Mark Rutland's comments in another email, let me respin and send v3.
> I'll put a comment about the dependencies this time.

Just sanity tested these patches on v3.11-rc6 too.

Drivers register successfully after passing the boot crypto testmgr tests.

bash-4.2# cat /proc/crypto | grep -i omap
driver       : ctr-aes-omap
driver       : cbc-aes-omap
driver       : ecb-aes-omap
driver       : omap-hmac-sha256
driver       : omap-hmac-sha224
driver       : omap-sha256
driver       : omap-sha224
driver       : omap-hmac-md5
driver       : omap-hmac-sha1
driver       : omap-md5
driver       : omap-sha1


Thanks,

-Joel

  reply	other threads:[~2013-08-23 16:54 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-17 16:23 [PATCH v2 0/2] ARM: dts: Add SHAM and AES DT information Mark A. Greer
2013-07-17 16:23 ` Mark A. Greer
2013-07-17 16:23 ` [PATCH v2 1/2] ARM: dts: Add SHAM data and documentation for AM33XX Mark A. Greer
2013-07-17 16:23   ` Mark A. Greer
2013-08-22 14:08   ` Mark Rutland
2013-08-22 14:08     ` Mark Rutland
2013-07-17 16:23 ` [PATCH v2 2/2] ARM: dts: Add AES " Mark A. Greer
2013-07-17 16:23   ` Mark A. Greer
2013-08-21  0:13 ` [PATCH v2 0/2] ARM: dts: Add SHAM and AES DT information Paul Walmsley
2013-08-21  0:13   ` Paul Walmsley
2013-08-21 13:31   ` Benoit Cousson
2013-08-21 13:31     ` Benoit Cousson
2013-08-21 13:41     ` Benoit Cousson
2013-08-21 13:41       ` Benoit Cousson
2013-08-21 20:31       ` Mark A. Greer
2013-08-21 20:31         ` Mark A. Greer
2013-08-22  3:50       ` Lokesh Vutla
2013-08-22  3:50         ` Lokesh Vutla
2013-08-22  8:34         ` Benoit Cousson
2013-08-22  8:34           ` Benoit Cousson
2013-08-22  8:54           ` Lokesh Vutla
2013-08-22  8:54             ` Lokesh Vutla
2013-08-22 21:24           ` Mark A. Greer
2013-08-22 21:24             ` Mark A. Greer
2013-08-23 16:53             ` Joel Fernandes [this message]
2013-08-23 16:53               ` Joel Fernandes
2013-08-21 20:40     ` Mark A. Greer
2013-08-21 20:40       ` Mark A. Greer

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=5217939E.40903@ti.com \
    --to=joelf@ti.com \
    --cc=bcousson@baylibre.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=lokeshvutla@ti.com \
    --cc=mgreer@animalcreek.com \
    --cc=paul@pwsan.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.