diff options
| author | Mohamed Yassine Jebabli <med.jebabli@gmail.com> | 2026-10-01 12:24:42 +0200 |
|---|---|---|
| committer | Takashi Iwai <tiwai@suse.de> | 2026-10-03 11:16:06 +0200 |
| commit | 408249089c48df1a4d23f60b831be3f3c311e6d1 (patch) | |
| tree | 6712e432763b2fb56c243f8f0ebdd542c929a034 /scripts/cleanpatch | |
| parent | 593d46fc6af9a0178a46e77d6d24b20d2314165f (diff) | |
ALSA: hda/tas2781: Accept V1 calibration data without CRC
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>
Link: https://patch.msgid.link/20261001-tas2781-v1-nocrc-v1-1-ff0c1032ce76@gmail.com
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Diffstat (limited to 'scripts/cleanpatch')
0 files changed, 0 insertions, 0 deletions