From: <Hermes.Wu@ite.com.tw>
To: <krzk@kernel.org>
Cc: <mchehab@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <linux-media@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v8 1/2] dt-bindings: media: add ITE IT6625/IT6626 HDMI bridge
Date: Mon, 27 Jul 2026 06:24:45 +0000 [thread overview]
Message-ID: <87eaffcb47b24d9fb48fdca8d5309728@ite.com.tw> (raw)
In-Reply-To: <20260727-brawny-tested-puffin-febfc3@quoll>
Hi krzysztof,
>-----Original Message-----
>From: Krzysztof Kozlowski <krzk@kernel.org>
>Sent: Monday, July 27, 2026 2:19 PM
>To: Hermes Wu (吳佳宏) <Hermes.Wu@ite.com.tw>
>Cc: Mauro Carvalho Chehab <mchehab@kernel.org>; Rob Herring <robh@kernel.org>; Krzysztof Kozlowski <krzk+dt@kernel.org>; Conor Dooley <conor+dt@kernel.org>; linux-media@vger.kernel.org; devicetree@vger.kernel.org; linux-kernel@vger.kernel.org
>Subject: Re: [PATCH v8 1/2] dt-bindings: media: add ITE IT6625/IT6626 HDMI bridge
>
>On Mon, Jul 27, 2026 at 10:28:41AM +0800, Hermes Wu wrote:
>> Document the devicetree binding for the ITE IT6625/IT6626 HDMI to MIPI
>> CSI-2 bridge. The device exposes two graph ports: port@0
>> (MIPI0) and port@1 (MIPI1), the two selectable CSI-2 D-PHY/C-PHY
>> outputs. Only port@0 is required, since a board only needs to wire up
>> as many of the bridge's outputs as it actually uses.
>>
>> Signed-off-by: Hermes Wu <Hermes.wu@ite.com.tw>
>> ---
>> Changes in v8:
>
>Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
>
Thanks for your review.
>Best regards,
>Krzysztof
>
Regards,
Hermes
next prev parent reply other threads:[~2026-07-27 6:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 2:28 [PATCH v8 0/2] media: i2c: add support for ITE IT6625/IT6626 HDMI to MIPI CSI-2 bridge Hermes Wu via B4 Relay
2026-07-27 2:28 ` Hermes Wu
2026-07-27 2:28 ` [PATCH v8 1/2] dt-bindings: media: add ITE IT6625/IT6626 HDMI bridge Hermes Wu via B4 Relay
2026-07-27 2:28 ` Hermes Wu
2026-07-27 2:33 ` sashiko-bot
2026-07-27 6:19 ` Krzysztof Kozlowski
2026-07-27 6:24 ` Hermes.Wu [this message]
2026-07-27 2:28 ` [PATCH v8 2/2] media: i2c: add driver for ITE IT6625/IT6626 Hermes Wu via B4 Relay
2026-07-27 2:28 ` Hermes Wu
2026-07-27 2:38 ` sashiko-bot
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=87eaffcb47b24d9fb48fdca8d5309728@ite.com.tw \
--to=hermes.wu@ite.com.tw \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
/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.