Received-SPF: pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Horia Geanta <horia.geanta@nxp.com>
To:     Andrey Smirnov <andrew.smirnov@gmail.com>,
        Vakul Garg <vakul.garg@nxp.com>
CC:     "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
        Chris Healy <cphealy@gmail.com>,
        Lucas Stach <l.stach@pengutronix.de>,
        Herbert Xu <herbert@gondor.apana.org.au>,
        Iuliana Prodan <iuliana.prodan@nxp.com>,
        dl-linux-imx <linux-imx@nxp.com>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/5] CAAM JR lifecycle
Thread-Topic: [PATCH 0/5] CAAM JR lifecycle
Thread-Index: AQHVk+up3U0pU2iIOk61xrvFYlmkIg==
Date:   Wed, 13 Nov 2019 18:57:19 +0000
Message-ID: <VI1PR0402MB34851C1681F8A18341A8971098760@VI1PR0402MB3485.eurprd04.prod.outlook.com>
References: <20191105151353.6522-1-andrew.smirnov@gmail.com>
 <DB7PR04MB4620E3087C59A26B865DEE988B790@DB7PR04MB4620.eurprd04.prod.outlook.com>
 <CAHQ1cqH5hstMwbO1vqOkZ3GVe-j5a+c3TX-yosq-TvuFFxPkHQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
received-spf: None (protection.outlook.com: nxp.com does not designate
 permitted sender hosts)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: c3148436-6cce-49cd-04da-08d7686b4f6e
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Nov 2019 18:57:19.8574
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 686ea1d3-bc2b-4c6f-a92c-d99c5c301635
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: LgnsTArCjVpzgUZTc5HT48ceeS0K/MhoMjnjaPJ5IAqK7xY5Yoxd7gJjQVzx8KdBVRYnJTbUXuC1dZZM5ntICw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0402MB3760
Sender: linux-crypto-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-crypto.vger.kernel.org>
X-Mailing-List: linux-crypto@vger.kernel.org

On 11/6/2019 5:19 PM, Andrey Smirnov wrote:=0A=
> On Tue, Nov 5, 2019 at 11:27 PM Vakul Garg <vakul.garg@nxp.com> wrote:=0A=
>>=0A=
>>=0A=
>>=0A=
>>> -----Original Message-----=0A=
>>> From: linux-crypto-owner@vger.kernel.org <linux-crypto-=0A=
>>> owner@vger.kernel.org> On Behalf Of Andrey Smirnov=0A=
>>> Sent: Tuesday, November 5, 2019 8:44 PM=0A=
>>> To: linux-crypto@vger.kernel.org=0A=
>>> Cc: Andrey Smirnov <andrew.smirnov@gmail.com>; Chris Healy=0A=
>>> <cphealy@gmail.com>; Lucas Stach <l.stach@pengutronix.de>; Horia Geanta=
=0A=
>>> <horia.geanta@nxp.com>; Herbert Xu <herbert@gondor.apana.org.au>;=0A=
>>> Iuliana Prodan <iuliana.prodan@nxp.com>; dl-linux-imx <linux-=0A=
>>> imx@nxp.com>; linux-kernel@vger.kernel.org=0A=
>>> Subject: [PATCH 0/5] CAAM JR lifecycle=0A=
>>>=0A=
>>> Everyone:=0A=
>>>=0A=
>>> This series is a different approach to addressing the issues brought up=
 in=0A=
>>> [discussion]. This time the proposition is to get away from creating pe=
r-JR=0A=
>>> platfrom device, move all of the underlying code into caam.ko and disab=
le=0A=
>>> manual binding/unbinding of the CAAM device via sysfs. Note that this s=
eries=0A=
>>> is a rough cut intented to gauge if this approach could be acceptable f=
or=0A=
>>> upstreaming.=0A=
>>>=0A=
>>> Thanks,=0A=
>>> Andrey Smirnov=0A=
>>>=0A=
>>> [discussion] lore.kernel.org/lkml/20190904023515.7107-13-=0A=
>>> andrew.smirnov@gmail.com=0A=
>>>=0A=
>>> Andrey Smirnov (5):=0A=
>>>   crypto: caam - use static initialization=0A=
>>>   crypto: caam - introduce caam_jr_cbk=0A=
>>>   crypto: caam - convert JR API to use struct caam_drv_private_jr=0A=
>>>   crypto: caam - do not create a platform devices for JRs=0A=
>>>   crypto: caam - disable CAAM's bind/unbind attributes=0A=
>>>=0A=
>>=0A=
>> To access caam jobrings from DPDK (user space drivers), we unbind job-ri=
ng's platform device from the kernel.=0A=
>> What would be the alternate way to enable job ring drivers in user space=
?=0A=
>>=0A=
> =0A=
> Wouldn't either building your kernel with=0A=
> CONFIG_CRYPTO_DEV_FSL_CAAM_JR=3Dn (this series doesn't handle that right=
=0A=
> currently due to being a rough cut) or disabling specific/all JRs via=0A=
> DT accomplish the same goal?=0A=
> =0A=
It's not a 1:1 match, the ability to move a ring to user space / VM etc.=0A=
*dynamically* goes away.=0A=
=0A=
Horia=0A=