CONFIG_CAVIUM_CPT: Cavium Cryptographic Accelerator driver

General informations

The Linux kernel configuration item CONFIG_CAVIUM_CPT:

prompt: Cavium Cryptographic Accelerator driver
type: tristate
depends on: ( CONFIG_ARCH_THUNDER || CONFIG_COMPILE_TEST ) && ( CONFIG_PCI_MSI && CONFIG_64BIT )
defined in drivers/crypto/cavium/cpt/Kconfig
found in Linux kernels: 4.11–4.20, 5.0–5.19, 6.0–6.12
modules built: cptpf, cptvf

Support for Cavium CPT block found in octeon-tx series of processors.

To compile this as a module, choose M here.

Numeric ID (from LKDDb) and names (from pci.ids) of recognized devices:

vendor: 177d ("Cavium, Inc."), device: a040 ("THUNDERX CPT Cryptographic Accelerator")
vendor: 177d ("Cavium, Inc."), device: a040 ("THUNDERX CPT Cryptographic Accelerator")
vendor: 177d ("Cavium, Inc."), device: a041
vendor: 177d ("Cavium, Inc."), device: a041

Raw data from LKDDb:

lkddb module cptpf CONFIG_CAVIUM_CPT : drivers/crypto/cavium/cpt/Kconfig : "Cavium Cryptographic Accelerator driver" # in 4.11–4.20, 5.0–5.19, 6.0–6.12
lkddb module cptvf CONFIG_CAVIUM_CPT : drivers/crypto/cavium/cpt/Kconfig : "Cavium Cryptographic Accelerator driver" # in 4.11–4.20, 5.0–5.19, 6.0–6.12
lkddb pci 177d a040 .... .... ...... : CONFIG_CAVIUM_CPT CONFIG_CRYPTO CONFIG_CRYPTO_DEV_CAVIUM_ZIP CONFIG_CRYPTO_DEV_CPT : drivers/crypto/cavium/cpt/cptpf_main.c # in 4.12–4.20, 5.0–5.19, 6.0–6.12
lkddb pci 177d a040 .... .... ...... : CONFIG_CAVIUM_CPT CONFIG_CRYPTO CONFIG_CRYPTO_DEV_CPT : drivers/crypto/cavium/cpt/cptpf_main.c # in 4.11
lkddb pci 177d a041 .... .... ...... : CONFIG_CAVIUM_CPT CONFIG_CRYPTO CONFIG_CRYPTO_DEV_CAVIUM_ZIP CONFIG_CRYPTO_DEV_CPT : drivers/crypto/cavium/cpt/cptvf_main.c # in 4.12–4.20, 5.0–5.19, 6.0–6.12
lkddb pci 177d a041 .... .... ...... : CONFIG_CAVIUM_CPT CONFIG_CRYPTO CONFIG_CRYPTO_DEV_CPT : drivers/crypto/cavium/cpt/cptvf_main.c # in 4.11

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

Custom Search

Popular queries:

Automatically generated (in year 2024). See also LKDDb sources on GitLab