From: Takashi Iwai <tiwai@suse.de>
To: Shenghao Ding <shenghao-ding@ti.com>
Cc: <broonie@kernel.org>, <andriy.shevchenko@linux.intel.com>,
<lgirdwood@gmail.com>, <perex@perex.cz>,
<pierre-louis.bossart@linux.intel.com>, <13916275206@139.com>,
<alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>,
<liam.r.girdwood@intel.com>, <bard.liao@intel.com>,
<yung-chuan.liao@linux.intel.com>, <kevin-lu@ti.com>,
<cameron.berkenpas@gmail.com>, <baojun.xu@ti.com>, <soyer@irl.hu>,
<Baojun.Xu@fpt.com>
Subject: Re: [PATCH v3] ALSA: ASoc/tas2781: Fix wrong loading calibrated data sequence
Date: Fri, 03 May 2024 09:42:01 +0200 [thread overview]
Message-ID: <878r0ribp2.wl-tiwai@suse.de> (raw)
In-Reply-To: <20240502232450.484-1-shenghao-ding@ti.com>
On Fri, 03 May 2024 01:24:49 +0200,
Shenghao Ding wrote:
>
> Calibrated data will be set to default after loading DSP config params,
> which will cause speaker protection work abnormally. Reload calibrated
> data after loading DSP config params.
>
> 'Fixes: 0a0877812628 ("ASoc: tas2781: Fix spelling mistake "calibraiton"
> -> "calibration"")'
This usage of Fixes tag is utterly wrong: first off, drop the single
quote of the whole line. Moreover, the suggested commit looks very
dubious. It's merely a change to correct spelling, and this can't be
the culprit of the bug itself. Please point to the right commit.
> @@ -13,8 +13,8 @@
> // Author: Kevin Lu <kevin-lu@ti.com>
> //
>
> -#ifndef __TASDEVICE_DSP_H__
> -#define __TASDEVICE_DSP_H__
> +#ifndef __TAS2781_DSP_H__
> +#define __TAS2781_DSP_H__
This is unnecessary / related change, better to keep or do it in
another patch.
> @@ -1878,7 +1878,7 @@ int tas2781_load_calibration(void *context, char *file_name,
> {
> struct tasdevice_priv *tas_priv = (struct tasdevice_priv *)context;
> struct tasdevice *tasdev = &(tas_priv->tasdevice[i]);
> - const struct firmware *fw_entry;
> + const struct firmware *fw_entry = NULL;
Why is this needed? If a NULL initialization is a must (for some
warning fix or whatever), do it in an individual fix patch instead.
The rest changes look OK, but it's a bit hard to judge because the
code has too few comments, unfortunately...
thanks,
Takashi
next prev parent reply other threads:[~2024-05-03 7:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 23:24 [PATCH v3] ALSA: ASoc/tas2781: Fix wrong loading calibrated data sequence Shenghao Ding
2024-05-03 7:42 ` Takashi Iwai [this message]
2024-05-03 15:52 ` Andy Shevchenko
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=878r0ribp2.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=13916275206@139.com \
--cc=Baojun.Xu@fpt.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=baojun.xu@ti.com \
--cc=bard.liao@intel.com \
--cc=broonie@kernel.org \
--cc=cameron.berkenpas@gmail.com \
--cc=kevin-lu@ti.com \
--cc=lgirdwood@gmail.com \
--cc=liam.r.girdwood@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=shenghao-ding@ti.com \
--cc=soyer@irl.hu \
--cc=yung-chuan.liao@linux.intel.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