From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: Igor Paunovic <royalnet026@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
linux-media@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, kernel@collabora.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/4] media: synopsys: hdmirx: add HDMI audio capture support
Date: Sat, 25 Jul 2026 20:58:23 +0300 [thread overview]
Message-ID: <e1034df6-3801-424a-ba1e-a03d61b37222@collabora.com> (raw)
In-Reply-To: <CAEWPSH4aB4KZsrLx2TESjPvUG0+A_Z_7uuO=5Rd-VidKU9U3eg@mail.gmail.com>
Hi,
On 7/24/26 02:47, Igor Paunovic wrote:
> Hi Dmitry,
>
> Thank you -- and thank you for reviewing the whole series and testing
> 2/4. It went through a lot of back-and-forth since the RFC, so having
> it land with your Tested-by means a lot.
>
> I'll prepare the follow-ups as separate patches once this series is in:
>
> - The video_device lifetime issue on the V4L2 side (the devm-allocated
> struct with video_device_release_empty that the automated review
> flagged) -- as a standalone fix for the existing driver, since it's
> independent of the audio support.
> - An atomicity fix for the GLOBAL_SWENABLE read-modify-write, now that
> the audio path adds a second writer to that register alongside the
> CEC code.
>
> The repeated-suspend wedge I mentioned in the cover letter I'd rather
> send only once I have a clean, reproducible trigger for it -- it's
> still under investigation and I don't want to send a fix ahead of a
> solid repro.
>
> The dynamic codec registration you suggested (bind on the plug event,
> read the actual wire sample rate and restrict the codec's rate) is the
> direction I'd like to explore after these, once I've looked at what it
> needs from hdmi_codec_ops.
Good plan
RE the sample rate restriction, hdmi_codec_ops has get_eld() that
restricts rate based on HDMI ELD [1]. For RX we could tell the exact
rate to CODEC without ELD or we could generate ELD in the driver, either
way should require extension of CODEC driver with support of RX rate
restriction. This way userspace will see that there is only one rate
available for capture, so it won't be able to choose wrong rate and will
resample audio itself as it needs.
HDMI plug event -> signal stable -> gate audio rate from ACR -> register
CODEC device -> ops.get_eld() returns our ELD
[1]
https://elixir.bootlin.com/linux/v7.1.3/source/sound/soc/codecs/hdmi-codec.c#L477
--
Best regards,
Dmitry
next prev parent reply other threads:[~2026-07-25 17:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-18 8:57 [PATCH v3 0/4] media: synopsys: hdmirx: add HDMI audio capture support Igor Paunovic
2026-07-18 8:57 ` [PATCH v3 1/4] dt-bindings: media: snps,dw-hdmi-rx: add #sound-dai-cells Igor Paunovic
2026-07-19 8:54 ` Krzysztof Kozlowski
2026-07-19 9:53 ` Igor Paunovic
2026-07-18 8:57 ` [PATCH v3 2/4] media: synopsys: hdmirx: add HDMI audio capture support Igor Paunovic
2026-07-18 9:09 ` sashiko-bot
2026-07-18 10:53 ` Igor Paunovic
2026-07-20 1:42 ` Dmitry Osipenko
2026-07-20 12:30 ` Igor Paunovic
2026-07-20 14:36 ` Dmitry Osipenko
2026-07-21 5:31 ` Igor Paunovic
2026-07-23 20:56 ` Dmitry Osipenko
2026-07-23 23:47 ` Igor Paunovic
2026-07-25 17:58 ` Dmitry Osipenko [this message]
2026-07-18 8:57 ` [PATCH v3 3/4] arm64: dts: rockchip: add #sound-dai-cells to the RK3588 HDMI receiver Igor Paunovic
2026-07-18 11:12 ` Igor Paunovic
2026-07-18 8:57 ` [PATCH v3 4/4] arm64: dts: rockchip: enable HDMI RX audio capture on Orange Pi 5 Plus Igor Paunovic
2026-07-18 9:11 ` sashiko-bot
2026-07-18 11:04 ` Igor Paunovic
2026-07-18 23:31 ` Sebastian Reichel
2026-07-19 7:12 ` Igor Paunovic
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=e1034df6-3801-424a-ba1e-a03d61b37222@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
--cc=royalnet026@gmail.com \
--cc=sebastian.reichel@collabora.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