All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Emilio López" <emilio@elopez.com.ar>
To: herbert@gondor.apana.org.au, David Miller <davem@davemloft.net>,
	linux-crypto@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Getting started with crypto drivers
Date: Sun, 29 Sep 2013 15:10:27 -0300	[thread overview]
Message-ID: <52486D13.1000800@elopez.com.ar> (raw)

Hello everyone,

I would like to write a driver to support the "Security System" hardware 
block on some Allwinner ARM SoCs. The hardware supports AES, DES, 3DES, 
SHA-1, MD5 and has a PRNG. Data passing is done via two FIFOs. You can 
find some ugly userspace code to calculate a SHA1 hash here, so you can 
get an idea of how it works:

http://git.elopez.com.ar/ss-poc/raw/31c57d893ce8913aa0d87c982f5350433fbe89c7/md5-tool.c

My main issue at the moment is that I do not have any experience working 
with the crypto API, and that I found the documentation on 
Documentation/ lacking for my purposes. I'd be very grateful if you 
could suggest me reading material to understand the "hardware-oriented" 
API better, and if you could point me to good drivers I could use as an 
example when developing my own.

Thanks!

Emilio

WARNING: multiple messages have this Message-ID (diff)
From: "Emilio López" <emilio@elopez.com.ar>
To: herbert@gondor.hengli.com.au, David Miller <davem@davemloft.net>,
	linux-crypto@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Getting started with crypto drivers
Date: Sun, 29 Sep 2013 15:10:27 -0300	[thread overview]
Message-ID: <52486D13.1000800@elopez.com.ar> (raw)

Hello everyone,

I would like to write a driver to support the "Security System" hardware 
block on some Allwinner ARM SoCs. The hardware supports AES, DES, 3DES, 
SHA-1, MD5 and has a PRNG. Data passing is done via two FIFOs. You can 
find some ugly userspace code to calculate a SHA1 hash here, so you can 
get an idea of how it works:

http://git.elopez.com.ar/ss-poc/raw/31c57d893ce8913aa0d87c982f5350433fbe89c7/md5-tool.c

My main issue at the moment is that I do not have any experience working 
with the crypto API, and that I found the documentation on 
Documentation/ lacking for my purposes. I'd be very grateful if you 
could suggest me reading material to understand the "hardware-oriented" 
API better, and if you could point me to good drivers I could use as an 
example when developing my own.

Thanks!

Emilio

             reply	other threads:[~2013-09-29 18:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-29 18:10 Emilio López [this message]
2013-09-29 18:10 ` Getting started with crypto drivers Emilio López

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=52486D13.1000800@elopez.com.ar \
    --to=emilio@elopez.com.ar \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@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 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.