On 9/30/17 3:30 AM, Borislav Petkov wrote: ...
> From: Borislav Petkov <b...@suse.de> > > This is AMD-specific hardware so present it in Kconfig only when AMD > CPU support is enabled. > > Signed-off-by: Borislav Petkov <b...@suse.de> > Cc: Brijesh Singh <brijesh.si...@amd.com> > Cc: Tom Lendacky <thomas.lenda...@amd.com> > Cc: Gary Hook <gary.h...@amd.com> > Cc: Herbert Xu <herb...@gondor.apana.org.au> > Cc: "David S. Miller" <da...@davemloft.net> > Cc: linux-cry...@vger.kernel.org > --- > drivers/crypto/ccp/Kconfig | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/crypto/ccp/Kconfig b/drivers/crypto/ccp/Kconfig > index 627f3e61dcac..f58a6521270b 100644 > --- a/drivers/crypto/ccp/Kconfig > +++ b/drivers/crypto/ccp/Kconfig > @@ -1,5 +1,6 @@ > config CRYPTO_DEV_CCP_DD > tristate "Secure Processor device driver" > + depends on CPU_SUP_AMD Please note that ccp.ko is built on both x86 and aarch64 (AMD Seattle) architectures. I have not looked into details but I thought CPU_SUP_AMD is x64 specific config. I will look into it and verify that we don't break AMD Seattle platform builds. > default m > help > Provides AMD Secure Processor device driver.
