From: kernel test robot <lkp@intel.com>
To: Hui Wang <hui.wang@canonical.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Mark Brown <broonie@kernel.org>, Bard Liao <bard.liao@intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>
Subject: [broonie-sound:for-linus 313/320] sound/soc/sof/intel/hda-codec.c:132:35: error: 'CODEC_PROBE_RETRIES' undeclared
Date: Tue, 7 Dec 2021 08:10:42 +0800 [thread overview]
Message-ID: <202112070826.L6twVlKM-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-linus
head: de2138b0ab8ac888a97868a08c29c2e37f8b71bd
commit: 046aede2f847676f93a2ea4f48b77909c51dba40 [313/320] ASoC: SOF: Intel: Retry codec probing if it fails
config: x86_64-randconfig-r026-20211202 (https://download.01.org/0day-ci/archive/20211207/202112070826.L6twVlKM-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/?id=046aede2f847676f93a2ea4f48b77909c51dba40
git remote add broonie-sound https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
git fetch --no-tags broonie-sound for-linus
git checkout 046aede2f847676f93a2ea4f48b77909c51dba40
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
sound/soc/sof/intel/hda-codec.c: In function 'hda_codec_probe':
>> sound/soc/sof/intel/hda-codec.c:132:35: error: 'CODEC_PROBE_RETRIES' undeclared (first use in this function)
132 | } while (resp == -1 && retry++ < CODEC_PROBE_RETRIES);
| ^~~~~~~~~~~~~~~~~~~
sound/soc/sof/intel/hda-codec.c:132:35: note: each undeclared identifier is reported only once for each function it appears in
vim +/CODEC_PROBE_RETRIES +132 sound/soc/sof/intel/hda-codec.c
110
111 /* probe individual codec */
112 static int hda_codec_probe(struct snd_sof_dev *sdev, int address,
113 bool hda_codec_use_common_hdmi)
114 {
115 #if IS_ENABLED(CONFIG_SND_SOC_SOF_HDA_AUDIO_CODEC)
116 struct hdac_hda_priv *hda_priv;
117 struct hda_codec *codec;
118 int type = HDA_DEV_LEGACY;
119 #endif
120 struct hda_bus *hbus = sof_to_hbus(sdev);
121 struct hdac_device *hdev;
122 u32 hda_cmd = (address << 28) | (AC_NODE_ROOT << 20) |
123 (AC_VERB_PARAMETERS << 8) | AC_PAR_VENDOR_ID;
124 u32 resp = -1;
125 int ret, retry = 0;
126
127 do {
128 mutex_lock(&hbus->core.cmd_mutex);
129 snd_hdac_bus_send_cmd(&hbus->core, hda_cmd);
130 snd_hdac_bus_get_response(&hbus->core, address, &resp);
131 mutex_unlock(&hbus->core.cmd_mutex);
> 132 } while (resp == -1 && retry++ < CODEC_PROBE_RETRIES);
133
134 if (resp == -1)
135 return -EIO;
136 dev_dbg(sdev->dev, "HDA codec #%d probed OK: response: %x\n",
137 address, resp);
138
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-12-07 0:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202112070826.L6twVlKM-lkp@intel.com \
--to=lkp@intel.com \
--cc=bard.liao@intel.com \
--cc=broonie@kernel.org \
--cc=hui.wang@canonical.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@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
all inboxes | Powered by JetHome®