From: kernel test robot <lkp@intel.com>
To: Baojun Xu <baojun.xu@ti.com>, broonie@kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
tiwai@suse.de, andriy.shevchenko@linux.intel.com,
13916275206@139.com, alsa-devel@alsa-project.org,
shenghao-ding@ti.com, baojun.xu@ti.com,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
k-yi@ti.com, henry.lo@ti.com, robinchen@ti.com,
niranjan.hy@ti.com, pin-hao.huang@hp.com,
Syed.SabaKareem@amd.com
Subject: Re: [PATCH v1] ASoC: tas2783-sdw: Add basic BPT support
Date: Wed, 4 Nov 2026 13:45:43 +0800 [thread overview]
Message-ID: <202611041243.Bn9AJATC-lkp@intel.com> (raw)
In-Reply-To: <20261103133853.1612-1-baojun.xu@ti.com>
Hi Baojun,
kernel test robot noticed the following build warnings:
[auto build test WARNING on broonie-sound/for-next]
[also build test WARNING on linus/master next-20261030]
[cannot apply to v7.3]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Baojun-Xu/ASoC-tas2783-sdw-Add-basic-BPT-support/20261103-213853
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
patch link: https://lore.kernel.org/r/20261103133853.1612-1-baojun.xu%40ti.com
patch subject: [PATCH v1] ASoC: tas2783-sdw: Add basic BPT support
config: riscv-allyesconfig (https://download.01.org/0day-ci/archive/20261104/202611041243.Bn9AJATC-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 65303e81f481bbfe386b8596423f94c43198ba94)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261104/202611041243.Bn9AJATC-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202611041243.Bn9AJATC-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> sound/soc/codecs/tas2783-sdw.c:1369:6: warning: variable 'ret' is uninitialized when used here [-Wuninitialized]
1369 | if (ret) {
| ^~~
sound/soc/codecs/tas2783-sdw.c:1362:9: note: initialize the variable 'ret' to silence this warning
1362 | s32 ret;
| ^
| = 0
1 warning generated.
vim +/ret +1369 sound/soc/codecs/tas2783-sdw.c
1357
1358 static s32 tas_io_init(struct device *dev, struct sdw_slave *slave)
1359 {
1360 struct tas2783_prv *tas_dev = dev_get_drvdata(dev);
1361 uint val;
1362 s32 ret;
1363
1364 if (tas_dev->hw_init)
1365 return 0;
1366
1367 regmap_read(tas_dev->regmap, TASDEV_REG_SDW(0, 0, 7), &val);
1368 dev_dbg(dev, "Got B0P0R7 = %02X with %d.", val, ret);
> 1369 if (ret) {
1370 dev_err(dev, "Get FW download status failed, err=%d", ret);
1371 return ret;
1372 }
1373 if (val != 0x22) {
1374 tas_dev->fw_dl_success = false;
1375 ret = regmap_write(tas_dev->regmap, TAS2783_SW_RESET, 0x1);
1376 if (ret) {
1377 dev_err(dev, "sw reset failed, err=%d", ret);
1378 return ret;
1379 }
1380 usleep_range(2000, 2200);
1381 regcache_cache_only(tas_dev->regmap, false);
1382 tas_dev->fw_use_fallback = false;
1383 ret = tas_fw_load(tas_dev, slave);
1384 if (!ret && tas_dev->fw_use_fallback)
1385 ret = tas_fw_load(tas_dev, slave);
1386 }
1387 if (!ret) {
1388 if (tas_dev->sa_func_data)
1389 ret = sdca_regmap_write_init(dev, tas_dev->regmap,
1390 tas_dev->sa_func_data);
1391 else
1392 ret = regmap_multi_reg_write(tas_dev->regmap, tas2783_init_seq,
1393 ARRAY_SIZE(tas2783_init_seq));
1394
1395 /* Re-active AMP after resume. */
1396 regmap_write(tas_dev->regmap, TASDEV_REG_SDW(0, 0, 2), 0);
1397 if (ret)
1398 dev_err(tas_dev->dev,
1399 "init writes failed, err=%d", ret);
1400 else
1401 tas_dev->hw_init = true;
1402 }
1403
1404 return ret;
1405 }
1406
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-11-04 5:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 13:38 Baojun Xu
2026-11-03 17:07 ` Pierre-Louis Bossart
2026-11-03 17:39 ` Andy Shevchenko
2026-11-04 5:45 ` kernel test robot [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=202611041243.Bn9AJATC-lkp@intel.com \
--to=lkp@intel.com \
--cc=13916275206@139.com \
--cc=Syed.SabaKareem@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=baojun.xu@ti.com \
--cc=broonie@kernel.org \
--cc=henry.lo@ti.com \
--cc=k-yi@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=niranjan.hy@ti.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pin-hao.huang@hp.com \
--cc=robinchen@ti.com \
--cc=shenghao-ding@ti.com \
--cc=tiwai@suse.de \
/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®