From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 216665] New: Synopsys Designware HDMI >= 2.10a seems not to insert PCUV bits into HDMI audio stream unless insert_pcuv bit is set
Date: Sat, 05 Nov 2022 19:38:43 +0000 [thread overview]
Message-ID: <bug-216665-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=216665
Bug ID: 216665
Summary: Synopsys Designware HDMI >= 2.10a seems not to insert
PCUV bits into HDMI audio stream unless insert_pcuv
bit is set
Product: Drivers
Version: 2.5
Kernel Version: 6.0.7
Hardware: ARM
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: geraldogabriel@gmail.com
Regression: No
Created attachment 303135
--> https://bugzilla.kernel.org/attachment.cgi?id=303135&action=edit
Patch to set insert_pcuv
Enabling sound in the device tree for my Radxa Rock Pi N10 (RK3399Pro SoM)
resulted in music sounding like white noise with my Philips 243V HDMI monitor.
I then found out I wasn't alone by reading the following LibreELEC thread:
https://forum.libreelec.tv/thread/17600-rk3399-hdmi-audio-quality/
Particularly, sigmaris on page 2 of that thread, experienced similar symptoms
with his/her Samsung TV, like I did. Like him/her, I had to software mix the
volume down to 33% at which point music would sound like music, not white
noise.
I was very puzzled by that, and after an exchange with Sugar Zhang from
Rockchip I dumped all the HDMI registers with i2cdump and started checking them
one by one, comparing what was set by the Linux kernel driver with the Rockchip
Technical Reference Manual.
This lead me to the missing insert_pcuv bit, which it seems to me, Synopsys
introduced purposefully breaking compatibility with existing driver codebases.
The attached patch fixes my problem (I have normal music with 100% of audio
volume and no glitches) and was posted to relevant kernel lists:
https://lore.kernel.org/dri-devel/Y2A48a5ff+SyxqLR@geday/T/
I'd like to thank Mark Brown for pointing out the fix should be restricted to
Linear PCM only, and Neil Armstrong for further researching this. Unfortunately
it seems we're out of testers for the time being.
I post this in the hope all this doesn't sink down the memory hole, and maybe
Google will lead people experiencing the same problems towards here, and they
can test the proposed solution in the attachment.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
reply other threads:[~2022-11-05 19:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-216665-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.