From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: "Ding, Shenghao" <shenghao-ding@ti.com>,
"broonie@kernel.org" <broonie@kernel.org>
Cc: "andriy.shevchenko@linux.intel.com"
<andriy.shevchenko@linux.intel.com>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"perex@perex.cz" <perex@perex.cz>,
"13916275206@139.com" <13916275206@139.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"liam.r.girdwood@intel.com" <liam.r.girdwood@intel.com>,
"bard.liao@intel.com" <bard.liao@intel.com>,
"mengdong.lin@intel.com" <mengdong.lin@intel.com>,
"yung-chuan.liao@linux.intel.com"
<yung-chuan.liao@linux.intel.com>, "Lu, Kevin" <kevin-lu@ti.com>,
"tiwai@suse.de" <tiwai@suse.de>, "Xu, Baojun" <baojun.xu@ti.com>,
"soyer@irl.hu" <soyer@irl.hu>,
"Baojun.Xu@fpt.com" <Baojun.Xu@fpt.com>,
"Navada Kanyana, Mukund" <navada@ti.com>
Subject: Re: [EXTERNAL] Re: [PATCH v11] ASoc: tas2783: Add tas2783 codec driver
Date: Tue, 26 Mar 2024 10:00:19 -0500 [thread overview]
Message-ID: <bc8d97e2-6742-4ca3-bd6a-143fe88f617b@linux.intel.com> (raw)
In-Reply-To: <51a81ac8aace456aae7d07634912367c@ti.com>
>>> +
>>> + /* Check Calibrated Data V2 */
>>> + if (tmp_val[0] == 2783) {
>>> + const struct calibdatav2_info calib_info = {
>>> + .number_of_devices = tmp_val[1],
>>> + .crc32_indx = 3 + tmp_val[1] * 6,
>>> + .byt_sz = 12 + tmp_val[1] * 24,
>>> + .cali_data = &tmp_val[3]
>>> + };
>>> +
>>> + if (calib_info.number_of_devices >
>> TAS2783_MAX_DEV_NUM ||
>>> + calib_info.number_of_devices == 0) {
>>> + dev_dbg(tas_dev->dev, "No dev in calibrated data
>> V2.");
>>
>> the log is not aligned with the first condition where you have too many
>> devices.
>>
>> It's not clear why it's not an error.
> playback still work without calibrated data stored in UEFI, for example bypass mode.
> Even if in case of bypass mode, algo can still work with default calibrated data.
> So, not an error.
I would use a dev_info with a clearer message that defaults are used,
e.g. along the lines of
dev_info(tas_dev->dev, "using default calibration data, no device found
in EFI data v2").
dev_warn would work as well if this is really not expected.
next prev parent reply other threads:[~2024-03-26 15:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 13:58 [PATCH v11] ASoc: tas2783: Add tas2783 codec driver Shenghao Ding
2024-03-19 15:35 ` Pierre-Louis Bossart
2024-03-26 12:36 ` [EXTERNAL] " Ding, Shenghao
2024-03-26 15:00 ` Pierre-Louis Bossart [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-05 13:26 Shenghao Ding
2024-03-05 16:03 ` Pierre-Louis Bossart
2024-03-10 0:47 ` [EXTERNAL] " Ding, Shenghao
2024-03-11 15:25 ` Pierre-Louis Bossart
2024-03-05 16:04 ` Amadeusz Sławiński
2024-03-16 12:44 ` [EXTERNAL] " Ding, Shenghao
2024-03-18 9:12 ` Amadeusz Sławiński
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=bc8d97e2-6742-4ca3-bd6a-143fe88f617b@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--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=kevin-lu@ti.com \
--cc=lgirdwood@gmail.com \
--cc=liam.r.girdwood@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mengdong.lin@intel.com \
--cc=navada@ti.com \
--cc=perex@perex.cz \
--cc=shenghao-ding@ti.com \
--cc=soyer@irl.hu \
--cc=tiwai@suse.de \
--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