From: "Rob Herring (Arm)" <robh@kernel.org>
To: Yemike Abhilash Chandra <y-abhilashchandra@ti.com>
Cc: laurent.pinchart@ideasonboard.com, hverkuil@xs4all.nl,
krzk+dt@kernel.org, hansg@kernel.org, dongcheng.yan@intel.com,
u-kumar1@ti.com, linux-kernel@vger.kernel.org,
mchehab@kernel.org, tomi.valkeinen@ideasonboard.com,
linux-media@vger.kernel.org, sakari.ailus@linux.intel.com,
benjamin.mugnier@foss.st.com, conor+dt@kernel.org,
ribalda@chromium.org, git@apitzsch.eu, jai.luthra@linux.dev,
devicetree@vger.kernel.org, mehdi.djait@linux.intel.com,
vladimir.zapolskiy@linaro.org
Subject: Re: [PATCH V3 1/4] media: dt-bindings: ti,ds90ub960: Refactor port definitions
Date: Mon, 29 Dec 2025 17:54:57 -0600 [thread overview]
Message-ID: <176705249711.2817246.10046046202740276325.robh@kernel.org> (raw)
In-Reply-To: <20251219122955.2078270-2-y-abhilashchandra@ti.com>
On Fri, 19 Dec 2025 17:59:52 +0530, Yemike Abhilash Chandra wrote:
> The current bindings duplicate the port definitions for each FPD-Link RX
> and CSI-2 TX ports. This results in a large amount of repeated schema
> blocks and makes it harder to extend the bindings for new devices.
>
> Refactor the bindings by introducing shared deftinitions for FPD-Link
> input ports and CSI-2 output ports. No functional change intended.
>
> Signed-off-by: Yemike Abhilash Chandra <y-abhilashchandra@ti.com>
> ---
> Changelog:
> Changes in v3:
> - Remove the | character from the ports description since preserving formatting is not required. (Rob)
> - Wrap the ports description at 80 characters. (Rob)
>
> .../bindings/media/i2c/ti,ds90ub960.yaml | 120 +++++++-----------
> 1 file changed, 44 insertions(+), 76 deletions(-)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2025-12-29 23:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 12:29 [PATCH V3 0/4] Add support for DS90UB954-Q1 Yemike Abhilash Chandra
2025-12-19 12:29 ` [PATCH V3 1/4] media: dt-bindings: ti,ds90ub960: Refactor port definitions Yemike Abhilash Chandra
2025-12-22 10:55 ` Tomi Valkeinen
2025-12-29 23:54 ` Rob Herring (Arm) [this message]
2025-12-19 12:29 ` [PATCH V3 2/4] media: i2c: ds90ub960: Use enums for chip type and chip family Yemike Abhilash Chandra
2025-12-22 10:46 ` Tomi Valkeinen
2026-01-06 11:26 ` Jai Luthra
2025-12-19 12:29 ` [PATCH V3 3/4] media: dt-bindings: ti,ds90ub960: Add support for DS90UB954-Q1 Yemike Abhilash Chandra
2025-12-22 11:29 ` Tomi Valkeinen
2026-01-06 10:06 ` Yemike Abhilash Chandra
2026-01-23 9:54 ` Tomi Valkeinen
2025-12-29 23:58 ` Rob Herring (Arm)
2025-12-19 12:29 ` [PATCH V3 4/4] media: i2c: ds90ub960: " Yemike Abhilash Chandra
2025-12-22 10:46 ` Tomi Valkeinen
2026-01-06 11:34 ` Jai Luthra
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=176705249711.2817246.10046046202740276325.robh@kernel.org \
--to=robh@kernel.org \
--cc=benjamin.mugnier@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dongcheng.yan@intel.com \
--cc=git@apitzsch.eu \
--cc=hansg@kernel.org \
--cc=hverkuil@xs4all.nl \
--cc=jai.luthra@linux.dev \
--cc=krzk+dt@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mehdi.djait@linux.intel.com \
--cc=ribalda@chromium.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=u-kumar1@ti.com \
--cc=vladimir.zapolskiy@linaro.org \
--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®