From: Anoob Joseph <anoobj@marvell.com>
To: Akhil Goyal <gakhil@marvell.com>,
Thomas Monjalon <thomas@monjalon.net>,
Ali Alnubani <alialnu@mellanox.com>,
David Marchand <david.marchand@redhat.com>
Cc: Anoob Joseph <anoobj@marvell.com>,
Jerin Jacob <jerinj@marvell.com>,
"Ankur Dwivedi" <adwivedi@marvell.com>,
Tejasree Kondoj <ktejasree@marvell.com>, <dev@dpdk.org>
Subject: [dpdk-dev] [PATCH] crypto/cnxk: add PCI ID for cn9k
Date: Fri, 9 Jul 2021 11:58:43 +0530 [thread overview]
Message-ID: <1625812123-802-1-git-send-email-anoobj@marvell.com> (raw)
Add PCI ID for crypo_cn9k PMD.
To avoid conflicting PCI ID in crypto_octeontx2 and
crypto_cn9k PMDs, disable crypto_cn9k PMD when built with
octeontx2 config.
The lack of PCI ID is causing debug build to fail for
crypto_cn9k PMD.
Reported-by: Ali Alnubani <alialnu@mellanox.com>
Suggested-by: David Marchand <david.marchand@redhat.com>
Signed-off-by: Anoob Joseph <anoobj@marvell.com>
---
config/arm/arm64_octeontx2_linux_gcc | 1 +
drivers/crypto/cnxk/cn9k_cryptodev.c | 2 ++
2 files changed, 3 insertions(+)
diff --git a/config/arm/arm64_octeontx2_linux_gcc b/config/arm/arm64_octeontx2_linux_gcc
index 9156ee5..8fbdd38 100644
--- a/config/arm/arm64_octeontx2_linux_gcc
+++ b/config/arm/arm64_octeontx2_linux_gcc
@@ -14,3 +14,4 @@ endian = 'little'
[properties]
platform = 'octeontx2'
+disable_drivers = 'common/cnxk'
diff --git a/drivers/crypto/cnxk/cn9k_cryptodev.c b/drivers/crypto/cnxk/cn9k_cryptodev.c
index e74e739..71d144f 100644
--- a/drivers/crypto/cnxk/cn9k_cryptodev.c
+++ b/drivers/crypto/cnxk/cn9k_cryptodev.c
@@ -21,6 +21,8 @@ uint8_t cn9k_cryptodev_driver_id;
static struct rte_pci_id pci_id_cpt_table[] = {
{
+ RTE_PCI_DEVICE(PCI_VENDOR_ID_CAVIUM,
+ PCI_DEVID_CN9K_RVU_CPT_VF)
},
/* sentinel */
{
--
2.7.4
next reply other threads:[~2021-07-09 6:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 6:28 Anoob Joseph [this message]
2021-07-09 6:30 ` Akhil Goyal
2021-07-09 12:09 ` David Marchand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1625812123-802-1-git-send-email-anoobj@marvell.com \
--to=anoobj@marvell.com \
--cc=adwivedi@marvell.com \
--cc=alialnu@mellanox.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=ktejasree@marvell.com \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).