Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "eziogale@gmail.com" <eziogale@gmail.com>
Cc: Jaroslav Kysela ` <perex@perex.cz>,
	linux-sound@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH] ALSA: hda/ca0132: add QUIRK_GENERIC path for Gigabyte, GA-Z170X-Gaming G1
Date: Tue, 19 May 2026 07:35:46 +0200	[thread overview]
Message-ID: <87h5o43qrx.wl-tiwai@suse.de> (raw)
In-Reply-To: <0c0b781f-1595-4595-921a-66d83cf5930b@gmail.com>

On Mon, 18 May 2026 11:23:25 +0200,
eziogale@gmail.com wrote:
> 
> Sorry, with gmail and OAUTH2 it's a bit complicated. I'v to make an
> attachmant.
> Tanks for the patience.
> 
> From 6411be653404246e661d6bcf418345abf866e098 Mon Sep 17 00:00:00 2001
> From: Ezio Galeazzi <eziogale@gmail.com>
> Date: Sun, 17 May 2026 17:42:36 +0200
> Subject: [PATCH] ALSA: hda/ca0132: add QUIRK_GENERIC path for Gigabyte
>  GA-Z170X-Gaming G1
> 
> Some CA0132 implementations (e.g. Gigabyte GA-Z170X-Gaming G1) produce white noise when using the DSP firmware path. Add a QUIRK_GENERIC path that uses the standard HDA generic parser instead, with custom pin configs.
> This patch applies against v6.18.24.
> 
> Signed-off-by: Ezio Galeazzi <eziogale@gmail.com>

Thanks, applied to for-next branch now.


Takashi

      reply	other threads:[~2026-05-19  5:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-10  9:38 ca0132: add generic parser fallback for broken DSP path eziogale
2026-05-16 13:41 ` Takashi Iwai
2026-05-17 16:29   ` [PATCH] ALSA: hda/ca0132: add QUIRK_GENERIC path for Gigabyte, GA-Z170X-Gaming G1 eziogale
2026-05-17 19:53     ` Takashi Iwai
2026-05-18  9:19       ` eziogale
2026-05-18  9:23       ` eziogale
2026-05-19  5:35         ` 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=87h5o43qrx.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=eziogale@gmail.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    /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