public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Zhang Heng <zhangheng@kylinos.cn>
Cc: Takashi Iwai <tiwai@suse.de>,
	tiwai@suse.com, perex@perex.cz, linux-sound@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/realtek: Add quirk for CSL Unity BF24B
Date: Thu, 09 Apr 2026 09:59:39 +0200	[thread overview]
Message-ID: <87jyugk1hw.wl-tiwai@suse.de> (raw)
In-Reply-To: <f66e3c00-5280-4d35-9e95-2d142e4f1458@kylinos.cn>

On Thu, 09 Apr 2026 09:51:44 +0200,
Zhang Heng wrote:
> 
> Do we still need to consider HDA_FIXUP_ACT_PRE_PROBE
> 
> and HDA_FIXUP_ACT_INIT?

With my proposed change, only HDA_FIXUP_ACT_INIT is needed.

Of course, it pretty much depends on how the GPIO bits are handled.
For a volatile toggle like your case, there is no need to cache the
value, hence the direct call to handle GPIO bits is better.  OTOH,
for static GPIO setups, the caching can work better as is now.

In anyway, I already applied your original patch.  After cooking up
the whole, I'll submit the cleanups.


thanks,

Takashi

      reply	other threads:[~2026-04-09  7:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-09  2:40 [PATCH] ALSA: hda/realtek: Add quirk for CSL Unity BF24B Zhang Heng
2026-04-09  5:09 ` Takashi Iwai
2026-04-09  5:58   ` Zhang Heng
2026-04-09  6:28     ` Takashi Iwai
2026-04-09  6:30       ` Takashi Iwai
2026-04-09  6:33         ` Zhang Heng
2026-04-09  6:47           ` Takashi Iwai
2026-04-09  7:00   ` Zhang Heng
2026-04-09  7:24     ` Takashi Iwai
2026-04-09  7:51       ` Zhang Heng
2026-04-09  7:59         ` Takashi Iwai [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=87jyugk1hw.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    --cc=zhangheng@kylinos.cn \
    /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