From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH v5 01/19] crypto/ccp: add AMD ccp skeleton PMD
Date: Mon, 23 Apr 2018 09:57:41 +0200
Message-ID: <2364264.3iAuRLQE6r@xps>
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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
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>
To: "Kumar, Ravi1" <Ravi1.Kumar@amd.com>
Return-path: <dev-bounces@dpdk.org>
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)
In-Reply-To: <CY4PR12MB15098125824708FE0C63B8E6AE890@CY4PR12MB1509.namprd12.prod.outlook.com>
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>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

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?