From: Jai Luthra <jai.luthra@ideasonboard.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>
Cc: Devarsh Thakkar <devarsht@ti.com>,
Rishikesh Donadkar <r-donadkar@ti.com>,
Vaishnav Achath <vaishnav.a@ti.com>,
Changhuang Liang <changhuang.liang@starfivetech.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Jai Luthra <jai.luthra@ideasonboard.com>,
Yemike Abhilash Chandra <y-abhilashchandra@ti.com>
Subject: [PATCH v3 4/6] media: cadence: csi2rx: Implement get_fwnode_pad op
Date: Thu, 26 Jun 2025 18:06:09 -0700 [thread overview]
Message-ID: <20250626-probe_fixes-v3-4-83e735ae466e@ideasonboard.com> (raw)
In-Reply-To: <20250626-probe_fixes-v3-0-83e735ae466e@ideasonboard.com>
Use v4l2_subdev_get_fwnode_pad_1_to_1() as the get_fwnode_pad operation.
Cadence CSI2RX maps port numbers and pad indices 1:1.
Reviewed-by: Changhuang Liang <changhuang.liang@starfivetech.com>
Reviewed-by: Devarsh Thakkar <devarsht@ti.com>
Tested-by: Yemike Abhilash Chandra <y-abhilashchandra@ti.com> (on SK-AM68)
Signed-off-by: Jai Luthra <jai.luthra@ideasonboard.com>
---
drivers/media/platform/cadence/cdns-csi2rx.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/platform/cadence/cdns-csi2rx.c b/drivers/media/platform/cadence/cdns-csi2rx.c
index cebcae196eeccc65548d2c8e14bcba4799415beb..608298c72462031515d9ad01c6b267bf7375a5bf 100644
--- a/drivers/media/platform/cadence/cdns-csi2rx.c
+++ b/drivers/media/platform/cadence/cdns-csi2rx.c
@@ -479,6 +479,7 @@ static const struct v4l2_subdev_internal_ops csi2rx_internal_ops = {
static const struct media_entity_operations csi2rx_media_ops = {
.link_validate = v4l2_subdev_link_validate,
+ .get_fwnode_pad = v4l2_subdev_get_fwnode_pad_1_to_1,
};
static int csi2rx_async_bound(struct v4l2_async_notifier *notifier,
--
2.49.0
next prev parent reply other threads:[~2025-06-27 1:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 1:06 [PATCH v3 0/6] media: ti, cdns: Multiple pixel support and misc fixes Jai Luthra
2025-06-27 1:06 ` [PATCH v3 1/6] media: ti: j721e-csi2rx: Use devm_of_platform_populate Jai Luthra
2025-06-27 1:06 ` [PATCH v3 2/6] media: ti: j721e-csi2rx: Use fwnode_get_named_child_node Jai Luthra
2025-06-27 1:06 ` [PATCH v3 3/6] media: ti: j721e-csi2rx: Fix source subdev link creation Jai Luthra
2025-06-27 1:06 ` Jai Luthra [this message]
2025-06-27 1:06 ` [PATCH v3 5/6] media: cadence: cdns-csi2rx: Support multiple pixels per clock cycle Jai Luthra
2025-07-01 3:59 ` kernel test robot
2025-06-27 1:06 ` [PATCH v3 6/6] media: ti: j721e-csi2rx: Support multiple pixels per clock Jai Luthra
2025-08-12 6:19 ` [PATCH v3 0/6] media: ti, cdns: Multiple pixel support and misc fixes Rishikesh Donadkar
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=20250626-probe_fixes-v3-4-83e735ae466e@ideasonboard.com \
--to=jai.luthra@ideasonboard.com \
--cc=changhuang.liang@starfivetech.com \
--cc=devarsht@ti.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mripard@kernel.org \
--cc=r-donadkar@ti.com \
--cc=sakari.ailus@linux.intel.com \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=vaishnav.a@ti.com \
--cc=y-abhilashchandra@ti.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®