LKML Archive on
help / color / mirror / Atom feed
From: Geert Uytterhoeven <>
To: Gilad Ben-Yossef <>
Cc: Herbert Xu <>,
	"David S . Miller" <>,
	Arnd Bergmann <>,
	Linux Crypto Mailing List <>,
	Linux kernel mailing list <>
Subject: Re: [PATCH/RFC] crypto: Add platform dependencies for CRYPTO_DEV_CCREE
Date: Mon, 23 Apr 2018 10:11:14 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Gilad,

On Mon, Apr 23, 2018 at 9:45 AM, Gilad Ben-Yossef <> wrote:
> On Wed, Apr 18, 2018 at 10:47 AM, Geert Uytterhoeven
> <> wrote:
>> On Wed, Apr 18, 2018 at 6:32 AM, Gilad Ben-Yossef <> wrote:
>>> On Tue, Apr 17, 2018 at 9:14 PM, Geert Uytterhoeven
>>> <> wrote:
>>>> The ARM TrustZone CryptoCell is found on ARM SoCs only.  Hence make it
>>>> depend on ARM or ARM64, unless compile-testing.
>>> Actually it is not. Despite what the name suggest, CryptoCell is
>>> designed by Arm but is
>>> not in fact limited to Arm cores. I think the only requirement is
>>> ability to provide an AMBA bus
>>> interface. Kudos to our marketing department to make that so clear and
>>> so on... :-)
>> Good to know, I couldn't find any users of the compatible value in DT sources,
>> so I had to guess... and missed ;-)
> Yes, the original driver that went through staging was for CC 712,
> which so new it doesn't yet
> have a commercially available silicon yet :-)
> I've added the older 710 and 613 support just recently and will be
> working with CC hardware implementors
> to add the relevant DT bindings for their respective SoCs
>> Do you have a good suggestion for a platform dependency?
>> Based on the above, I'd say "depends on ARM_AMBA || COMPILE_TEST",
>> but (currently) ARM_AMBA is selected on ARM or ARM64 only?
> So AMBA *as a system bus* is not strictly needed AFAIK in the sense
> that you just need
> an AMBA to whatever bus interface, so not all system implementing this
> actually define ARM_AMBA.


> It's actually safer for me to rule out certain architectures rather
> than point to which are used.
> I'd say ruling out s390, um, alpha, ia64 and m68k is a safe bet.
> Do you want to send a patch or shall I?

Please send a patch, thanks!

(I don't want to be the one adding more negative architecture dependencies ;-)



Geert Uytterhoeven -- There's lots of Linux beyond ia32 --

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

      reply	other threads:[~2018-04-23  8:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-17 18:14 Geert Uytterhoeven
2018-04-17 19:53 ` Arnd Bergmann
2018-04-18  7:43   ` Geert Uytterhoeven
2018-04-18  4:32 ` Gilad Ben-Yossef
2018-04-18  7:47   ` Geert Uytterhoeven
2018-04-23  7:45     ` Gilad Ben-Yossef
2018-04-23  8:11       ` Geert Uytterhoeven [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \ \ \ \
    --subject='Re: [PATCH/RFC] crypto: Add platform dependencies for CRYPTO_DEV_CCREE' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).