From: Romain Gantois <romain.gantois@bootlin.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Felix Gu <ustc.gu@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Romain Gantois <romain.gantois@bootlin.com>
Subject: [PATCH RESEND v2 1/3] misc: ti_fpc202: Depend on GPIOLIB instead of selecting it
Date: Wed, 25 Mar 2026 10:54:31 +0100 [thread overview]
Message-ID: <20260325-fpc202-leds-v2-1-a2f4da739b92@bootlin.com> (raw)
In-Reply-To: <20260325-fpc202-leds-v2-0-a2f4da739b92@bootlin.com>
Selecting a foreign subsystem such as GPIOLIB may lead to dependency loops.
Use a "depends on" instead.
Signed-off-by: Romain Gantois <romain.gantois@bootlin.com>
---
drivers/misc/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
index 5cc79d1517af5..dcb36e39d7079 100644
--- a/drivers/misc/Kconfig
+++ b/drivers/misc/Kconfig
@@ -116,7 +116,7 @@ config RPMB
config TI_FPC202
tristate "TI FPC202 Dual Port Controller"
depends on I2C
- select GPIOLIB
+ depends on GPIOLIB
select I2C_ATR
help
If you say yes here you get support for the Texas Instruments FPC202
--
2.53.0
next prev parent reply other threads:[~2026-03-25 9:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 9:54 [PATCH RESEND v2 0/3] misc: ti_fpc202: Add LED support Romain Gantois
2026-03-25 9:54 ` Romain Gantois [this message]
2026-03-25 9:54 ` [PATCH RESEND v2 2/3] dt-bindings: misc: Describe FPC202 LED features Romain Gantois
2026-03-25 17:17 ` Rob Herring
2026-03-25 9:54 ` [PATCH RESEND v2 3/3] misc: ti_fpc202: Support special-purpose GPIO lines with " Romain Gantois
2026-03-25 10:31 ` [PATCH RESEND v2 0/3] misc: ti_fpc202: Add LED support Arnd Bergmann
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=20260325-fpc202-leds-v2-1-a2f4da739b92@bootlin.com \
--to=romain.gantois@bootlin.com \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=ustc.gu@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®