From: Takashi Iwai <tiwai@suse.de>
To: Gergo Koteles <soyer@irl.hu>
Cc: Shenghao Ding <shenghao-ding@ti.com>, Kevin Lu <kevin-lu@ti.com>,
Baojun Xu <baojun.xu@ti.com>, Sen Wang <sen@ti.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Philipp Oster <philippdev5396@outlook.de>,
Georg Wenzel <g.wenzel@gmail.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
alsa-devel@alsa-project.org
Subject: Re: [PATCH v2 0/2] ALSA: hda/tas2781: Skip invalid TAS2563 UEFI calibration data
Date: Wed, 14 Oct 2026 07:55:23 +0200 [thread overview]
Message-ID: <87jynkg71w.wl-tiwai@suse.de> (raw)
In-Reply-To: <cover.1791895478.git.soyer@irl.hu>
On Tue, 13 Oct 2026 15:02:19 +0200,
Gergo Koteles wrote:
>
> Hi,
>
> Georg Wenzel experienced a regession with TAS2563 amplifiers. His laptop
> lacks proper calibration data, and due to a bug, the driver failed to
> apply them in the v6.16.x. That's why they worked.
>
> The amplifiers operate even without calibration data, so the calibration
> setup can be skipped if the data is invalid.
>
> The first patch simplifies error paths in the tas2563_save_calibration()
> function.
>
> The second patch skips the zero UEFI calibration data as it is not
> necessary to apply.
>
> The previous patch for this problem
> 3bc4fc135ec7 ("ALSA: hda/tas2781: Enable bass speakers support")
> should be removed/reverted.
>
> Gergo Koteles (2):
> ALSA: hda/tas2781: Assign total_sz at the end of the function
> ALSA: hda/tas2781: Skip invalid TAS2563 UEFI calibration data
Applied with the revert of the previous fix to for-next branch now.
thanks,
Takashi
prev parent reply other threads:[~2026-10-14 5:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 13:02 [PATCH v2 0/2] ALSA: hda/tas2781: Skip invalid TAS2563 UEFI calibration data Gergo Koteles
2026-10-13 13:02 ` [PATCH v2 1/2] ALSA: hda/tas2781: Assign total_sz at the end of the function Gergo Koteles
2026-10-13 13:02 ` [PATCH v2 2/2] ALSA: hda/tas2781: Skip invalid TAS2563 UEFI calibration data Gergo Koteles
2026-10-14 5:55 ` 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=87jynkg71w.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=baojun.xu@ti.com \
--cc=g.wenzel@gmail.com \
--cc=kevin-lu@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=philippdev5396@outlook.de \
--cc=sen@ti.com \
--cc=shenghao-ding@ti.com \
--cc=soyer@irl.hu \
--cc=tiwai@suse.com \
/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