All of lore.kernel.org
 help / color / mirror / Atom feed
From: Casey Tunturi <casey@samaritansolutions.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: Casey Tunturi via B4 Relay
	<devnull+casey.samaritansolutions.net@kernel.org>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda: intel: reset link for HP ENVY 27-p014
Date: Thu, 03 Sep 2026 13:12:57 -0400	[thread overview]
Message-ID: <4875e82cbae39f7ea1a18e11fe47c7e2@samaritansolutions.net> (raw)
In-Reply-To: <87o6ehcgzk.wl-tiwai@suse.de>

On Tue, Sep 1, 2026 at 8:07 AM Takashi Iwai <tiwai@suse.de> wrote:
> Thanks for the patch. But I must say that it's very hackish, and we 
> should
> reconsider to make the changes a bit more generic or cleaner.
> 
> But, first off, could you give more details about your hardware? At 
> best,
> give alsa-info.sh output (run with --no-upload option and attach the 
> output).


Thank you for taking the time to review it!

Oh yes, I think it's cursed. This is a hack.

I submitted it just before leaving my in-laws' place so it wouldn't stay 
isolated to that one machine. It has been running for about four months, 
and it was the only thing I found so far that made the codec enumerate 
and gave my father-in-law working analog audio under Linux.

I don't have the machine in front of me now. I'll have it again just 
short of two weeks. I'll rerun the tests, collect the alsa-info output, 
and work through the reset and PIO questions then.

> Can't the standard snd_hdac_bus_reset_link() work? If not, we may tweak
> there in the standard code instead of open-code here.

I knew I was probably forcing the issue at the wrong layer. I asked 
around on Matrix with a couple of devs and couldn't get the standard 
reset path to work on this hardware.

I'd appreciate any pointers to code or docs I should read. I'd like to 
understand the right fix rather than just keep the workaround.

Casey

      reply	other threads:[~2026-09-03 17:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-28 20:29 [PATCH] ALSA: hda: intel: reset link for HP ENVY 27-p014 Casey Tunturi
2026-08-28 20:29 ` Casey Tunturi via B4 Relay
2026-09-01 12:07 ` Takashi Iwai
2026-09-03 17:12   ` Casey Tunturi [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=4875e82cbae39f7ea1a18e11fe47c7e2@samaritansolutions.net \
    --to=casey@samaritansolutions.net \
    --cc=devnull+casey.samaritansolutions.net@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.