From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Iwona Winiarska <iwona.winiarska@intel.com>,
Jason M Bills <jason.m.bills@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Joel Stanley <joel@jms.id.au>,
Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>
Cc: openbmc@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [PATCH] peci: PECI should depend on ARCH_ASPEED
Date: Tue, 29 Mar 2022 11:21:37 +0200 [thread overview]
Message-ID: <f7ea35c723da72a89028da5b976ad417fbd7bf52.1648545587.git.geert@linux-m68k.org> (raw)
The Platform Environment Control Interface (PECI) is only available on
Baseboard Management Controllers (BMC) for Intel processors. Currently
the only supported BMCs are ASpeed BMC SoCs. Hence add a dependency on
ARCH_ASPEED, to prevent asking the user about the PECI subsystem when
configuring a kernel without ASpeed SoC support.
Fixes: 6523d3b2ffa238ac ("peci: Add core infrastructure")
Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
---
drivers/peci/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/peci/Kconfig b/drivers/peci/Kconfig
index 89872ad833201510..0d3ef8ba0998d649 100644
--- a/drivers/peci/Kconfig
+++ b/drivers/peci/Kconfig
@@ -2,6 +2,7 @@
menuconfig PECI
tristate "PECI support"
+ depends on ARCH_ASPEED || COMPILE_TEST
help
The Platform Environment Control Interface (PECI) is an interface
that provides a communication channel to Intel processors and
--
2.25.1
next reply other threads:[~2022-03-29 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 9:21 Geert Uytterhoeven [this message]
2022-03-29 10:33 ` Greg Kroah-Hartman
2022-03-29 17:08 ` Patrick Williams
2022-03-30 10:37 ` Winiarska, Iwona
2022-03-30 11:51 ` Geert Uytterhoeven
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=f7ea35c723da72a89028da5b976ad417fbd7bf52.1648545587.git.geert@linux-m68k.org \
--to=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=iwona.winiarska@intel.com \
--cc=jae.hyun.yoo@linux.intel.com \
--cc=jason.m.bills@linux.intel.com \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=pierre-louis.bossart@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®