From: Kai-Heng Feng <kaihengf@nvidia.com>
To: Takashi Iwai <tiwai@suse.de>, Vasiliy Kovalev <kovalev@altlinux.org>
Cc: Takashi Iwai <tiwai@suse.com>, Jaroslav Kysela <perex@perex.cz>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
bo liu <bo.liu@senarytech.com>
Subject: Re: [PATCH v2] ALSA: hda/conexant - Fix audio routing for HP EliteOne 1000 G2
Date: Thu, 10 Oct 2024 11:32:18 +0800 [thread overview]
Message-ID: <b0ac19a5-1d93-41a5-beaa-279939e8ebde@nvidia.com> (raw)
In-Reply-To: <87h69ltmgn.wl-tiwai@suse.de>
On 2024/10/9 9:50 PM, Takashi Iwai wrote:
> On Wed, 09 Oct 2024 15:42:48 +0200,
> Vasiliy Kovalev wrote:
>>
>> There is a problem with simultaneous audio output to headphones and
>> speakers, and when headphones are turned off, the speakers also turn
>> off and do not turn them on.
>>
>> However, it was found that if you boot linux immediately after windows,
>> there are no such problems. When comparing alsa-info, the only difference
>> is the different configuration of Node 0x1d:
>>
>> working conf. (windows): Pin-ctls: 0x80: HP
>> not working (linux): Pin-ctls: 0xc0: OUT HP
>>
>> This patch disable the AC_PINCTL_OUT_EN bit of Node 0x1d and fixes the
>> described problem.
>>
>> Signed-off-by: Vasiliy Kovalev <kovalev@altlinux.org>
>
> Thanks, applied now.
Though this is already applied, is it possible to see if the issue also
happens on S4?
Linux doesn't put PCI devices like HDA to D3 during shutdown and reboot
while Windows does, that might be the reason boot Linux after Windows
can workaround the issue.
Linux does put PCI devices to D3 for hibernate (S4), so we can use it as
an experiment.
Kai-Heng
>
>
> Takashi
next prev parent reply other threads:[~2024-10-10 3:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 13:42 [PATCH v2] ALSA: hda/conexant - Fix audio routing for HP EliteOne 1000 G2 Vasiliy Kovalev
2024-10-09 13:50 ` Takashi Iwai
2024-10-10 3:32 ` Kai-Heng Feng [this message]
2024-10-10 5:17 ` Takashi Iwai
2024-10-10 8:36 ` Vasiliy Kovalev
2024-10-16 8:14 ` Vasiliy Kovalev
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=b0ac19a5-1d93-41a5-beaa-279939e8ebde@nvidia.com \
--to=kaihengf@nvidia.com \
--cc=bo.liu@senarytech.com \
--cc=kovalev@altlinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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