From: kernel test robot <lkp@intel.com>
To: Mohan Kumar <mkumard@nvidia.com>,
tiwai@suse.com, kai.vehmanen@linux.intel.com, perex@perex.cz,
ville.syrjala@linux.intel.com
Cc: kbuild-all@lists.01.org, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org, thierry.reding@gmail.com,
jonathanh@nvidia.com, Mohan Kumar <mkumard@nvidia.com>
Subject: Re: [PATCH] ALSA: hda: Avoid unsol event during RPM suspending
Date: Mon, 28 Mar 2022 21:07:15 +0800 [thread overview]
Message-ID: <202203282137.YsDmfIAj-lkp@intel.com> (raw)
In-Reply-To: <20220328091411.31488-1-mkumard@nvidia.com>
Hi Mohan,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on tiwai-sound/for-next]
[also build test ERROR on v5.17 next-20220328]
[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]
url: https://github.com/intel-lab-lkp/linux/commits/Mohan-Kumar/ALSA-hda-Avoid-unsol-event-during-RPM-suspending/20220328-171517
base: https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git for-next
config: alpha-buildonly-randconfig-r001-20220327 (https://download.01.org/0day-ci/archive/20220328/202203282137.YsDmfIAj-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/intel-lab-lkp/linux/commit/80c4e21f5e97cd4b779806fa5da5bb7392e2874f
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Mohan-Kumar/ALSA-hda-Avoid-unsol-event-during-RPM-suspending/20220328-171517
git checkout 80c4e21f5e97cd4b779806fa5da5bb7392e2874f
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=alpha SHELL=/bin/bash sound/pci/hda/
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/pci/hda/patch_hdmi.c: In function 'hdmi_present_sense_via_verbs':
>> sound/pci/hda/patch_hdmi.c:1644:28: error: 'struct dev_pm_info' has no member named 'runtime_status'
1644 | (dev->power.runtime_status == RPM_SUSPENDING))
| ^
vim +1644 sound/pci/hda/patch_hdmi.c
1620
1621 /* update ELD and jack state via HD-audio verbs */
1622 static void hdmi_present_sense_via_verbs(struct hdmi_spec_per_pin *per_pin,
1623 int repoll)
1624 {
1625 struct hda_codec *codec = per_pin->codec;
1626 struct hdmi_spec *spec = codec->spec;
1627 struct hdmi_eld *eld = &spec->temp_eld;
1628 struct device *dev = hda_codec_dev(codec);
1629 hda_nid_t pin_nid = per_pin->pin_nid;
1630 int dev_id = per_pin->dev_id;
1631 /*
1632 * Always execute a GetPinSense verb here, even when called from
1633 * hdmi_intrinsic_event; for some NVIDIA HW, the unsolicited
1634 * response's PD bit is not the real PD value, but indicates that
1635 * the real PD value changed. An older version of the HD-audio
1636 * specification worked this way. Hence, we just ignore the data in
1637 * the unsolicited response to avoid custom WARs.
1638 */
1639 int present;
1640 int ret;
1641
1642 ret = snd_hda_power_up_pm(codec);
1643 if ((ret < 0 && pm_runtime_suspended(dev)) ||
> 1644 (dev->power.runtime_status == RPM_SUSPENDING))
1645 goto out;
1646
1647 present = snd_hda_jack_pin_sense(codec, pin_nid, dev_id);
1648
1649 mutex_lock(&per_pin->lock);
1650 eld->monitor_present = !!(present & AC_PINSENSE_PRESENCE);
1651 if (eld->monitor_present)
1652 eld->eld_valid = !!(present & AC_PINSENSE_ELDV);
1653 else
1654 eld->eld_valid = false;
1655
1656 codec_dbg(codec,
1657 "HDMI status: Codec=%d NID=0x%x Presence_Detect=%d ELD_Valid=%d\n",
1658 codec->addr, pin_nid, eld->monitor_present, eld->eld_valid);
1659
1660 if (eld->eld_valid) {
1661 if (spec->ops.pin_get_eld(codec, pin_nid, dev_id,
1662 eld->eld_buffer, &eld->eld_size) < 0)
1663 eld->eld_valid = false;
1664 }
1665
1666 update_eld(codec, per_pin, eld, repoll);
1667 mutex_unlock(&per_pin->lock);
1668 out:
1669 snd_hda_power_down_pm(codec);
1670 }
1671
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-03-28 13:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 9:14 [PATCH] ALSA: hda: Avoid unsol event during RPM suspending Mohan Kumar
2022-03-28 9:42 ` Takashi Iwai
2022-03-28 10:19 ` Mohan Kumar D
2022-03-28 10:57 ` Takashi Iwai
2022-03-28 13:51 ` Mohan Kumar D
2022-03-28 16:15 ` Takashi Iwai
2022-03-28 17:03 ` Mohan Kumar D
2022-03-28 13:07 ` kernel test robot [this message]
2022-03-28 16:09 ` kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2022-03-29 15:59 Mohan Kumar
2022-03-30 8:21 ` Takashi Iwai
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=202203282137.YsDmfIAj-lkp@intel.com \
--to=lkp@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=jonathanh@nvidia.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkumard@nvidia.com \
--cc=perex@perex.cz \
--cc=thierry.reding@gmail.com \
--cc=tiwai@suse.com \
--cc=ville.syrjala@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