From: Takashi Iwai <tiwai@suse.de>
To: med.jebabli@gmail.com
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Shenghao Ding <shenghao-ding@ti.com>,
Takashi Iwai <tiwai@suse.de>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/tas2781: Accept V1 calibration data without CRC
Date: Sat, 03 Oct 2026 11:17:57 +0200 [thread overview]
Message-ID: <87h5j3xhve.wl-tiwai@suse.de> (raw)
In-Reply-To: <20261001-tas2781-v1-nocrc-v1-1-ff0c1032ce76@gmail.com>
On Thu, 01 Oct 2026 12:24:42 +0200,
Mohamed Yassine Jebabli via B4 Relay wrote:
>
> From: Mohamed Yassine Jebabli <med.jebabli@gmail.com>
>
> Some Lenovo BIOSes (e.g. Legion Pro 7 16IRX9H, SSID 17aa:38cd) store
> valid V1 calibration data in the CALI_DATA EFI variable but leave the
> TimeStamp and CRC fields zeroed. The driver rejects such data, so the
> amplifiers always run with default parameters on these machines.
>
> The rejection was silent until
> commit 4fe238513407 ("ALSA: hda/tas2781: Move and unified the
> calibrated-data getting function for SPI and I2C into the tas2781_hda lib")
> turned it into "V1 CRC error".
>
> The stored values are consistent (R0 = 3.82/3.83 ohm, 1/R0 matching
> within 1e-4), so accept V1 data when both TimeStamp and CRC are zero
> and the first device entry is non-zero, and emit a warning.
>
> Fixes: 5be27f1e3ec9 ("ALSA: hda/tas2781: Add tas2781 HDA driver")
> Cc: stable@vger.kernel.org
> Signed-off-by: Mohamed Yassine Jebabli <med.jebabli@gmail.com>
Applied now. Thanks.
Takashi
prev parent reply other threads:[~2026-10-03 9:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 10:24 Mohamed Yassine Jebabli via B4 Relay
2026-10-03 9:17 ` 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=87h5j3xhve.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=med.jebabli@gmail.com \
--cc=perex@perex.cz \
--cc=shenghao-ding@ti.com \
--cc=stable@vger.kernel.org \
--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
all inboxes | Powered by JetHome®