From: Benjamin Poirier <benjamin.poirier@gmail.com>
To: Jaroslav Kysela <perex@perex.cz>
Cc: alsa-devel@alsa-project.org, Kailang Yang <kailang@realtek.com>,
Takashi Iwai <tiwai@suse.com>, Hui Wang <hui.wang@canonical.com>,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
Vincent Bernat <vincent@bernat.ch>,
Even Brenden <evenbrenden@gmail.com>
Subject: Re: [PATCH v2 2/2] ALSA: hda/realtek - Replace Lenovo Thinkpad X1 Carbon 7th quirk
Date: Mon, 6 Jul 2020 08:19:55 +0900 [thread overview]
Message-ID: <20200705231955.GA2439@f3> (raw)
In-Reply-To: <58a7791c-0db4-a585-c550-3d3e9576191c@perex.cz>
On 2020-07-03 12:33 +0200, Jaroslav Kysela wrote:
[...]
> > @@ -7559,8 +7606,8 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
> > SND_PCI_QUIRK(0x17aa, 0x224c, "Thinkpad", ALC298_FIXUP_TPT470_DOCK),
> > SND_PCI_QUIRK(0x17aa, 0x224d, "Thinkpad", ALC298_FIXUP_TPT470_DOCK),
> > SND_PCI_QUIRK(0x17aa, 0x225d, "Thinkpad T480", ALC269_FIXUP_LIMIT_INT_MIC_BOOST),
> > - SND_PCI_QUIRK(0x17aa, 0x2292, "Thinkpad X1 Carbon 7th", ALC285_FIXUP_THINKPAD_HEADSET_JACK),
> > - SND_PCI_QUIRK(0x17aa, 0x22be, "Thinkpad X1 Carbon 8th", ALC285_FIXUP_THINKPAD_HEADSET_JACK),
> > + SND_PCI_QUIRK(0x17aa, 0x2292, "Thinkpad X1 Carbon 7th", ALC295_FIXUP_TPX17_DUAL_SPEAKERS),
> > + SND_PCI_QUIRK(0x17aa, 0x22be, "Thinkpad X1 Carbon 8th", ALC285_FIXUP_SPEAKER2_TO_DAC1),
>
> It will cause regression with the old UCM configs.
Yes, good point. I'll try to find a way that doesn't need ucm changes.
> I would preper the manual
> model selection and switch this when things settle a bit in the user space.
> We definitely need a better way to control this volume separately for both
> tweeters and the bass speakers in the user space. The "Master" volume hack
> is far from the ideal solution.
[...]
>
> > The volume control for PCM-OUT2 is renamed to reflect its dual effect.
> > This name is also used in a modified alsa UCM profile. [4]
>
> The new name is not ideal. Perhaps, a mirror (joined) control might be
> better in this case. I mean to create both "Bass Speaker Playback Volume"
> and "Headphone Playback Volume" with the similar NID control.
>
> Or create "Speaker Playback" controls with 4 channels (and joined "Headphone
> Playback" controls).
I'll look into that. As I'm working on this in my spare time, no
guarantee on how long it'll take.
Thanks for the review.
prev parent reply other threads:[~2020-07-05 23:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 8:00 [PATCH v2 0/2] Fix Lenovo ThinkPad X1 Carbon 7th gen bass volume Benjamin Poirier
2020-07-03 8:00 ` [PATCH v2 1/2] ALSA: hda/realtek - Fix Lenovo Thinkpad X1 Carbon 7th quirk subdevice id Benjamin Poirier
2020-07-07 8:16 ` Takashi Iwai
2020-07-03 8:00 ` [PATCH v2 2/2] ALSA: hda/realtek - Replace Lenovo Thinkpad X1 Carbon 7th quirk Benjamin Poirier
2020-07-03 10:33 ` Jaroslav Kysela
2020-07-03 10:59 ` [External] " Mark Pearson
2020-07-03 12:43 ` Jaroslav Kysela
2020-07-05 23:31 ` Benjamin Poirier
2020-07-05 23:19 ` Benjamin Poirier [this message]
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=20200705231955.GA2439@f3 \
--to=benjamin.poirier@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=evenbrenden@gmail.com \
--cc=hui.wang@canonical.com \
--cc=kai.heng.feng@canonical.com \
--cc=kailang@realtek.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=vincent@bernat.ch \
/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