From: Arnd Bergmann <arnd@arndb.de>
To: Andrew Bresticker <abrestic@chromium.org>
Cc: James Hartley <james.hartley@imgtec.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
davem@davemloft.net, Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
joe@perches.com, mchehab@osg.samsung.com,
Antti Palosaari <crope@iki.fi>,
jg1.han@samsung.com, linux-crypto@vger.kernel.org,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Ezequiel Garcia <ezequiel.garcia@imgtec.com>
Subject: Re: [PATCH 1/2] crypto: Add Imagination Technologies hw hash accelerator
Date: Sat, 15 Nov 2014 12:08:30 +0100 [thread overview]
Message-ID: <2542656.2ocf2Vp6rc@wuerfel> (raw)
In-Reply-To: <CAL1qeaGN9q_WHP2YJ3fY3r11v0pitcmwbjam5dRzeZhHCp7c8g@mail.gmail.com>
On Friday 14 November 2014 15:59:02 Andrew Bresticker wrote:
> > diff --git a/drivers/crypto/Kconfig b/drivers/crypto/Kconfig
> > index 2fb0fdf..4b931eb 100644
> > --- a/drivers/crypto/Kconfig
> > +++ b/drivers/crypto/Kconfig
> > @@ -436,4 +436,17 @@ config CRYPTO_DEV_QCE
> > hardware. To compile this driver as a module, choose M here. The
> > module will be called qcrypto.
> >
> > +config CRYPTO_DEV_IMGTEC_HASH
> > + tristate "Imagination Technologies hardware hash accelerator"
>
> Is there no meaningful depends-on here? There's no MACH_PISTACHIO
> yet, but perhaps MIPS for now? Also, {readl,writel}_relaxed aren't
> available on all architectures.
>
I've queued up support for {readl,writel}_relaxed on all architectures
for 3.19, based on a series from Will Deacon.
Arnd
next prev parent reply other threads:[~2014-11-15 11:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 12:10 [PATCH 0/2] crypto: Add support for the IMG hash accelerator James Hartley
[not found] ` <1415621455-10468-1-git-send-email-james.hartley-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
2014-11-10 12:10 ` [PATCH 1/2] crypto: Add Imagination Technologies hw " James Hartley
2014-11-10 15:09 ` Vladimir Zapolskiy
2014-11-11 14:59 ` James Hartley
2014-11-11 15:12 ` Vladimir Zapolskiy
2014-11-11 15:28 ` James Hartley
2014-11-14 23:59 ` Andrew Bresticker
2014-11-15 7:55 ` Corentin LABBE
2014-11-17 17:11 ` Andrew Bresticker
2014-11-24 14:39 ` Herbert Xu
2014-11-15 11:08 ` Arnd Bergmann [this message]
2014-11-18 18:16 ` James Hartley
2014-11-10 12:10 ` [PATCH 2/2] Documentation: crypto: Add DT binding info for the img " James Hartley
2014-11-10 17:30 ` Andrew Bresticker
2014-11-18 18:33 ` James Hartley
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=2542656.2ocf2Vp6rc@wuerfel \
--to=arnd@arndb.de \
--cc=abrestic@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=crope@iki.fi \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel.garcia@imgtec.com \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=ijc+devicetree@hellion.org.uk \
--cc=james.hartley@imgtec.com \
--cc=jg1.han@samsung.com \
--cc=joe@perches.com \
--cc=linux-crypto@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@osg.samsung.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).