Linux cryptographic layer development
 help / color / mirror / Atom feed
From: leroy christophe <christophe.leroy@c-s.fr>
To: Kim Phillips <kim.phillips@freescale.com>
Cc: linux-crypto@vger.kernel.org
Subject: Re: Question about Talitos Linux driver for MPC885
Date: Fri, 23 Nov 2012 17:03:15 +0100	[thread overview]
Message-ID: <50AF9E43.7080409@c-s.fr> (raw)
In-Reply-To: <50AF7F4C.9080704@c-s.fr>

Kim,

Looking once more at talitos.h file, it looks like none of the values 
corresponds to what is in the reference manuals.
But it looks like in the talitos.h it is encoded as if it was with LSB 
first. Hence for instance the TALITOS_MCR_SWR which is 0x01 instead of  
0x01000000.
Then I'm wondering what/where the problem is.

Christophe


Le 23/11/2012 14:51, leroy christophe a écrit :
> Dear Kim,
>
> Thank you for you quick answer.
> I didn't have much time to look at it until this week unfortunatly.
>
> I have some more questions/observations below
>
> Le 26/09/2012 02:47, Kim Phillips a écrit :
>> On Tue, 25 Sep 2012 10:45:17 +0200
>> leroy christophe <christophe.leroy@c-s.fr> wrote:
>>
>>> I'm trying to use the Talitos crypto driver with the MPC885
>>> microcontroller. For the time being, it doesn't work.
>> yes, they're not exactly compatible...
>>
>>> The kernel startup blocks at the test of the DES function.
>>>
>>> I have added the following definition in the DTS file:
>>>
>>>           crypto@20000 {
>>>               compatible = "fsl,sec2.0";
>> interesting, its called "SEC Lite" and its version register does
>> indeed say 2.  I see it has a single channel FIFO instead of a ring,
>> that the SEC v1.x (MPC185) used, so you probably don't have to
>> rewrite talitos_submit.
> Good news, it was also my understanding.
>>
>>>               reg = <0x20000 0x8000>;
>>>               interrupts = <1 1>;
>> I couldn't find the IRQ line in the MPC855RM - if there's no IRQ
>> line, then that's a problem.
> Neither do I on the drawing, however in Table 52-1, there are 3 bits 
> in the CPTR register for defining the interrupt level of the SEC lite, 
> just like you do for the CPM and for the FEC.
> So I believe this should be ok ?
>>
>>>               interrupt-parent = <&PIC>;
>>>               fsl,num-channels = <1>;
>>>               fsl,channel-fifo-len = <24>;
>>>               fsl,exec-units-mask = <0x4c>;
>>>               fsl,descriptor-types-mask = <0x301f>;
>> the descriptor type enumeration isn't uniform across into the mpc8xx
>> SEC version, e.g., the SEC Lite doesn't support the ipsec_esp
>> descriptor type, represented in mpc8xxx SEC versions as the second
>> bit, so this descriptor-types-mask setting should be fixed to at
>> least omit that since the driver checks for, and uses it if
>> available.
>>
>>> Is there anything wrong in what I did ? Or is there something else I
>>> should do ?
>> might want to go through the defines in talitos.h, e.g,
>> TALITOS_MCR_SWR is 0x1 on mpc8xxx vs. 0x10000000 on
>> mpc8xx (I suppose CONFIG_PPC_8xx can be used as the ifdef, btw).
> I'm surprised about this, I didn't check the talitos.h file, but had 
> checked the Reference Manual of the MPC 8272.
> I rechecked yesterday and the SWR bit is at the same place as on the 
> MPC885 which is different from what is defined in talitos.h
>>
>> Descriptor header and pointer formats, along with field locations,
>> sizes, and enumerations may also be different.
>>
>> It also appears the SEC Lite doesn't support scatter-gather tables,
>> which will make performance hurt for fragmented (large) packet sizes.
> Does it mean something has to be modified if the SW ?
>>
>> Kim
>>
> Thanks,
> Christophe

  reply	other threads:[~2012-11-23 16:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-25  8:45 Question about Talitos Linux driver for MPC885 leroy christophe
2012-09-26  0:47 ` Kim Phillips
2012-11-23 13:51   ` leroy christophe
2012-11-23 16:03     ` leroy christophe [this message]
2012-11-27 23:15       ` Kim Phillips
2012-11-27 23:11     ` Kim Phillips
2014-04-14 12:01       ` leroy christophe

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=50AF9E43.7080409@c-s.fr \
    --to=christophe.leroy@c-s.fr \
    --cc=kim.phillips@freescale.com \
    --cc=linux-crypto@vger.kernel.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