From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Zhang, Sonic" <Sonic.Zhang@analog.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
LKML <linux-kernel@vger.kernel.org>,
"uclinux-dist-devel@blackfin.uclinux.org"
<uclinux-dist-devel@blackfin.uclinux.org>
Subject: Re: [PATCH] driver: char: bfin_crc: CRC hardware accelerator driver for BF60x family processors.
Date: Thu, 17 May 2012 06:40:54 -0700 [thread overview]
Message-ID: <20120517134054.GC5380@kroah.com> (raw)
In-Reply-To: <DB904C5425BA6F4E8424B3B51A1414D16F64F85057@NWD2CMBX1.ad.analog.com>
On Thu, May 17, 2012 at 06:55:36AM -0400, Zhang, Sonic wrote:
> Hi Greg,
>
> >-----Original Message-----
> >From: Greg Kroah-Hartman [mailto:gregkh@linuxfoundation.org]
> >Sent: Wednesday, May 16, 2012 8:13 PM
> >To: Zhang, Sonic
> >Cc: Arnd Bergmann; LKML; uclinux-dist-devel@blackfin.uclinux.org
> >Subject: Re: [PATCH] driver: char: bfin_crc: CRC hardware accelerator driver for
> >BF60x family processors.
> >
> >On Wed, May 16, 2012 at 04:26:07PM +0800, sonic.zhang@analog.com wrote:
> >> From: Sonic Zhang <sonic.zhang@analog.com>
> >>
> >> The CRC peripheral is a hardware block used to compute the CRC of the block
> >> of data. This is based on a CRC32 engine which computes the CRC value of 32b
> >> data words presented to it. For data words of < 32b in size, it is the
> >> responsibility of the application to pack the data into 32b data units.
> >>
> >> This driver defines data strcture crc_info and 4 IOCTL interfaces for applciations.
> >> 1) CRC Memory Scan
> >> 2) CRC Memory Transfer
> >> 3) CRC Data Verify
> >> 4) CRC Data Fill
> >>
> >> Signed-off-by: Sonic Zhang <sonic.zhang@analog.com>
> >> ---
> >> drivers/char/Kconfig | 8 +
> >> drivers/char/Makefile | 1 +
> >> drivers/char/bfin_crc.c | 537
> >+++++++++++++++++++++++++++++++++++++++++++++++
> >> 3 files changed, 546 insertions(+), 0 deletions(-)
> >> create mode 100644 drivers/char/bfin_crc.c
> >
> >Why is this a char driver, and not a crypto driver, using the existing
> >crypto userspace api for things like this?
> >
>
> It looks only the CRC memory scan mode can be implemented as a crypto
> ahash driver. The other 3 functions are not supported in the crypto
> framework. I will post a crypto driver for the CRC memory scan mode
> later.
Then why not extend the crypto framework to handle these 3 other
functions?
greg k-h
prev parent reply other threads:[~2012-05-17 13:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 8:26 sonic.zhang
2012-05-16 12:12 ` Greg Kroah-Hartman
2012-05-16 13:39 ` Arnd Bergmann
2012-05-16 14:53 ` Greg Kroah-Hartman
2012-05-16 15:11 ` Arnd Bergmann
2012-05-17 10:55 ` Zhang, Sonic
2012-05-17 13:40 ` Greg Kroah-Hartman [this message]
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=20120517134054.GC5380@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Sonic.Zhang@analog.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=uclinux-dist-devel@blackfin.uclinux.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
Powered by JetHome