From: Takashi Iwai <tiwai@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Takashi Iwai <tiwai@suse.de>, Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Linux Sound Mailing List <linux-sound@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] sound updates for 6.17-rc1
Date: Wed, 30 Jul 2025 07:51:20 +0200 [thread overview]
Message-ID: <8734aeteef.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAHk-=whvoZuw-Cv2Bx2ip8Kq4j9jw0meLBg0xz8GbxzFmQK7QA@mail.gmail.com>
On Wed, 30 Jul 2025 06:45:35 +0200,
Linus Torvalds wrote:
>
> On Tue, 29 Jul 2025 at 21:21, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > I think that's realtek, but when I enable it, I get this mess of
> > "which realtek", which I have no idea because the ALC3271 that the
> > kernel used to print out is not mentioned.
>
> Enabling them all makes the kernel recognize it as a ALC3271 again,
> and it appears to have loaded the alc269 one.
>
> But sound is still gone, so there's something else still missing. But
> I'm heading off for the night now...
It's a dilemma of the default kconfig enablement. In general we want
to keep the default disabled for leaf drivers.
CONFIG_SND_HDA_CODEC_REALTEK is still present but now it's a
menuconfig, so this is taken over from the previous config. The
remaining CONFIG_SND_HDA_CODEC_ALC* are the missing stuff.
Maybe we should set CONFIG_SND_HDA_CODEC_ALC*=y as default as an
exception for smooth upgrade?
I guess the same applies to the HDMI audio stuff, too.
Takashi
next prev parent reply other threads:[~2025-07-30 5:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 13:44 Takashi Iwai
2025-07-29 6:50 ` pr-tracker-bot
2025-07-30 4:21 ` Linus Torvalds
2025-07-30 4:45 ` Linus Torvalds
2025-07-30 5:51 ` Takashi Iwai [this message]
2025-07-30 16:50 ` Linus Torvalds
2025-07-30 17:21 ` Linus Torvalds
2025-07-30 18:14 ` Takashi Iwai
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=8734aeteef.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome