From: "Cabiddu, Giovanni" <giovanni.cabiddu@intel.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jie Wang <jie.wang@intel.com>, <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: Fri, 5 Jan 2024 17:44:15 +0000 [thread overview]
Message-ID: <ZZg/7+7XPXyR06CG@gcabiddu-mobl.ger.corp.intel.com> (raw)
In-Reply-To: <c6662ee1-9c2a-49fb-917f-2a3586f636b4@linux-m68k.org>
Hi Geert,
On Tue, Dec 26, 2023 at 12:31:20PM +0100, Geert Uytterhoeven wrote:
> On Fri, 15 Dec 2023, Jie Wang wrote:
> > --- 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?
Thanks for spotting this.
For this particular device it should be X86_64.
Plug-in cards devices (e.g. DH895xCC), instead, should stay !CPU_BIG_ENDIAN
as they can be used on any little-endian system.
I'm going to send a patch to change this.
--
Giovanni
prev parent reply other threads:[~2024-01-05 17:45 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
2024-01-05 17:44 ` Cabiddu, Giovanni [this message]
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=ZZg/7+7XPXyR06CG@gcabiddu-mobl.ger.corp.intel.com \
--to=giovanni.cabiddu@intel.com \
--cc=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®