From: <Hermes.Wu@ite.com.tw>
To: <dmitry.baryshkov@oss.qualcomm.com>
Cc: <andrzej.hajda@intel.com>, <neil.armstrong@linaro.org>,
<rfoss@kernel.org>, <Laurent.pinchart@ideasonboard.com>,
<jonas@kwiboo.se>, <jernej.skrabec@gmail.com>,
<airlied@gmail.com>, <simona@ffwll.ch>,
<maarten.lankhorst@linux.intel.com>, <mripard@kernel.org>,
<tzimmermann@suse.de>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <Pet.Weng@ite.com.tw>,
<Kenneth.Hung@ite.com.tw>, <dri-devel@lists.freedesktop.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v4 2/2] drm/bridge: Add ITE IT6162 MIPI DSI to HDMI bridge driver
Date: Mon, 23 Mar 2026 04:46:14 +0000 [thread overview]
Message-ID: <482dc98deded4d26a8084228836c891f@ite.com.tw> (raw)
In-Reply-To: <hylxawutrdmwxem52lyhhprkdm4oc6bnj2w6z5p2e2czvwmhgq@apcxe3lg6kgd>
Hi
>On Thu, Mar 19, 2026 at 02:37:12PM +0800, Hermes Wu via B4 Relay wrote:
>> From: Hermes Wu <Hermes.wu@ite.com.tw>
>>
>> Add support for the ITE IT6162 MIPI DSI to HDMI 2.0 bridge chip.
>> The IT6162 is an I2C-controlled bridge that supports the following
>> configurations:
>>
>> - Single MIPI DSI input: up to 4K @ 30Hz
>> - Dual MIPI DSI input (combined): up to 4K @ 60Hz
>>
>> The driver implements the DRM bridge and connector frameworks,
>> including mode setting, EDID retrieval, and HPD support.
>>
>> Also add a MAINTAINERS entry for the newly introduced ITE IT6162 MIPI
>> DSI to HDMI bridge driver, covering the driver source file and the
>> device tree binding document.
>>
>> Signed-off-by: Hermes Wu <Hermes.wu@ite.com.tw>
>> ---
>> Changes in v4
>> * Drop struc it6162_audio
>> * Add HDCP_AUTO in enum hdcp_ver{}, FW enable HDCP by sink capability.
>> * Call drm_atomic_helper_connector_hdmi_clear_audio_infoframe()
>> in it6162_bridge_hdmi_audio_shutdown()
>> * Drop it6162_bridge_hdmi_audio_startup()
>> * Add hdmi_clear_hdmi_infoframe and hdmi_write_hdmi_infoframe
>> * Drop it6162_parse_dt() due to "ite,support-hdcp" is removed from DT.
>> * Add DRM_BRIDGE_OP_HDMI to it6162->bridge.ops
>>
>
>Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
>
Thank you for reviewing
>--
>With best wishes
>Dmitry
>
prev parent reply other threads:[~2026-03-23 4:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 6:37 [PATCH v4 0/2] Add ITE IT6162 MIPI DSI to HDMI bridge driver Hermes Wu via B4 Relay
2026-03-19 6:37 ` [PATCH v4 1/2] dt-bindings: display: bridge: Add ITE IT6162 MIPI DSI to HDMI bridge Hermes Wu via B4 Relay
2026-03-19 8:56 ` Krzysztof Kozlowski
2026-03-23 4:49 ` Hermes.Wu
2026-03-19 6:37 ` [PATCH v4 2/2] drm/bridge: Add ITE IT6162 MIPI DSI to HDMI bridge driver Hermes Wu via B4 Relay
2026-03-23 3:45 ` Dmitry Baryshkov
2026-03-23 4:46 ` Hermes.Wu [this message]
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=482dc98deded4d26a8084228836c891f@ite.com.tw \
--to=hermes.wu@ite.com.tw \
--cc=Kenneth.Hung@ite.com.tw \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=Pet.Weng@ite.com.tw \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--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=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