mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Laight <david.laight.linux@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Alexander Usyskin <alexander.usyskin@intel.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Vitaly Lubart <lubvital@gmail.com>,
	Karol Wachowski <karol.wachowski@linux.intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] issei: INTEL_SSEI should depend on X86
Date: Thu, 27 Aug 2026 09:35:02 +0100	[thread overview]
Message-ID: <20260827093502.23b6b062@pumpkin> (raw)
In-Reply-To: <CAMuHMdWDcfrUM4tKGOO3fHJQ3FnYBu-tPG61BY_069Yv_TxXKw@mail.gmail.com>

On Wed, 26 Aug 2026 16:03:11 +0200
Geert Uytterhoeven <geert@linux-m68k.org> wrote:

> Hi David,
> 
> On Wed, 26 Aug 2026 at 11:08, David Laight <david.laight.linux@gmail.com> wrote:
> > On Thu,  6 Aug 2026 11:46:55 +0200
> > Geert Uytterhoeven <geert+renesas@glider.be> wrote:  
> > > The Intel Silicon Security Engine is only present on systems with Intel
> > > Lunar Lake CPUs.  Hence add a dependency on X86, to prevent asking the
> > > user about this subsystem when configuring a kernel for a non-x86
> > > architecture.  
> >
> > Should it be X86_64 ?  
> 
> I don't know. Can you still run 32-bit kernels on these CPUs?

You should be able to, but there is no need to support new features.

David

> 
> > > --- a/drivers/misc/issei/Kconfig
> > > +++ b/drivers/misc/issei/Kconfig
> > > @@ -2,6 +2,7 @@
> > >  # Copyright (C) 2023-2026 Intel Corporation
> > >  config INTEL_SSEI
> > >       tristate "Intel Silicon Security Engine Interface"
> > > +     depends on X86 || COMPILE_TEST
> > >       help
> > >         The ISSEI (Intel Silicon Security Engine Interface)
> > >         subsystem provides a communication channel between the host and the  
> 
> Gr{oetje,eeting}s,
> 
>                         Geert
> 


      reply	other threads:[~2026-08-27  8:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06  9:46 Geert Uytterhoeven
2026-08-26  6:50 ` Usyskin, Alexander
2026-08-26  9:08 ` David Laight
2026-08-26 14:03   ` Geert Uytterhoeven
2026-08-27  8:35     ` David Laight [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=20260827093502.23b6b062@pumpkin \
    --to=david.laight.linux@gmail.com \
    --cc=alexander.usyskin@intel.com \
    --cc=arnd@arndb.de \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=karol.wachowski@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lubvital@gmail.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®