linux-kernel - Re: [PATCH] crypto: caam - Dynamic allocation of addresses for various memory blocks in CAAM.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 15 Sep 2014 19:46:44 +0800
From:	Herbert Xu <herbert@...dor.apana.org.au>
To:	Nitesh Narayan Lal <b44382@...escale.com>
Cc:	linux-crypto@...r.kernel.org, vakul@...escale.com,
	davem@...emloft.net, alexandru.porosanu@...escale.com,
	horia.geanta@...escale.com, kim.phillips@...escale.com,
	dan.carpenter@...cle.com, linux-kernel@...r.kernel.org,
	Ruchika Gupta <r66431@...escale.com>
Subject: Re: [PATCH] crypto: caam - Dynamic allocation of addresses for
 various memory blocks in CAAM.

On Mon, Sep 01, 2014 at 03:00:44PM +0530, Nitesh Narayan Lal wrote:
> CAAM's memory is broken into following address blocks:
> Block           Included Registers
> 0               General Registers
> 1-4             Job ring registers
> 6               RTIC registers
> 7               QI registers
> 8               DECO and CCB
> 
> Size of the above stated blocks varies in various platforms. The block size can be 4K or 64K.
> The block size can be dynamically determined by reading CTPR register in CAAM.
> This patch initializes the block addresses dynamically based on the value read from this register.
> 
> Signed-off-by: Ruchika Gupta <r66431@...escale.com>
> Signed-off-by: Nitesh Narayan Lal <b44382@...escale.com>

Patch applied.  Thanks!
-- 
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/