From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas@monjalon.net>
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com
 [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 71F192BD2
 for <dev@dpdk.org>; Mon, 23 Apr 2018 09:57:45 +0200 (CEST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
 by mailout.nyi.internal (Postfix) with ESMTP id CC87B21AEC;
 Mon, 23 Apr 2018 03:57:43 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162])
 by compute1.internal (MEProxy); Mon, 23 Apr 2018 03:57:43 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h=
 cc:content-transfer-encoding:content-type:date:from:in-reply-to
 :message-id:mime-version:references:subject:to:x-me-sender
 :x-me-sender:x-sasl-enc; s=mesmtp; bh=+BLgBl4KUff9HfwPETqURpCrTs
 c3w3SYe4xrOwA8s38=; b=nqobUwHEB0EE3MFSe6YyCaobM94uqwDVJuIGQXit8D
 R7pEyKbmQdxnLDDblh08PG/PLGu2s/2ks4AQXIQwykMQ533EEx3FsSFYLwzts1Og
 F8VNKiXh6Ek6Npu7D5MJYDWBHzXgRyOALYL5ulvtRVxBpDoB76aVSMSox3VllMtV
 8=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
 messagingengine.com; h=cc:content-transfer-encoding:content-type
 :date:from:in-reply-to:message-id:mime-version:references
 :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=+BLgBl
 4KUff9HfwPETqURpCrTsc3w3SYe4xrOwA8s38=; b=Q4y8sY7Imk98MA4EOrXGar
 /GntnzNiiupcNPPHnwUjH50IjQGBxvAOzSGY6ZaBxlwOzknKxzhhDqKUtgsLuaQC
 gpC/RXV/0EasX04ob5Jwe6QjtQO5+GNY702O3IK6XD5QBPKQTUXtuhhz1awl2HeU
 89d3+qpXGgXFh6hoUsbl3Y0RvWXPMJ9QKiQG6PwCGgSiNxQVuT67qX+KZ3A2gNAK
 YG/Gph+hmWwbDo0xjsq7oxsuXu41r8Z7jFKlNej1a1Nim/ucGcZhsLT4WzoAMyb0
 vB9U/O6hHgVEdGaoqspQLT3VoHs4ptphf4pAbWH0bEDQCL37vIzmk5Sb3F66duDg
 ==
X-ME-Sender: <xms:95HdWpOtR4JM0JkcjXEmSnnYlhy4MU72yV8x0XgyfEVfHvGbhscihA>
Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184])
 by mail.messagingengine.com (Postfix) with ESMTPA id 0D88FE43E8;
 Mon, 23 Apr 2018 03:57:42 -0400 (EDT)
From: Thomas Monjalon <thomas@monjalon.net>
To: "Kumar, Ravi1" <Ravi1.Kumar@amd.com>
Cc: "pablo.de.lara.guarch@intel.com" <pablo.de.lara.guarch@intel.com>,
 "dev@dpdk.org" <dev@dpdk.org>,
 "hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>
Date: Mon, 23 Apr 2018 09:57:41 +0200
Message-ID: <2364264.3iAuRLQE6r@xps>
In-Reply-To: <CY4PR12MB15098125824708FE0C63B8E6AE890@CY4PR12MB1509.namprd12.prod.outlook.com>
References: <1520584520-130522-1-git-send-email-Ravi1.kumar@amd.com>
 <1612190.ovG0FycYX0@xps>
 <CY4PR12MB15098125824708FE0C63B8E6AE890@CY4PR12MB1509.namprd12.prod.outlook.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [dpdk-dev] [PATCH v5 01/19] crypto/ccp: add AMD ccp skeleton PMD
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Apr 2018 07:57:45 -0000

23/04/2018 08:37, Kumar, Ravi1:
> >Hi,
> >
> >19/03/2018 13:23, Ravi Kumar:
> >> --- a/config/common_base
> >> +++ b/config/common_base
> >> @@ -529,6 +529,11 @@ CONFIG_RTE_LIBRTE_PMD_CRYPTO_SCHEDULER_DEBUG=n
> >>  CONFIG_RTE_LIBRTE_PMD_NULL_CRYPTO=y
> >>  
> >>  #
> >> +# Compile PMD for AMD CCP crypto device # CONFIG_RTE_LIBRTE_PMD_CCP=n
> >
> >Why is it disabled by default?
> >
> Hi Thomas,
> 
> The CCP HW crypto engines are available only on specific AMD platforms.
> That is why we let the user decide when to enable.

Most of the devices are not always available,
but they are enabled by default.

Can we enable this one from the first patch?