From: Askar Safin <safinaskar@gmail.com>
To: tiwai@suse.de
Cc: amadeuszx.slawinski@linux.intel.com, baojun.xu@ti.com,
bo.liu@senarytech.com, cezary.rojewski@intel.com,
kai.vehmanen@linux.intel.com, kailang@realtek.com,
linux-sound@vger.kernel.org, patches@opensource.cirrus.com,
rf@opensource.cirrus.com, regressions@lists.linux.dev,
Dell.Client.Kernel@dell.com
Subject: [REGRESSION][BISECTED] My audio broke (was: [PATCH 05/27] ALSA: hda: Move controller drivers into sound/hda/controllers directory)
Date: Tue, 14 Oct 2025 06:41:56 +0300 [thread overview]
Message-ID: <20251014034156.4480-1-safinaskar@gmail.com> (raw)
In-Reply-To: <20250709160434.1859-6-tiwai@suse.de>
Takashi Iwai <tiwai@suse.de>:
> Now HD-audio controller drivers are moved into sound/hda/controllers
> directory as a part of HD-audio code reorganization. Most of drivers
> are independent from PCI bus, hence it makes more sense to put under
> sound/hda.
>
> The hda_ prefix is dropped from most of files at moving, as it's
> more or less superfluous.
>
> Signed-off-by: Takashi Iwai <tiwai@suse.de>
This patch broke my laptop's speakers.
My laptop is Dell Precision 7780.
Here is output of "sudo lspci -vvvvv":
https://zerobin.net/?bb0d52d5c33a1ca8#Z4cktfC0ofZhkzBU4/AFGpYAVJFXrus46nDeLQOV22s=
(This output was collected on Linux 6.12.43+deb13-amd64, audio works there.)
My OS is Debian Trixie.
If you need my config, then here is my config I tested with linux-next:
https://zerobin.net/?989789b5698e0afe#DKjA80yFwRFnLkYwo3ZnNZEVGowGyn5N78aSy8omoGY=
It was tested with current linux-next:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tag/?h=next-20251013
(and audio didn't work).
#regzbot introduced: 2d9223d2d64cb5216859ced6cc33fb3b04e5f98f
--
Askar Safin
next parent reply other threads:[~2025-10-14 3:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250709160434.1859-6-tiwai@suse.de>
2025-10-14 3:41 ` Askar Safin [this message]
2025-10-14 6:04 ` [REGRESSION][BISECTED] My audio broke (was: [PATCH 05/27] ALSA: hda: Move controller drivers into sound/hda/controllers directory) Takashi Iwai
2025-10-15 4:37 ` Askar Safin
2025-10-15 5:51 ` Takashi Iwai
2025-10-15 6:49 ` Askar Safin
2025-10-15 7:47 ` Takashi Iwai
2025-10-15 11:44 ` Askar Safin
2025-10-15 12:05 ` Takashi Iwai
2025-10-15 14:57 ` Askar Safin
2025-10-15 15:18 ` Takashi Iwai
2025-10-15 15:45 ` Askar Safin
2025-10-15 15:54 ` Takashi Iwai
2025-10-16 2:37 ` Askar Safin
2025-10-16 4:50 ` Askar Safin
2025-10-16 6:03 ` Askar Safin
2025-10-16 9:52 ` Takashi Iwai
2025-10-28 12:05 ` Takashi Iwai
2025-10-28 13:03 ` Askar Safin
2025-10-29 12:23 ` Askar Safin
2025-12-02 19:21 ` Askar Safin
2025-12-03 9:42 ` Takashi Iwai
2025-12-06 21:39 ` Askar Safin
2025-12-09 7:57 ` Takashi Iwai
2025-12-09 9:27 ` Takashi Iwai
2025-12-10 1:45 ` Askar Safin
2025-12-10 13:00 ` Takashi Iwai
2025-12-10 13:55 ` Thorsten Leemhuis
2025-12-11 18:11 ` Askar Safin
2025-10-15 15:02 ` Askar Safin
2025-10-15 5:01 ` Askar Safin
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=20251014034156.4480-1-safinaskar@gmail.com \
--to=safinaskar@gmail.com \
--cc=Dell.Client.Kernel@dell.com \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=baojun.xu@ti.com \
--cc=bo.liu@senarytech.com \
--cc=cezary.rojewski@intel.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=kailang@realtek.com \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=regressions@lists.linux.dev \
--cc=rf@opensource.cirrus.com \
--cc=tiwai@suse.de \
/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