From: Takashi Iwai <tiwai@suse.de>
To: "Yang, Libin" <libin.yang@intel.com>
Cc: kernel test robot <ying.huang@linux.intel.com>,
"lkp@01.org" <lkp@01.org>, LKML <linux-kernel@vger.kernel.org>,
"Wu, Fengguang" <fengguang.wu@intel.com>,
"Lin, Mengdong" <mengdong.lin@intel.com>
Subject: Re: [lkp] [ALSA] ca53fbf3a6: WARNING: CPU: 0 PID: 151 at sound/hda/hdac_i915.c:129 pin2port+0x2a/0x40 [snd_hda_core]()
Date: Mon, 14 Mar 2016 14:02:51 +0100 [thread overview]
Message-ID: <s5hfuvt43gk.wl-tiwai@suse.de> (raw)
In-Reply-To: <96A12704CE18D347B625EE2D4A099D1904681A1B@SHSMSX103.ccr.corp.intel.com>
On Mon, 14 Mar 2016 13:02:39 +0100,
Yang, Libin wrote:
>
> Hi Takashi,
>
> > -----Original Message-----
> > From: Takashi Iwai [mailto:tiwai@suse.de]
> > Sent: Monday, March 14, 2016 3:23 PM
> > To: kernel test robot
> > Cc: lkp@01.org; LKML; Wu, Fengguang; Yang, Libin; Lin, Mengdong
> > Subject: Re: [lkp] [ALSA] ca53fbf3a6: WARNING: CPU: 0 PID: 151 at
> > sound/hda/hdac_i915.c:129 pin2port+0x2a/0x40 [snd_hda_core]()
> >
> > On Mon, 14 Mar 2016 01:50:45 +0100,
> > kernel test robot wrote:
> > >
> > > FYI, we noticed the below changes on
> > >
> > > https://github.com/0day-ci/linux Takashi-Iwai/ALSA-hda-Add-a-sanity-
> > check-of-pin-port-mapping-on-i915-HDMI-DP/20160310-225740
> > > commit ca53fbf3a609b6831222078af9ddbecbf76fddce ("ALSA: hda -
> > Add a sanity check of pin / port mapping on i915 HDMI/DP")
> > >
> > >
> > > [ 14.546058] snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops
> > i915_audio_component_bind_ops [i915])
> > > [ 14.549740] fbcon: inteldrmfb (fb0) is primary device
> > > [ 14.553691] ------------[ cut here ]------------
> > > [ 14.553707] WARNING: CPU: 0 PID: 151 at
> > sound/hda/hdac_i915.c:129 pin2port+0x2a/0x40 [snd_hda_core]()
> >
> > Does your tree contain the commit
> > 2f791908a70e95768596f5bb9e6de4f441d7bf13
> > drm/i915: Fix bogus dig_port_map[] assignment for pre-HSW
> > ?
> >
> > The commit above should cover it even for HSW.
> >
> > If it's already included, then it's really a bug, and the warning is
> > exactly for catching such a bug. The HD-audio driver expects that the
> > valid audio ports are only from port B to port D while i915 driver
> > assigns a different one. I suspect that the current assumption is too
> > naive and broken for SKL and later in this regard.
> >
> > Libin, Mengdong, could you check whether the audio port mapping rule
> > is still valid? At least, a wrong port-A mapping could be reproduced
> > even on a HSW laptop with DP-MST dock when I boot without eDP
> > (e.g. video=eDP-1:d option).
>
> We checked with HW before, and the mapping should be right.
> What's the problem now? I will check with our HW and gfx team.
One problem I've heard is that port-A is reported from i915 ELD
notifier. This happens when you disable eDP and use DP-MST on a HSW
machine. Then port A DDI is also used for the DP-MST, and when it's
plugged, it passes port=0 to the notifier.
Takashi
next prev parent reply other threads:[~2016-03-14 13:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 0:50 kernel test robot
2016-03-14 7:22 ` Takashi Iwai
2016-03-14 12:02 ` Yang, Libin
2016-03-14 13:02 ` Takashi Iwai [this message]
2016-03-14 15:30 ` Lin, Mengdong
2016-03-14 17:11 ` Takashi Iwai
2016-03-15 16:11 ` Lin, Mengdong
2016-03-16 3:15 ` Lin, Mengdong
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=s5hfuvt43gk.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=fengguang.wu@intel.com \
--cc=libin.yang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mengdong.lin@intel.com \
--cc=ying.huang@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®