From: <Pet.Weng@ite.com.tw>
To: <krzk@kernel.org>, <andrzej.hajda@intel.com>,
<neil.armstrong@linaro.org>, <rfoss@kernel.org>,
<Laurent.pinchart@ideasonboard.com>, <jonas@kwiboo.se>,
<jernej.skrabec@gmail.com>, <maarten.lankhorst@linux.intel.com>,
<mripard@kernel.org>, <tzimmermann@suse.de>, <airlied@gmail.com>,
<simona@ffwll.ch>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>
Cc: <dri-devel@lists.freedesktop.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <Hermes.Wu@ite.com.tw>,
<Kenneth.Hung@ite.com.tw>, <Jau-Chih.Tseng@ite.com.tw>,
<treapking@google.com>, <krzysztof.kozlowski@oss.qualcomm.com>
Subject: RE: [PATCH v7 1/2] dt-binding: display: Add ITE IT61620 MIPI DSI to HDMI bridge
Date: Mon, 16 Mar 2026 03:55:41 +0000 [thread overview]
Message-ID: <15aa9069d5f341eb82815f4b9da54fa0@ite.com.tw> (raw)
In-Reply-To: <21cc3b90-0cd7-421c-914d-30e718558224@kernel.org>
Hi Krzysztof,
>
> On 13/03/2026 07:48, Pet Weng wrote:
> > This chip receives MIPI DSI input and outputs HDMI, and is commonly
> > connected to SoCs via I2C and DSI.
> >
> > Signed-off-by: Pet Weng <pet.weng@ite.com.tw>
> > Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> > ---
> > .../bindings/display/bridge/ite,it61620.yaml | 142 +++++++++++++++++++++
> > 1 file changed, 142 insertions(+)
>
>
> This is almost the same as ite,it6162. Almost the same binding, same
> description. Also google finds nothing for ite,it61620.
>
> Looks like some duplicate and your cover letter does not explain here
> anything.
>
IT61620 is a variant of IT6162.
The main differences are:
- IT61620 supports only a single MIPI DSI input port, while IT6162
supports dual MIPI DSI ports.
- IT61620 does not include the internal MCU present in IT6162.
Because of these architectural differences, IT61620 uses a separate
compatible string even though the external interfaces and bindings
are largely similar.
I will update the binding description and cover letter to clarify
these differences
> Best regards,
> Krzysztof
Best regards,
Pet Weng
next prev parent reply other threads:[~2026-03-16 3:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 6:48 [PATCH v7 0/2] Add ITE IT61620 MIPI DSI to HDMI bridge driver Pet Weng
2026-03-13 6:48 ` [PATCH v7 1/2] dt-binding: display: Add ITE IT61620 MIPI DSI to HDMI bridge Pet Weng
2026-03-14 9:31 ` Krzysztof Kozlowski
2026-03-16 3:55 ` Pet.Weng [this message]
2026-03-13 6:48 ` [PATCH v7 2/2] drm/bridge: Add ITE IT61620 MIPI DSI to HDMI bridge driver Pet Weng
2026-03-14 1:56 ` Dmitry Baryshkov
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=15aa9069d5f341eb82815f4b9da54fa0@ite.com.tw \
--to=pet.weng@ite.com.tw \
--cc=Hermes.Wu@ite.com.tw \
--cc=Jau-Chih.Tseng@ite.com.tw \
--cc=Kenneth.Hung@ite.com.tw \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=treapking@google.com \
--cc=tzimmermann@suse.de \
/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®