All of lore.kernel.org
 help / color / mirror / Atom feed
From: bingbu.cao@intel.com
To: linux-media@vger.kernel.org, sakari.ailus@linux.intel.com,
	hidenorik@chromium.org
Cc: bingbu.cao@intel.com, bingbu.cao@linux.intel.com
Subject: [PATCH] media: intel/ipu6: set the bus_info of the v4l2_capability
Date: Wed, 12 Feb 2025 15:53:14 +0800	[thread overview]
Message-ID: <20250212075314.2291135-1-bingbu.cao@intel.com> (raw)

From: Bingbu Cao <bingbu.cao@intel.com>

IPU6 isys driver missed setting the bus_info of its v4l2_capability.
`v4l2-ctl --all` cannot show the bus_info. This patch copy the bus_info
from the media device to fill the v4l2_capability.

Fixes: 3c1dfb5a69cf ("media: intel/ipu6: input system video nodes and buffer queues")
Signed-off-by: Hidenori Kobayashi <hidenorik@chromium.org>
Signed-off-by: Bingbu Cao <bingbu.cao@intel.com>
---
 drivers/media/pci/intel/ipu6/ipu6-isys-video.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/media/pci/intel/ipu6/ipu6-isys-video.c b/drivers/media/pci/intel/ipu6/ipu6-isys-video.c
index 387963529adb..3ca3f44da387 100644
--- a/drivers/media/pci/intel/ipu6/ipu6-isys-video.c
+++ b/drivers/media/pci/intel/ipu6/ipu6-isys-video.c
@@ -146,6 +146,8 @@ static int ipu6_isys_vidioc_querycap(struct file *file, void *fh,
 
 	strscpy(cap->driver, IPU6_ISYS_NAME, sizeof(cap->driver));
 	strscpy(cap->card, av->isys->media_dev.model, sizeof(cap->card));
+	strscpy(cap->bus_info, av->isys->media_dev.bus_info,
+		sizeof(cap->bus_info));
 
 	return 0;
 }
-- 
2.34.1


             reply	other threads:[~2025-02-12  7:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-12  7:53 bingbu.cao [this message]
2025-02-12  8:25 ` [PATCH] media: intel/ipu6: set the bus_info of the v4l2_capability Sakari Ailus
2025-02-12  9:14   ` Bingbu Cao
2025-02-12  9:20     ` Bingbu Cao
2025-02-12  9:39       ` Sakari Ailus
2025-02-12 11:14         ` 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=20250212075314.2291135-1-bingbu.cao@intel.com \
    --to=bingbu.cao@intel.com \
    --cc=bingbu.cao@linux.intel.com \
    --cc=hidenorik@chromium.org \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.