From: Takashi Iwai <tiwai@suse.de>
To: Baojun Xu <baojun.xu@ti.com>
Cc: <broonie@kernel.org>, <andriy.shevchenko@linux.intel.com>,
<alsa-devel@alsa-project.org>, <shenghao-ding@ti.com>,
<navada@ti.com>, <13916275206@139.com>, <v-hampiholi@ti.com>,
<v-po@ti.com>, <linux-sound@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] ALSA: hda/tas2781: Fix calibration data parser issue
Date: Sun, 06 Jul 2025 10:08:09 +0200 [thread overview]
Message-ID: <8734b9oi6u.wl-tiwai@suse.de> (raw)
In-Reply-To: <20250705130908.26248-1-baojun.xu@ti.com>
On Sat, 05 Jul 2025 15:09:08 +0200,
Baojun Xu wrote:
>
> Calibration data was overwritten during parser, it cause issue.
It'd be helpful if you can write a bit more clearly what's the issue
and what you've done here.
thanks,
Takashi
> Fixes: 4fe238513407 ("ALSA: hda/tas2781: Move and unified the calibrated-data getting function for SPI and I2C into the tas2781_hda lib")
>
> Signed-off-by: Baojun Xu <baojun.xu@ti.com>
> ---
> sound/pci/hda/tas2781_hda.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/sound/pci/hda/tas2781_hda.c b/sound/pci/hda/tas2781_hda.c
> index 5f1d4b3e9688..34217ce9f28e 100644
> --- a/sound/pci/hda/tas2781_hda.c
> +++ b/sound/pci/hda/tas2781_hda.c
> @@ -44,7 +44,7 @@ static void tas2781_apply_calib(struct tasdevice_priv *p)
> TASDEVICE_REG(0, 0x13, 0x70),
> TASDEVICE_REG(0, 0x18, 0x7c),
> };
> - unsigned int crc, oft;
> + unsigned int crc, oft, node_num;
> unsigned char *buf;
> int i, j, k, l;
>
> @@ -80,8 +80,9 @@ static void tas2781_apply_calib(struct tasdevice_priv *p)
> dev_err(p->dev, "%s: CRC error\n", __func__);
> return;
> }
> + node_num = tmp_val[1];
>
> - for (j = 0, k = 0; j < tmp_val[1]; j++) {
> + for (j = 0, k = 0; j < node_num; j++) {
> oft = j * 6 + 3;
> if (tmp_val[oft] == TASDEV_UEFI_CALI_REG_ADDR_FLG) {
> for (i = 0; i < TASDEV_CALIB_N; i++) {
> @@ -99,8 +100,9 @@ static void tas2781_apply_calib(struct tasdevice_priv *p)
> }
>
> data[l] = k;
> + oft++;
> for (i = 0; i < TASDEV_CALIB_N * 4; i++)
> - data[l + i] = data[4 * oft + i];
> + data[l + i + 1] = data[4 * oft + i];
> k++;
> }
> }
> --
> 2.43.0
>
prev parent reply other threads:[~2025-07-06 8:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-05 13:09 Baojun Xu
2025-07-06 8:08 ` 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=8734b9oi6u.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=13916275206@139.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=baojun.xu@ti.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=navada@ti.com \
--cc=shenghao-ding@ti.com \
--cc=v-hampiholi@ti.com \
--cc=v-po@ti.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®