public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH] input: Correct dependencies for CROS_EC_KEYB
Date: Mon, 23 Mar 2026 13:52:56 -0600	[thread overview]
Message-ID: <20260323195256.2363513-1-trini@konsulko.com> (raw)

The CROS_EC_KEYB functionality can only work with CROS_EC enabled, so
express this dependency in Kconfig, for all build phases.

Signed-off-by: Tom Rini <trini@konsulko.com>
---
 drivers/input/Kconfig | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/input/Kconfig b/drivers/input/Kconfig
index 5bf122c55051..df8fbf1551de 100644
--- a/drivers/input/Kconfig
+++ b/drivers/input/Kconfig
@@ -64,7 +64,7 @@ config CPCAP_POWER_BUTTON
 
 config CROS_EC_KEYB
 	bool "Enable Chrome OS EC keyboard support"
-	depends on INPUT
+	depends on INPUT && CROS_EC
 	help
 	  Most ARM Chromebooks use an EC to provide access to the keyboard.
 	  Messages are used to request key scans from the EC and these are
@@ -72,7 +72,7 @@ config CROS_EC_KEYB
 
 config SPL_CROS_EC_KEYB
 	bool "Enable Chrome OS EC keyboard support in SPL"
-	depends on SPL_INPUT
+	depends on SPL_INPUT && SPL_CROS_EC
 	help
 	  Most ARM Chromebooks use an EC to provide access to the keyboard.
 	  Messages are used to request key scans from the EC and these are
@@ -80,7 +80,7 @@ config SPL_CROS_EC_KEYB
 
 config TPL_CROS_EC_KEYB
 	bool "Enable Chrome OS EC keyboard support in TPL"
-	depends on TPL_INPUT
+	depends on TPL_INPUT && TPL_CROS_EC
 	help
 	  Most ARM Chromebooks use an EC to provide access to the keyboard.
 	  Messages are used to request key scans from the EC and these are
-- 
2.43.0


             reply	other threads:[~2026-03-23 19:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23 19:52 Tom Rini [this message]
2026-04-07 19:50 ` [PATCH] input: Correct dependencies for CROS_EC_KEYB Tom Rini

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=20260323195256.2363513-1-trini@konsulko.com \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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