From: kernel test robot <lkp@intel.com>
To: Niranjan H Y <niranjan.hy@ti.com>, alsa-devel@alsa-project.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-sound@vger.kernel.org, lgirdwood@gmail.com,
broonie@kernel.org, perex@perex.cz, tiwai@suse.com,
yung-chuan.liao@linux.intel.com, cezary.rojewski@intel.com,
peter.ujfalusi@linux.intel.com,
ranjani.sridharan@linux.intel.com, kai.vehmanen@linux.intel.com,
pierre-louis.bossart@linux.dev, navada@ti.com,
shenghao-ding@ti.com, v-hampiholi@ti.com, baojun.xu@ti.com,
Niranjan H Y <niranjan.hy@ti.com>
Subject: Re: [PATCH v2 1/4] ASoc: tas2783A: Add soundwire based codec driver
Date: Wed, 10 Sep 2025 10:21:04 +0800 [thread overview]
Message-ID: <202509101012.OvT5ytrT-lkp@intel.com> (raw)
In-Reply-To: <20250901051144.1112-1-niranjan.hy@ti.com>
Hi Niranjan,
kernel test robot noticed the following build errors:
[auto build test ERROR on broonie-sound/for-next]
[also build test ERROR on linus/master v6.17-rc5 next-20250909]
[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/Niranjan-H-Y/ASoc-tas2783A-machine-driver-amp-utility-for-TI-devices/20250909-201553
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
patch link: https://lore.kernel.org/r/20250901051144.1112-1-niranjan.hy%40ti.com
patch subject: [PATCH v2 1/4] ASoc: tas2783A: Add soundwire based codec driver
config: hexagon-randconfig-002-20250910 (https://download.01.org/0day-ci/archive/20250910/202509101012.OvT5ytrT-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 7fb1dc08d2f025aad5777bb779dfac1197e9ef87)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250910/202509101012.OvT5ytrT-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/202509101012.OvT5ytrT-lkp@intel.com/
All errors (new ones prefixed by >>):
>> sound/soc/codecs/tas2783-sdw.c:791:8: error: incompatible pointer types passing 'size_t *' (aka 'unsigned int *') to parameter of type 'unsigned long *' [-Werror,-Wincompatible-pointer-types]
791 | &size, NULL);
| ^~~~~
1 error generated.
vim +791 sound/soc/codecs/tas2783-sdw.c
769
770 static s32 tas2783_update_calibdata(struct tas2783_prv *tas_dev)
771 {
772 efi_guid_t efi_guid = TAS2783_CALI_GUID;
773 u32 attr, i, *tmp_val;
774 size_t size;
775 s32 ret;
776 efi_status_t status;
777 static efi_char16_t efi_names[][32] = {
778 L"SmartAmpCalibrationData", L"CALI_DATA"};
779
780 tmp_val = (u32 *)tas_dev->cali_data.data;
781 attr = 0;
782 i = 0;
783
784 /*
785 * In some cases, the calibration is performed in Windows,
786 * and data was saved in UEFI. Linux can access it.
787 */
788 for (i = 0; i < ARRAY_SIZE(efi_names); i++) {
789 size = 0;
790 status = efi.get_variable(efi_names[i], &efi_guid, &attr,
> 791 &size, NULL);
792 if (size > TAS2783_CALIB_DATA_SZ) {
793 dev_err(tas_dev->dev, "cali data too large\n");
794 break;
795 }
796
797 tas_dev->cali_data.read_sz = size;
798 if (status == EFI_BUFFER_TOO_SMALL) {
799 status = efi.get_variable(efi_names[i], &efi_guid, &attr,
800 &tas_dev->cali_data.read_sz,
801 tas_dev->cali_data.data);
802 dev_dbg(tas_dev->dev, "cali get %lu bytes result:%ld\n",
803 tas_dev->cali_data.read_sz, status);
804 }
805 if (status == EFI_SUCCESS)
806 break;
807 }
808
809 if (status != EFI_SUCCESS) {
810 /* Failed got calibration data from EFI. */
811 dev_dbg(tas_dev->dev, "No calibration data in UEFI.");
812 return 0;
813 }
814
815 mutex_lock(&tas_dev->calib_lock);
816 ret = tas2783_validate_calibdata(tas_dev, tas_dev->cali_data.data,
817 tas_dev->cali_data.read_sz);
818 if (!ret)
819 tas2783_set_calib_params_to_device(tas_dev, tmp_val);
820 mutex_unlock(&tas_dev->calib_lock);
821
822 return ret;
823 }
824
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-09-10 2:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 5:11 [PATCH v2 1/4] ASoc: tas2783A: Add soundwire based codec driver Niranjan H Y
2025-09-01 5:11 ` [PATCH v2 2/4] ASoc: tas2783A: machine driver amp utility for TI devices Niranjan H Y
2025-09-01 5:11 ` [PATCH v2 3/4] ASoc: tas2783A: add machine driver changes Niranjan H Y
2025-09-01 5:11 ` [PATCH v2 4/4] tas2783A: Add acpi match changes for Intel MTL Niranjan H Y
2025-09-10 2:21 ` 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=202509101012.OvT5ytrT-lkp@intel.com \
--to=lkp@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=baojun.xu@ti.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=navada@ti.com \
--cc=niranjan.hy@ti.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=ranjani.sridharan@linux.intel.com \
--cc=shenghao-ding@ti.com \
--cc=tiwai@suse.com \
--cc=v-hampiholi@ti.com \
--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