From: Bingbu Cao <bingbu.cao@linux.intel.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>, linux-media@vger.kernel.org
Cc: tian.shu.qiu@intel.com, antti.laakso@linux.intel.com,
mehdi.djait@linux.intel.com
Subject: Re: [PATCH v4 11/14] media: ipu6: Obtain unique source pad from remote sub-device
Date: Thu, 8 Jan 2026 16:20:24 +0800 [thread overview]
Message-ID: <e40726ad-36e6-56e1-ba40-8ec589a17f65@linux.intel.com> (raw)
In-Reply-To: <20260108081712.543704-12-sakari.ailus@linux.intel.com>
Reviewed-by: Bingbu Cao <bingbu.cao@intel.com>
On 1/8/26 4:17 PM, Sakari Ailus wrote:
> Obtain unique source pad from a remote sub-device, instead of the first
> one. This means that only one link may be active at stream start. There's
> no functional change in practice, unless multiple CSI-2 transmitters are
> directly connected to the receiver.
>
> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> ---
> drivers/media/pci/intel/ipu6/ipu6-isys-video.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/media/pci/intel/ipu6/ipu6-isys-video.c b/drivers/media/pci/intel/ipu6/ipu6-isys-video.c
> index 54d861aca008..1d58e321bda7 100644
> --- a/drivers/media/pci/intel/ipu6/ipu6-isys-video.c
> +++ b/drivers/media/pci/intel/ipu6/ipu6-isys-video.c
> @@ -1204,10 +1204,10 @@ int ipu6_isys_setup_video(struct ipu6_isys_video *av,
>
> remote_sd = media_entity_to_v4l2_subdev(remote_pad->entity);
> asd = to_ipu6_isys_subdev(remote_sd);
> - source_pad = media_pad_remote_pad_first(&remote_pad->entity->pads[0]);
> - if (!source_pad) {
> + source_pad = media_pad_remote_pad_unique(&remote_pad->entity->pads[0]);
> + if (IS_ERR(source_pad)) {
> dev_dbg(dev, "No external source entity\n");
> - return -ENODEV;
> + return PTR_ERR(source_pad);
> }
>
> *source_entity = source_pad->entity;
>
--
Best regards,
Bingbu Cao
next prev parent reply other threads:[~2026-01-08 8:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 8:16 [PATCH v4 00/14] IPU6 driver cleanups and fixes Sakari Ailus
2026-01-08 8:16 ` [PATCH v4 01/14] media: ipu6: Ensure stream_mutex is acquired when dealing with node list Sakari Ailus
2026-01-08 8:16 ` [PATCH v4 02/14] media: ipu6: Drop MMU hardware initialisation in probe() Sakari Ailus
2026-01-08 8:16 ` Bingbu Cao
2026-01-08 8:17 ` [PATCH v4 03/14] media: ipu6: Remove redundant driver data checks Sakari Ailus
2026-01-08 8:17 ` Bingbu Cao
2026-01-08 8:17 ` [PATCH v4 04/14] media: ipu6: Make symbols static Sakari Ailus
2026-01-08 8:17 ` Bingbu Cao
2026-01-08 8:17 ` [PATCH v4 05/14] media: ipu6: Remove redundant streaming start via buffer queueing Sakari Ailus
2026-01-08 8:17 ` [PATCH v4 06/14] media: ipu6: Don't check pipeline in stream_start Sakari Ailus
2026-01-08 8:17 ` Bingbu Cao
2026-01-08 8:17 ` [PATCH v4 07/14] media: ipu6: Close firmware streams on streaming enable failure Sakari Ailus
2026-01-08 8:18 ` Bingbu Cao
2026-01-08 8:17 ` [PATCH v4 08/14] media: ipu6: Always close firmware stream Sakari Ailus
2026-01-08 8:19 ` Bingbu Cao
2026-01-08 8:17 ` [PATCH v4 09/14] media: ipu6: Drop error argument from ipu6_isys_stream_start() Sakari Ailus
2026-01-08 8:19 ` Bingbu Cao
2026-01-08 8:17 ` [PATCH v4 10/14] media: ipu6: Obtain remote pad using media_pad_remote_pad_unique() Sakari Ailus
2026-01-08 8:20 ` Bingbu Cao
2026-01-08 8:17 ` [PATCH v4 11/14] media: ipu6: Obtain unique source pad from remote sub-device Sakari Ailus
2026-01-08 8:20 ` Bingbu Cao [this message]
2026-01-08 12:28 ` Mehdi Djait
2026-01-08 12:36 ` Sakari Ailus
2026-01-08 8:17 ` [PATCH v4 12/14] media: ipu6: Remove source_entity from struct ipu6_isys_stream Sakari Ailus
2026-01-08 8:17 ` [PATCH v4 13/14] media: ipu6: Drop custom functions to obtain sd state information Sakari Ailus
2026-01-08 8:22 ` Bingbu Cao
2026-01-08 8:17 ` [PATCH v4 14/14] media: ipu6: Always call video_device_pipeline_alloc_start() Sakari Ailus
2026-01-08 12:44 ` [PATCH v4 00/14] IPU6 driver cleanups and fixes Mehdi Djait
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=e40726ad-36e6-56e1-ba40-8ec589a17f65@linux.intel.com \
--to=bingbu.cao@linux.intel.com \
--cc=antti.laakso@linux.intel.com \
--cc=linux-media@vger.kernel.org \
--cc=mehdi.djait@linux.intel.com \
--cc=sakari.ailus@linux.intel.com \
--cc=tian.shu.qiu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox