From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Jie Wang <jie.wang@intel.com>
Cc: herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org,
qat-linux@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] crypto: qat - add support for 420xx devices
Date: Tue, 26 Dec 2023 12:31:20 +0100 (CET) [thread overview]
Message-ID: <c6662ee1-9c2a-49fb-917f-2a3586f636b4@linux-m68k.org> (raw)
In-Reply-To: <20231215100147.1703641-6-jie.wang@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2244 bytes --]
Hi Jie,
On Fri, 15 Dec 2023, Jie Wang wrote:
> Add support for 420xx devices by including a new device driver that
> supports such devices, updates to the firmware loader and capabilities.
>
> Compared to 4xxx devices, 420xx devices have more acceleration engines
> (16 service engines and 1 admin) and support the wireless cipher
> algorithms ZUC and Snow 3G.
>
> Signed-off-by: Jie Wang <jie.wang@intel.com>
> Co-developed-by: Dong Xie <dong.xie@intel.com>
> Signed-off-by: Dong Xie <dong.xie@intel.com>
> Reviewed-by: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
Thanks for your patch, which is now commit fcf60f4bcf54952c ("crypto:
qat - add support for 420xx devices") in crypto/master
> --- a/drivers/crypto/intel/qat/Kconfig
> +++ b/drivers/crypto/intel/qat/Kconfig
> @@ -59,6 +59,17 @@ config CRYPTO_DEV_QAT_4XXX
> To compile this as a module, choose M here: the module
> will be called qat_4xxx.
>
> +config CRYPTO_DEV_QAT_420XX
> + tristate "Support for Intel(R) QAT_420XX"
> + depends on PCI && (!CPU_BIG_ENDIAN || COMPILE_TEST)
These dependencies suggest that the QAT_420XX device can be present and
used on any little-endian system that supports PCIe (arm64, MIPS,
PowerPC, RISC-V, ...).
However, [1] says QAT is only present on intel Atom® C5000, P5300, and
P5700 processors, implying the dependency should rather be
depends on PCI && (X86_64 || COMPILE_TEST)
Which one is correct?
[1] https://www.intel.com/content/www/us/en/architecture-and-technology/intel-quick-assist-technology-overview.html
> + select CRYPTO_DEV_QAT
> + help
> + Support for Intel(R) QuickAssist Technology QAT_420xx
> + for accelerating crypto and compression workloads.
> +
> + To compile this as a module, choose M here: the module
> + will be called qat_420xx.
> +
> config CRYPTO_DEV_QAT_DH895xCCVF
> tristate "Support for Intel(R) DH895xCC Virtual Function"
> depends on PCI && (!CPU_BIG_ENDIAN || COMPILE_TEST)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next parent reply other threads:[~2023-12-26 11:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231215100147.1703641-1-jie.wang@intel.com>
[not found] ` <20231215100147.1703641-6-jie.wang@intel.com>
2023-12-26 11:31 ` Geert Uytterhoeven [this message]
2024-01-05 17:44 ` Cabiddu, Giovanni
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=c6662ee1-9c2a-49fb-917f-2a3586f636b4@linux-m68k.org \
--to=geert@linux-m68k.org \
--cc=herbert@gondor.apana.org.au \
--cc=jie.wang@intel.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qat-linux@intel.com \
/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
all inboxes | Powered by JetHome®