From: Stefan Wahren <stefan.wahren@i2se.com>
To: Diederik de Haas <didi.debian@cknow.org>
Cc: devel@driverdev.osuosl.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-rpi-kernel@lists.infradead.org
Subject: Re: Sound issues with the 5.10.x kernel (alsa)
Date: Mon, 8 Feb 2021 13:22:56 +0100 [thread overview]
Message-ID: <b0be09a0-5ec3-b716-4b77-1dde43719273@i2se.com> (raw)
In-Reply-To: <3165951.nLcn7dHqa8@bagend>
Hi Diederik,
Am 08.02.21 um 12:47 schrieb Diederik de Haas:
> Hi,
>
> This is basically me forwarding the bug I reported on Debian's BTS:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978025
>
> TL;DR: I have a RPi 3B+ running pure Debian Bullseye arm64 (~from
> raspi.debian.net), named rpi-mpd, connected via HDMI cable to my AV Receiver.
can you please confirm that the bcm2835-audio driver causing the issues?
> Playing music worked fine with kernel 5.9, but with 5.10.2-1 the music
> (quality) became not good to quite horribly, because of (static) noise and
> distortion.
> With kernel version 5.10.9 (linux-image-5.10.0-2-arm64) it all seemed fixed,
> but returned with 5.10.12 (linux-image-5.10.0-3-arm64) and is also present
> with 5.10.13.
I cannot explain why 5.10.9 works for you, but we had multiple
regressions in 5.10. Currently i cannot see any of the fixes by Phil
Elwell in linux-stable. Maybe they won't apply and needs to be backport
manually.
Just for reference here are the revelant patches:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/staging/vc04_services?h=next-20210205&id=96ae327678eceabf455b11a88ba14ad540d4b046
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/staging/vc04_services?h=next-20210205&id=88753cc19f087abe0d39644b844e67a59cfb5a3d
Could you please try?
Best regards
Stefan
>
> I can consistently reproduce this issue, rebooting into 5.10.9 and playing
> music is fine again, so I *think* this is not a local issue.
> This ML is the closest I can think of as 'upstream', so hopefully more insight
> can be accomplished here ... and a fix.
>
> Cheers,
> Diederik
>
> _______________________________________________
> linux-rpi-kernel mailing list
> linux-rpi-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rpi-kernel
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next parent reply other threads:[~2021-02-08 12:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3165951.nLcn7dHqa8@bagend>
2021-02-08 12:22 ` Stefan Wahren [this message]
2021-02-08 12:50 ` Sound issues with the 5.10.x kernel (alsa) Diederik de Haas
2021-02-16 0:12 ` Diederik de Haas
2021-02-16 14:38 ` Diederik de Haas
2021-03-28 0:48 ` Ryutaroh Matsumoto
2021-03-28 5:58 ` Ryutaroh Matsumoto
2021-03-28 9:29 ` Stefan Wahren
2021-03-28 23:13 ` Ryutaroh Matsumoto
2021-03-28 23:17 ` Ryutaroh Matsumoto
[not found] ` <20210208.230026.1706784668119437570.ryutaroh@ict.e.titech.ac.jp>
2021-02-08 14:31 ` Diederik de Haas
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=b0be09a0-5ec3-b716-4b77-1dde43719273@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=devel@driverdev.osuosl.org \
--cc=didi.debian@cknow.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-rpi-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).