From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Cc: "moderated list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER
MANAGEM..." <alsa-devel@alsa-project.org>,
kbuild-all@lists.01.org, kernel test robot <lkp@intel.com>,
llvm@lists.linux.dev, Hui Wang <hui.wang@canonical.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Mark Brown <broonie@kernel.org>, Bard Liao <bard.liao@intel.com>
Subject: Re: [linux-next:master 3956/5128] sound/soc/sof/intel/hda-codec.c:132:35: error: use of undeclared identifier 'CODEC_PROBE_RETRIES'
Date: Fri, 3 Dec 2021 08:48:46 -0600 [thread overview]
Message-ID: <7631ac5e-c1c4-9051-ee7a-985ed02183e5@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2112031605380.3554566@eliteleevi.tm.intel.com>
On 12/3/21 8:07 AM, Kai Vehmanen wrote:
> Hey,
>
>
> On Fri, 3 Dec 2021, Pierre-Louis Bossart wrote:
>
>>> 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);
>>
>> Indeed, something's not right here.
>>
>> CODEC_PROBE_RETRIES is defined conditionally
>>
>> #if IS_ENABLED(CONFIG_SND_SOC_SOF_HDA_AUDIO_CODEC)
>> #define IDISP_VID_INTEL 0x80860000
>> #define CODEC_PROBE_RETRIES 3
>>
>> but it's used unconditionally.
>
> yup, the definition needs to be moved out.
>
>> We could define this constant unconditionally as a quick fix, but this
>> compilation problem might expose a larger problem.
>>
>> Kai, I wonder if this is code from lines 120 to 139 that we didn't
>> update when we moved to support HDMI with the generic HDaudio parts? I
>> don't see why we could even try to send a command on the bus is there's
>> no audio codec support?
>>
>> hda_codec_use_common_hdmi should be the default assumption now, I don't
>> think we support the old solution, do we?
>
> We do still support the hdac-hdmi as well, albeit only for select old
> hardware to maintain backwards compatibility.
Would it be a major risk to drop this compatibility, possibly in steps
that can be reverted quickly? Maintaining this old HDMI-specific path
isn't really sustainable.
> I'll send the quick fix.
Thanks!
next prev parent reply other threads:[~2021-12-03 14:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 11:25 kernel test robot
2021-12-03 14:00 ` Pierre-Louis Bossart
2021-12-03 14:07 ` Kai Vehmanen
2021-12-03 14:48 ` Pierre-Louis Bossart [this message]
2021-12-03 15:01 ` Hui Wang
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=7631ac5e-c1c4-9051-ee7a-985ed02183e5@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--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-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
/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