From: "Wang, Sen" <sen@ti.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: "ple@baylibre.com" <ple@baylibre.com>,
"neil.armstrong@linaro.org" <neil.armstrong@linaro.org>,
"andrzej.hajda@intel.com" <andrzej.hajda@intel.com>,
"rfoss@kernel.org" <rfoss@kernel.org>,
"Laurent.pinchart@ideasonboard.com"
<Laurent.pinchart@ideasonboard.com>,
"jonas@kwiboo.se" <jonas@kwiboo.se>,
"jernej.skrabec@gmail.com" <jernej.skrabec@gmail.com>,
"Thakkar, Devarsh" <devarsht@ti.com>,
"Jain, Swamil" <s-jain1@ti.com>,
"SAHU, JEEVAN KUMAR" <j-sahu@ti.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] drm/bridge: ite-it66121: Convert to DRM HDMI Audio Helper
Date: Sun, 10 May 2026 23:26:47 -0500 [thread overview]
Message-ID: <e1e88498-8734-41b9-b565-a7477d3385c0@ti.com> (raw)
In-Reply-To: <kbv3s76q3i4aal7jp5cbjlgned34lztxo3irqxf65mw5pwm2jy@kc362d22y5pu>
On 5/8/2026 6:58 AM, Dmitry Baryshkov wrote:
> On Wed, Mar 18, 2026 at 10:46:36AM -0500, Sen Wang wrote:
>> Convert the IT66121 HDMI bridge driver from manually registering an
>> hdmi-codec platform device to using the DRM HDMI Audio Helper framework
>> via DRM_BRIDGE_OP_HDMI_AUDIO instead.
>>
>
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
>
> Also, if you have HW documentation for the bridge, would you consider
> implementing infoframes support? As another followup, would you consider
> switching the driver to drm_hdmi_acr_get_n_cts()?
>
Hi Dmitry, thanks for the review and suggestions!
I need to double-check if I have the VSI spec, but I can certainly give
it a try, looks like both AVI and n_cts can receive some refactoring
help like you mentioned. I'll send out separate patch(s) if it pans out.
Best,
Sen Wang
next prev parent reply other threads:[~2026-05-11 4:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 15:46 Sen Wang
2026-05-07 20:38 ` Wang, Sen
2026-05-08 11:58 ` Dmitry Baryshkov
2026-05-11 4:26 ` Wang, Sen [this message]
2026-05-18 10:29 ` Javier Martinez Canillas
2026-05-18 10:37 ` Javier Martinez Canillas
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=e1e88498-8734-41b9-b565-a7477d3385c0@ti.com \
--to=sen@ti.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=andrzej.hajda@intel.com \
--cc=devarsht@ti.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=j-sahu@ti.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=ple@baylibre.com \
--cc=rfoss@kernel.org \
--cc=s-jain1@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®