From: Randy Dunlap <rdunlap@infradead.org>
To: Arnd Bergmann <arnd@kernel.org>, Lee Jones <lee@kernel.org>,
Pavel Machek <pavel@kernel.org>,
Matthias Fend <matthias.fend@emfend.at>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
"André Apitzsch" <git@apitzsch.eu>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] leds: tps6131x: add V4L2_FLASH_LED_CLASS dependency
Date: Tue, 24 Jun 2025 21:02:25 -0700 [thread overview]
Message-ID: <e99773dd-c49e-4a09-bf2c-dacadfdd1c5b@infradead.org> (raw)
In-Reply-To: <20250620114440.4080938-1-arnd@kernel.org>
On 6/20/25 4:43 AM, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> This driver can optionally use the v4l2_flash infrastructure, but fails to
> link built=in if that is in a loadable module:
>
> ld.lld-21: error: undefined symbol: v4l2_flash_release
>>>> referenced by leds-tps6131x.c:792 (drivers/leds/flash/leds-tps6131x.c:792)
>
> Add the usual Kconfig dependency for it, still allowing it to be built when
> CONFIG_V4L2_FLASH_LED_CLASS is disabled.
>
> Fixes: b338a2ae9b31 ("leds: tps6131x: Add support for Texas Instruments TPS6131X flash LED driver")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
I just made this same patch, so
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Tested-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> drivers/leds/flash/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/leds/flash/Kconfig b/drivers/leds/flash/Kconfig
> index 55ca663ca506..5e08102a6784 100644
> --- a/drivers/leds/flash/Kconfig
> +++ b/drivers/leds/flash/Kconfig
> @@ -136,6 +136,7 @@ config LEDS_TPS6131X
> tristate "LED support for TI TPS6131x flash LED driver"
> depends on I2C && OF
> depends on GPIOLIB
> + depends on V4L2_FLASH_LED_CLASS || !V4L2_FLASH_LED_CLASS
> select REGMAP_I2C
> help
> This option enables support for Texas Instruments TPS61310/TPS61311
--
~Randy
next prev parent reply other threads:[~2025-06-25 4:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 11:43 Arnd Bergmann
2025-06-25 4:02 ` Randy Dunlap [this message]
2025-07-01 13:26 ` (subset) " Lee Jones
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=e99773dd-c49e-4a09-bf2c-dacadfdd1c5b@infradead.org \
--to=rdunlap@infradead.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=git@apitzsch.eu \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=matthias.fend@emfend.at \
--cc=pavel@kernel.org \
/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®