From: Sven Grewe <sven.grewe@stud.hs-bochum.de>
To: linux-sound@vger.kernel.org, Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Olivier Moysan <olivier.moysan@foss.st.com>
Cc: linux-kernel@vger.kernel.org
Subject: ASoC: dmic: add regulator support
Date: Sun, 16 Mar 2025 20:25:44 +0100 [thread overview]
Message-ID: <dad804b1-bfcf-4a72-bcaf-3f1137b3facc@stud.hs-bochum.de> (raw)
Dear Maintainers,
I tested linux-next and a patch in it breaks the audio and delays the
shutdown process on my system for a few minutes. Reverting the following
patch seems to fix it for me in linux-next 20250314:
Author: Olivier Moysan <olivier.moysan@foss.st.com>
Date: Thu Mar 6 18:18:40 2025 +0100
ASoC: dmic: add regulator support
Allow management of the regulator that may be used to supply the
digital microphone.
Signed-off-by: Olivier Moysan <olivier.moysan@foss.st.com>
Link:
https://patch.msgid.link/20250306171840.593443-3-olivier.moysan@foss.st.com
Signed-off-by: Mark Brown <broonie@kernel.org>
linux-next 20250307 worked. Later versions had the problem I described
above.
For the bisection I used the default .config from Debian's 6.12.x kernel
when building. I build and ran them on my Samsung Galaxy Book. This
device got a patch recently in linux-next not related to audio. That's
why I wanted to test linux-next and found this.
Linux version
6.14.0-rc6-next-20250314-next20250314-revertbrooniesound-grewe
(sven@Turbine) (gcc (Debian 14.2.0-17) 14.2.0, GNU ld (GNU Binutils for
Debian) 2.44) #1 SMP PREEMPT_DYNAMIC Sun Mar 16 16:06:58 CET 2025
Operating System: Debian GNU/Linux trixie on x86_64
Audio Chip: Realtek ALC256
Kind regards,
Sven J. Grewe
reply other threads:[~2025-03-16 19:34 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=dad804b1-bfcf-4a72-bcaf-3f1137b3facc@stud.hs-bochum.de \
--to=sven.grewe@stud.hs-bochum.de \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=olivier.moysan@foss.st.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®