From: Herbert Xu <herbert@gondor.apana.org.au>
To: Ruchika Gupta <ruchika.gupta@freescale.com>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
davem@davemloft.net, alexandru.porosanu@freescale.com,
horia.geanta@freescale.com, grant.likely@linaro.org,
NiteshNarayanLal@freescale.com, thierry.reding@gmail.com,
rob.herring@calxeda.com, kim.phillips@freescale.com,
dan.carpenter@oracle.com
Subject: Re: [PATCH] crypto:caam - Configuration for platforms with virtualization enabled in CAAM
Date: Wed, 25 Jun 2014 21:48:08 +0800 [thread overview]
Message-ID: <20140625134808.GB10379@gondor.apana.org.au> (raw)
In-Reply-To: <1403525553-17170-1-git-send-email-ruchika.gupta@freescale.com>
On Mon, Jun 23, 2014 at 05:42:33PM +0530, Ruchika Gupta wrote:
> For platforms with virtualization enabled
>
> 1. The job ring registers can be written to only is the job ring has been
> started i.e STARTR bit in JRSTART register is 1
>
> 2. For DECO's under direct software control, with virtualization enabled
> PL, BMT, ICID and SDID values need to be provided. These are provided by
> selecting a Job ring in start mode whose parameters would be used for the
> DECO access programming.
>
> Signed-off-by: Ruchika Gupta <ruchika.gupta@freescale.com>
Patch applied.
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2014-06-25 13:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 12:12 [PATCH] crypto:caam - Configuration for platforms with virtualization enabled in CAAM Ruchika Gupta
2014-06-25 13:48 ` Herbert Xu [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=20140625134808.GB10379@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=NiteshNarayanLal@freescale.com \
--cc=alexandru.porosanu@freescale.com \
--cc=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=grant.likely@linaro.org \
--cc=horia.geanta@freescale.com \
--cc=kim.phillips@freescale.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=ruchika.gupta@freescale.com \
--cc=thierry.reding@gmail.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 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).