[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20181029085629.55exxlamujlyvs3n@linutronix.de>
Date: Mon, 29 Oct 2018 09:56:29 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Horia Geanta <horia.geanta@....com>
Cc: Roy Pledge <roy.pledge@....com>,
Herbert Xu <herbert@...dor.apana.org.au>,
"David S. Miller" <davem@...emloft.net>,
Aymen Sghaier <aymen.sghaier@....com>,
Leo Li <leoyang.li@....com>,
Madalin-cristian Bucur <madalin.bucur@....com>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
"linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] crypto: caam/qi - simplify CGR allocation, freeing
On 2018-10-25 14:05:32 [+0000], Horia Geanta wrote:
> > Now, what is the problem with the CPU limitation? Is this a HW
> > limitation that you can access the registers from a certain CPU?
> >
> Roy confirmed the CPU limitation should actually be removed, there is nothing in
> HW requiring it.
> A clean-up patch will follow.
good. Thank you.
> Thanks,
> Horia
Sebastian
Powered by blists - more mailing lists