From: Sen Wang <sen@ti.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: <ple@baylibre.com>, <neil.armstrong@linaro.org>,
<andrzej.hajda@intel.com>, <rfoss@kernel.org>,
<Laurent.pinchart@ideasonboard.com>, <jonas@kwiboo.se>,
<jernej.skrabec@gmail.com>, <devarsht@ti.com>, <s-jain1@ti.com>,
<j-sahu@ti.com>, <dri-devel@lists.freedesktop.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/bridge: ite-it66121: Disable HDMI audio capture stream
Date: Mon, 16 Mar 2026 12:05:06 -0500 [thread overview]
Message-ID: <27a87cb1-d3f0-4e95-8fd1-9d49bf435a85@ti.com> (raw)
In-Reply-To: <unsq4jrmlmwmkh4l6yz3vpmzifqpfxcafluawnxwxixuxg2mcf@gpou5yjbyc62>
On 3/13/26 20:59, Dmitry Baryshkov wrote:
> On Thu, Mar 12, 2026 at 02:33:55PM -0500, Sen Wang wrote:
>> The IT66121 is an HDMI transmitter and does not support audio capture.
>> However, the driver registers hdmi-codec without setting no_i2s_capture,
>> causing the codec to advertise a non-functional capture stream. Userspace
>> audio servers such as PulseAudio then attempt to open this capture
>> device, resulting in errors.
>>
>> Set no_i2s_capture and no_spdif_capture in hdmi_codec_pdata so that the
>> hdmi-codec driver only registers playback, matching the actual hardware
>> capability.
>
> As you hopefully have the hardware, can I suggest instead porting the
> driver to HDMI helpers and HDMI audio helpers? The
> drm_connector_hdmi_audio_init() already sets thesse flags for you.
>
Hi Dmitry,
Thanks for your feedback. I dug the code base a little bit more, and I
sure can try to convert the legacy hdmi_codec_ops related APIs to the
newer hdmi_audio funcs and test it out. Hopefully there won't be any
regressions by this conversion.
Looks like I just need the following new drm_bridge_funcs:
.hdmi_audio_startup
.hdmi_audio_prepare
.hdmi_audio_shutdown
.hdmi_audio_mute_stream.
Please let me know if there's anything else to consider for the
conversion, I'll take a stab at it and send a separate patch.
Best Regards,
Sen Wang
>>
>> Signed-off-by: Sen Wang <sen@ti.com>
>> ---
>> drivers/gpu/drm/bridge/ite-it66121.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/bridge/ite-it66121.c b/drivers/gpu/drm/bridge/ite-it66121.c
>> index 329fa47a5701..a1b2c3d4e5f6 100644
>> --- a/drivers/gpu/drm/bridge/ite-it66121.c
>> +++ b/drivers/gpu/drm/bridge/ite-it66121.c
>> @@ -1476,6 +1476,8 @@ static int it66121_audio_codec_init(struct it66121_ctx *ctx, struct device *dev)
>> .i2s = 1, /* Only i2s support for now */
>> .spdif = 0,
>> .max_i2s_channels = 8,
>> + .no_i2s_capture = 1,
>> + .no_spdif_capture = 1,
>> .no_capture_mute = 1,
>> };
>>
>> --
>> 2.34.1
>
prev parent reply other threads:[~2026-03-16 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 19:33 Sen Wang
2026-03-14 1:59 ` Dmitry Baryshkov
2026-03-16 17:05 ` Sen Wang [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=27a87cb1-d3f0-4e95-8fd1-9d49bf435a85@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®