From: "Yan, Dongcheng" <dongcheng.yan@linux.intel.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Bingbu Cao <bingbu.cao@linux.intel.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
"Yan, Dongcheng" <dongcheng.yan@intel.com>
Subject: Re: [PATCH] media: i2c: lt6911uxe: add two selects to Kconfig
Date: Fri, 25 Apr 2025 17:34:48 +0800 [thread overview]
Message-ID: <4db38319-91d4-4f65-9db5-b8b78c40bc69@linux.intel.com> (raw)
In-Reply-To: <fb3799f7-8c32-4c17-8849-039a20ddf000@xs4all.nl>
Hi bingbu,
Hans Verkuil has submitted a fix patch.
And I saw it has merged into linux-next:
<https://web.git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/drivers/media/i2c/Kconfig>
Thanks,
Dongcheng
On 3/19/2025 6:36 PM, Hans Verkuil wrote:
> In order to get the v4l2_subdev functions you need to select
> MEDIA_CONTROLLER and VIDEO_V4L2_SUBDEV_API.
>
> Signed-off-by: Hans Verkuil <hverkuil@xs4all.nl>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202503151002.HacBN2LO-lkp@intel.com/
> Fixes: e49563c3be09 ("media: i2c: add lt6911uxe hdmi bridge driver")
> ---
> drivers/media/i2c/Kconfig | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/media/i2c/Kconfig b/drivers/media/i2c/Kconfig
> index b06365d02ef1..e45ba127069f 100644
> --- a/drivers/media/i2c/Kconfig
> +++ b/drivers/media/i2c/Kconfig
> @@ -1152,6 +1152,8 @@ config VIDEO_LT6911UXE
> depends on ACPI && VIDEO_DEV && I2C
> select V4L2_FWNODE
> select V4L2_CCI_I2C
> + select MEDIA_CONTROLLER
> + select VIDEO_V4L2_SUBDEV_API
> help
> This is a Video4Linux2 sensor-level driver for the Lontium
> LT6911UXE HDMI to MIPI CSI-2 bridge.
next prev parent reply other threads:[~2025-04-25 9:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 10:36 [PATCH] media: i2c: lt6911uxe: add two selects to Kconfig Hans Verkuil
2025-04-25 9:34 ` Yan, Dongcheng [this message]
2025-04-25 9:34 ` Bingbu Cao
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=4db38319-91d4-4f65-9db5-b8b78c40bc69@linux.intel.com \
--to=dongcheng.yan@linux.intel.com \
--cc=arnd@arndb.de \
--cc=bingbu.cao@linux.intel.com \
--cc=dongcheng.yan@intel.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.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