From: Christoffer Sandberg <cs@tuxedo.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: Werner Sembach <wse@tuxedocomputers.com>,
Jerry Luo <jerryluo225@gmail.com>,
Christian Heusel <christian@heusel.eu>,
regressions@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-sound@vger.kernel.org, Jaroslav Kysela <perex@perex.cz>
Subject: Re: [REGRESSION][BISECTED] Audio volume issues since 4178d78cd7a8
Date: Wed, 18 Sep 2024 16:10:00 +0200 [thread overview]
Message-ID: <cedb8758bb506bf9454b90eebcaaea24@tuxedo.de> (raw)
In-Reply-To: <87r09hcbr0.wl-tiwai@suse.de>
On 18.9.2024 15:49, Takashi Iwai wrote:
> On Wed, 18 Sep 2024 15:39:28 +0200,
> Werner Sembach wrote:
>>
>> Hi
>>
>> Am 18.09.24 um 10:09 schrieb Takashi Iwai:
>> > On Wed, 18 Sep 2024 10:06:01 +0200,
>> > Takashi Iwai wrote:
>> >> [...]
>> >> I don't see any relevant about the incorrect volumes by the suggested
>> >> commit, but at least we should avoid applying the quirk for a
>> >> non-existing speaker pin.
>> >>
>> >> Jerry, yours is with CX11970 (codec id 0x14f120d0), right?
>>
>> Yes, at least for the preproduction sample of the Sirius Gen1 I have
>> at hand atm.
>>
>> pciid is 2782:12c3
>>
>> @Christoffer: I guess 2782:12c5 is for the Gen2?
Yes the other is for Sirius Gen2
>
> Hm, and one of those PCI SSID conflicts with System76 Pangolin
> (pang14)? All seem to have the very same codec CX11970.
I don't think I saw the pci id explicitly listed, but that was the
assumption.
>
> If they really conflict in both PCI and HD-audio codec IDs, the only
> way would be to check DMI string, I'm afraid.
>
I asked about the volumes since it could be a hint that a second speaker
is activated but stuck on a fixed volume. This would make a low general
volume setting sound louder but still somewhat adjustable.
However, if we can not verify second speaker pair, then I agree, DMI
limit would be the safe choice.
Christoffer
next prev parent reply other threads:[~2024-09-18 14:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 16:39 [REGRESSION][BISECTED] Audio volume issues since 4178d78cd7a8 Christian Heusel
2024-09-16 17:22 ` Takashi Iwai
2024-09-16 19:36 ` Jerry Luo
2024-09-17 9:50 ` Christoffer Sandberg
2024-09-17 21:16 ` Jerry Luo
2024-09-18 8:06 ` Takashi Iwai
2024-09-18 8:09 ` Takashi Iwai
2024-09-18 13:39 ` Werner Sembach
2024-09-18 13:49 ` Takashi Iwai
2024-09-18 14:10 ` Christoffer Sandberg [this message]
2024-09-19 8:57 ` Takashi Iwai
2024-09-19 9:45 ` Werner Sembach
2024-09-23 19:37 ` Jerry Luo
2024-09-30 7:44 ` Takashi Iwai
2024-10-02 8:21 ` Christoffer Sandberg
2024-10-02 14:00 ` Takashi Iwai
2024-10-02 21:28 ` Jerry Luo
2024-10-02 22:36 ` Jerry Luo
2024-10-04 8:18 ` Christoffer Sandberg
2024-10-04 8:25 ` Takashi Iwai
2024-10-04 9:25 ` Christoffer Sandberg
2024-10-04 9:30 ` Takashi Iwai
2024-10-08 16:06 ` 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=cedb8758bb506bf9454b90eebcaaea24@tuxedo.de \
--to=cs@tuxedo.de \
--cc=christian@heusel.eu \
--cc=jerryluo225@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=regressions@lists.linux.dev \
--cc=tiwai@suse.de \
--cc=wse@tuxedocomputers.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