From: Takashi Iwai <tiwai@suse.de>
To: Jerry Luo <jerryluo225@gmail.com>
Cc: tiwai@suse.de, christian@heusel.eu, cs@tuxedo.de,
linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
perex@perex.cz, regressions@lists.linux.dev,
wse@tuxedocomputers.com
Subject: Re: [REGRESSION][BISECTED] Audio volume issues since 4178d78cd7a8
Date: Mon, 30 Sep 2024 09:44:43 +0200 [thread overview]
Message-ID: <87jzetk2l0.wl-tiwai@suse.de> (raw)
In-Reply-To: <ea6e5168-238f-41f5-9600-36b75ed990a1@gmail.com>
On Mon, 23 Sep 2024 21:37:42 +0200,
Jerry Luo wrote:
>
>
> Hi Takashi,
>
> On Mon, 16 Sep 2024 19:22:05 +0200,
>
> Takashi Iwai wrote:
>
> Could you give alsa-info.sh output from both working and non-working
> cases? Run the script with --no-upload option and attach the outputs.
>
> thanks,
>
> Takashi
>
> Issue now reappear, output from alsa-info.sh are attached. If they are still
> needed.
Thanks. The obvious difference seems to be the assignment of two DACs
0x10 and 0x11 for headphone and speaker outputs.
Christoffer, how are those on your machines?
Takashi
next prev parent reply other threads:[~2024-09-30 7:43 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
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 [this message]
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=87jzetk2l0.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=christian@heusel.eu \
--cc=cs@tuxedo.de \
--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=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