public inbox for linux-sound@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: wangdich9700@163.com
Cc: bo.liu@senarytech.com, perex@perex.cz, tiwai@suse.com,
	linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	wangdicheng <wangdicheng@kylinos.cn>
Subject: Re: [PATCH] ALSA: hda/senary: Add hardware init verbs and fixup framework
Date: Wed, 04 Mar 2026 12:09:36 +0100	[thread overview]
Message-ID: <871phzx34f.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260304070219.450083-1-wangdich9700@163.com>

On Wed, 04 Mar 2026 08:02:19 +0100,
wangdich9700@163.com wrote:
> 
> From: wangdicheng <wangdicheng@kylinos.cn>
> 
> Port the essential hardware initialization logic from the vendor driver
> and introduce the standard HDA fixup framework to handle different
> machine configurations.
> 
> Key changes:
> 
> 1. Add hardware init verbs:
>    - Implement `senary_init_verb` to send the vendor-specific
>      initialization sequence required by the SN6186 chip.
>    - Override pin capabilities for Node 0x19 to ensure proper headset
>      microphone support.
> 
> 2. Introduce fixup framework:
>    - Define a default pin configuration table (`senary_pincfg_default`)
>      to provide a fallback for devices with invalid BIOS configurations.
>    - Establish a quirk table structure for future machine-specific
>      fixes.
>    - Since the standard quirk matching relies on Subsystem IDs, we
>      manually apply the default fixup if `snd_hda_pick_fixup` does not
>      find a specific match.
> 
> This ensures the chip is correctly initialized during probe and resume,
> and provides a scalable mechanism for supporting specific hardware
> quirks.
> 
> Signed-off-by: wangdicheng <wangdicheng@kylinos.cn>

As this doesn't look like an urgent fix, I applied to for-next branch
for 7.1.


thanks,

Takashi

      reply	other threads:[~2026-03-04 11:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04  7:02 [PATCH] ALSA: hda/senary: Add hardware init verbs and fixup framework wangdich9700
2026-03-04 11:09 ` 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=871phzx34f.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=bo.liu@senarytech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    --cc=wangdich9700@163.com \
    --cc=wangdicheng@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