From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Frank Li <Frank.Li@nxp.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
"open list:MEDIA INPUT INFRASTRUCTURE (V4L/DVB)"
<linux-media@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
imx@lists.linux.dev
Subject: Re: [PATCH v2 1/1] media: dt-bindings: video-interfaces: add video-interfaces.h information
Date: Sun, 26 Oct 2025 20:49:33 +0200 [thread overview]
Message-ID: <20251026184933.GB1025@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20251021154922.2874390-1-Frank.Li@nxp.com>
Hi Frank,
Thank you for the patch.
On Tue, Oct 21, 2025 at 11:49:22AM -0400, Frank Li wrote:
> Mention include/dt-bindings/media/video-interfaces.h in descriptions to
> help avoid use hardcode in dts.
>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
> ---
> changes in v2
> - update commit message "mention ..."
> - use full path include/dt-bindings/media/video-interfaces.h
> ---
> Documentation/devicetree/bindings/media/video-interfaces.yaml | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/media/video-interfaces.yaml b/Documentation/devicetree/bindings/media/video-interfaces.yaml
> index 038e85b45befa..6ed4695cacf7e 100644
> --- a/Documentation/devicetree/bindings/media/video-interfaces.yaml
> +++ b/Documentation/devicetree/bindings/media/video-interfaces.yaml
> @@ -95,7 +95,7 @@ properties:
> - 6 # BT.656
> - 7 # DPI
I wondered if we should reference the macros here as well:
enum:
- 1 # MEDIA_BUS_TYPE_CSI2_CPHY
- 2 # MEDIA_BUS_TYPE_CSI1
- 3 # MEDIA_BUS_TYPE_CCP2
- 4 # MEDIA_BUS_TYPE_CSI2_DPHY
- 5 # MEDIA_BUS_TYPE_PARALLEL
- 6 # MEDIA_BUS_TYPE_BT656
- 7 # DPI
(Annoyingly we don't have a macro for DPI.)
This can be done separately if desired, so
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> description:
> - Data bus type.
> + Data bus type. See include/dt-bindings/media/video-interfaces.h.
>
> bus-width:
> $ref: /schemas/types.yaml#/definitions/uint32
> @@ -229,7 +229,7 @@ properties:
> Imaging. The length of the array must be the same length as the
> data-lanes property. If the line-orders property is omitted, the value
> shall be interpreted as 0 (ABC). This property is valid for CSI-2 C-PHY
> - busses only.
> + busses only. See include/dt-bindings/media/video-interfaces.h.
>
> strobe:
> $ref: /schemas/types.yaml#/definitions/uint32
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2025-10-26 18:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 15:49 [PATCH v2 1/1] media: dt-bindings: video-interfaces: add video-interfaces.h information Frank Li
2025-10-21 20:17 ` Krzysztof Kozlowski
2025-10-26 18:49 ` Laurent Pinchart [this message]
2025-10-27 8:08 ` Sakari Ailus
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=20251026184933.GB1025@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox